Exception.Data missing

[btecu]

When handling some exceptions I have the following:

try {
  await PotentiallyDangerousCodeAsync();
} catch (SomeKindOfException ex) {
  ex.Data.Add("FieldToHelpMeDebug", "This is why");
  throw;
}

However, it looks like the Data fields are not showing in the Sentry UI.
Is there any way to get those fields to show up?

[jamescrosswell]

@btecu there are a couple of extension methods:

sentry-dotnet/src/Sentry/SentryExceptionExtensions.cs

Lines 10 to 26 in 2a8813a

	/// <summary>
	/// Set a tag that will be added to the event when the exception is captured.
	/// </summary>
	/// <param name="ex">The exception.</param>
	/// <param name="name">The name of the tag.</param>
	/// <param name="value">The value of the key.</param>
	public static void AddSentryTag(this Exception ex, string name, string value)
	=> ex.Data.Add($"{MainExceptionProcessor.ExceptionDataTagKey}{name}", value);
	/// <summary>
	/// Set context data that will be added to the event when the exception is captured.
	/// </summary>
	/// <param name="ex">The exception.</param>
	/// <param name="name">The context name.</param>
	/// <param name="data">The context data.</param>
	public static void AddSentryContext(this Exception ex, string name, IReadOnlyDictionary<string, object> data)
	=> ex.Data.Add($"{MainExceptionProcessor.ExceptionDataContextKey}{name}", data);

These add exception data using specific keys. Sentry's main exception processor will copy data from those keys to the event before it gets sent to Sentry.

Alternatively, you could write a custom exception processor. You can see a demonstration of this in the samples.

[btecu]

It would be much better if it just worked out of the box. Both those options are specific to Sentry, and likely unnecessarily.

I'll take a look at a custom exception processor.

[btecu]

I was able to add the data this way:

builder.WebHost.UseSentry(x => {
    x.SetBeforeSend(@event => {

        if (@event.Exception != null) {
    
        foreach (KeyValuePair<string, object> entry in @event.Exception.Data) {

                @event.SetExtra(entry.Key, entry.Value);

            }

        }



        return @event;

    });
});

It works, but it's completely avoidable. Sentry should just include those fields by default.
Exception.Data is a very standard way in .NET for developers to add exception details to help debug issues.

[bruno-garcia]

We used to add this OOTB. It seems like we had a regression at some point.

It was even on the original sample I wrote:

sentry-dotnet/samples/Sentry.Samples.AspNetCore.Mvc/Controllers/HomeController.cs

Lines 104 to 118 in 47df982

	catch (Exception e)
	{
	var ioe = new InvalidOperationException("Bad POST! See Inner exception for details", e);
	ioe.Data.Add("thoughts",
	// This is an example of sending some additional information with the exception... The following
	// anonymous object will be serialized and sent with the exception to Sentry as additional context.
	new
	{
	Question = "What is the meaning of life?",
	Answer = 42
	});
	throw ioe;
	}