No data in Crash Reporting for ASP.NET Core 6 app

Hi Jen,

I was able to get the configuration you have provided to work correctly on a .NET 7 application. What version of .NET are you using?

I can think of 2 reasons why it might not be working for you:

1. The API key is incorrect or not being read from the appsettings file correctly
2. Another middleware is capturing the exception before the Raygun middleware can process it

To confirm if the first reason is the issue you can include this code to print out the configured API key:

var raygunConfig = builder.Configuration.GetSection("RaygunSettings").Get<RaygunSettings>();
Console.WriteLine($"Raygun API Key: {raygunConfig?.ApiKey}");

For the second reason, check if you have any other error-handling middleware configured and temporarily disable them to see if that allows Raygun to process the exceptions. It might be the case that you need to re-arrange the order of your middleware to ensure the Raygun middleware can process the exceptions.

Let me know how you get on.

Kind regards,

Jasen

Hello,

When you say you moved it to be the first item, did you put it before:

    // Configure the HTTP request pipeline.
    if (!app.Environment.IsDevelopment())
    {
        app.UseExceptionHandler("/Error/Index");

i.e

    app.UseRaygun();

    // Configure the HTTP request pipeline.
    if (!app.Environment.IsDevelopment())
    {
        app.UseExceptionHandler("/Error/Index");

I'm thinking that if UserExceptionHandler is run first it might be short circuiting the request so Raygun is never run.

NLog wouldn't interfere with Raygun would it?

No it shouldn't interfere at all. However if you're using the NLog Raygun provider there maybe a conflict. NLog.Raygun only works with Raygun v6.#, we haven't rolled out an update for v7 yet.

If it doesn't work moving it before the if (!app.Environment.IsDevelopment()) would you mind showing your Nuget References so we can try reproduce the issue?

Thank you,

Phill

Hi Jen,

Thanks for the extra information.

I have attempted to reproduce your issue but so far have been unsuccessful.

Looking at your stack trace, are exceptions being handled within the ReportConfigHandler class? Raygun will only automatically capture unhandled exceptions. Handled exceptions will need to be reported to Raygun manually.

Would you be able to provide a minimal project with the issue present so that I can investigate further?

Thanks,

Jasen

Hi Jen,

Thanks for sending through that project. There does not seem to be any issues with the configuration.

It does seem very likely that there is a configuration issue with your server. Take a look at the troubleshooting information here and let me know how you get on.

Thanks,

Jasen

An empty JSON response does indicate a 201 response but it is very odd that the error never turned up in Crash Reporting. Just to rule out any transitive issues could you try running the script one more time?

To enable the ThrowOnError setting you will need to add it to your appsettings file like so:

"RaygunSettings": {
    "ApiKey": "xxxxxx",
    "ThrowOnError": true
}

Let me know if enabling that setting provides any clues.

Thanks,

Jasen

Hey,

So just to double check, the PowerShell script produced that result on your test server right?

If we create a self-contained console app to test with are you able to put that on the test-server to test?

Alternatively if we published a pre-release nuget which outputs some more information can you test that out?

Thanks,

Phill

Hi,

Sorry for the delay in replying.

We have released a fix for the issue that was preventing you from receiving errors when running the PowerShell script.

Could you please run the script one more time from your test server to validate there are no more problems there?

We should be able to get you a test application to run shortly.

Thanks for your patience,

Jasen

Hi Jen,

I have attached a test application that contains a debug build of the raygun4net provider. The application has one endpoint /test that will throw an exception when called. Build, run the application on your server, navigate to the /test route and you should see in the output information about the status of sending the exception to Raygun.

Could you please run this test application on your server and let me know what the output is?

Thanks,

Jasen

Hi Jen,

Thanks for running the test project.

It seems like there is something interfering with how the configuration is being loaded. This may be from an Environment Variable or some other configuration on your server.

To check this, within the test application I sent, could you add the following lines of code after the line var app = builder.Build();

var logger = app.Services.GetRequiredService<ILogger<Program>>();
var root = builder.Configuration as IConfigurationRoot;
logger.LogInformation(root.GetDebugView());

This will print all configuration keys and values with the provider that has set the value.

There should be a section for the RaygunSettings which looks like the following:

  RaygunSettings:
    ApiKey=API_KEY_HERE (JsonConfigurationProvider for 'appsettings.json' (Optional))

Let me know if this contains the expected ApiKey value. If not you will need to check where it has pulled the configuration from and either update the value there or remove it.

Regards,

Jasen

From what you have said it seems like there are some environment variables that are overriding the values in your appsettings file.

If you run one of the following commands it will output all the environment variables on your server

PowerShell:

Get-ChildItem Env: | Format-Table -Wrap -AutoSize

Command Prompt:

set

If there is an entry with the name RaygunSettings__ApiKey you may need to investigate why it has been added as removing may have adverse effects on your other applications running on the server if they also run Raygun (if they are running Raygun, it might be worth checking how they are passing through the API key).

One solution is to pass in the Raygun API key when you run the application. For example, when running the RaygunTest application from the command line:

RaygunTest.exe --RaygunSettings:ApiKey API_KEY_HERE

Let me know how you get on with checking the environment variables.

Regards,

Jasen

Hi Jen,

From the screenshots, I can see you are executing the exe from a different directory than where it is located. By default .NET does not set the content root to the directory of the executing file but rather from where you have executed the command. In this case, you are executing from the C:\Users\jm5-admin directory so this is set as the content root. This is where .NET will look for the appsettings files. To always have the content root set to the directory of the executing program you can update the program as follows:

Directory.SetCurrentDirectory(AppDomain.CurrentDomain.BaseDirectory);
var builder = WebApplication.CreateBuilder(args);

Otherwise, run the exe from within the directory it is located and that will have the same outcome.

Doing one of these steps should allow your appsettings to be loaded correctly.

As for why the RaygunClient log messages are no longer being shown, it might be due to the logger and trace both trying to write to the console at the same time. You can add the following line to remove the logging and only see the output of the RaygunClient:

builder.Services.AddLogging(s => s.ClearProviders());

Let me know how you get on.

Regards,

Jasen

Just to clarify where we are at the program file of the RaygunTest app should look something like this:

using System.Diagnostics;
using Mindscape.Raygun4Net.AspNetCore;

Directory.SetCurrentDirectory(AppDomain.CurrentDomain.BaseDirectory);

var builder = WebApplication.CreateBuilder(args);

Trace.Listeners.Add(new ConsoleTraceListener());

builder.Services.AddControllers();
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();

builder.Services.AddRaygun(builder.Configuration);

builder.Services.AddLogging(s => s.ClearProviders());

var app = builder.Build();

if (app.Environment.IsDevelopment())
{
  app.UseSwagger();
  app.UseSwaggerUI();
}

app.UseRaygun();

app.UseHttpsRedirection();
app.UseAuthorization();
app.MapControllers();

app.Run();

Now that we are setting the CurrentDirectory the app can be run from anywhere and successfully load the appsettings file.

For example with the command: ./RaygunTest.exe

The app will no longer output anything into the console as we have disabled logging but you should be able to navigate to http://localhost:5000/Test to trigger the exception. Once triggered, there should be a message in the console about the status of sending the exception to Raygun.

Please confirm this is your setup and we'll take it from there.

Thanks,

Jasen

Hi Jen,

I have created a new test application that I would like you to build and then run on your test server. This new application has a new version of raygun4net that has some additional logging enabled. This should be able to tell us if raygun4net is being configured correctly as well as the result of sending exceptions to Raygun.

You will need to add your API key to the appsettings file but otherwise, it is the same as the RaygunTest application and you simply need to navigate to /Test route to trigger an exception.

Let me know if you get any output from running this application.

This has narrowed it down for us. I have updated the DebugRaygun app with some more debug logging which should tell us exactly where it is going wrong.

Let me know how this one goes, thanks.

Jasen

Hi Jen,

Assuming your self-signed certs are valid I wouldn't think they are the cause.

You will need to do some debugging into why your server is failing to complete the TLS handshake with the Raygun API. It might be an issue with the cipher suites available on your server. Take a look at this post and see if it can help to resolve this issue.

Let me know how you get on with this.

Jasen