Set Up Logs

Structured logs allow you to send, view and query logs sent from your applications within Sentry.

With Sentry Structured Logs, you can send text-based log information from your applications to Sentry. Once in Sentry, these logs can be viewed alongside relevant errors, searched by text-string, or searched using their individual attributes.

Logs for Serilog are supported in Sentry Serilog SDK version 5.16.0 and above.

To enable logging, you need to initialize the SDK with the Experimental.EnableLogs option set to true.

Copied
.WriteTo.Sentry(options =>
{
    options.Dsn = "";
    // Enable logs to be sent to Sentry
    options.Experimental.EnableLogs = true;
});

Once the feature is enabled on the SDK and the SDK is initialized, you can send logs using the Serilog APIs.

The static Log and instance Logger types expose various methods that you can use to log messages at six different log levels automatically mapped to Sentry's severity:

Serilog.Events.LogEventLevelSentry.SentryLogLevelSentry Logs UI Severity
VerboseTracetrace
DebugDebugdebug
InformationInfoinfo
WarningWarningwarn
ErrorErrorerror
FatalFatalfatal

These properties will be sent to Sentry, and can be searched from within the Logs UI, and even added to the Logs views as a dedicated column.

Copied
using (LogContext.PushProperty("Version", 5150))
{
    Log.Information("A simple log message");
    Log.Error("A {Parameter} log message", "formatted");
    Log.ForContext("Property", "Value").Warning("Message with Property");
}

The Enrichments of log events are attached as attributes to the logs, alongside a set of default attributes automatically provided by the SDK.

Available integrations:

If there's an integration you would like to see, open a new issue on GitHub.

Set to true in order to enable the logging integration via the Log/Logger APIs.

To filter logs, or update them before they are sent to Sentry, you can use the Experimental.SetBeforeSendLog(Func<SentryLog, SentryLog?>) option.

Copied
options =>
{
    options.Dsn = "";
    options.Experimental.EnableLogs = true;
    // a callback that is invoked before sending a log to Sentry
    options.Experimental.SetBeforeSendLog(static log =>
    {
        // filter out all info logs
        if (log.Level is SentryLogLevel.Info)
        {
            return null;
        }

        // filter out logs based on some attribute they have
        if (log.TryGetAttribute("suppress", out var attribute) && attribute is true)
        {
            return null;
        }

        // set a custom attribute for all other logs sent to Sentry
        log.SetAttribute("my.attribute", "value");

        return log;
    });
});

The callback function set via Experimental.SetBeforeSendLog(Func<SentryLog, SentryLog?>) receives a log object, and should return the log object if you want it to be sent to Sentry, or null if you want to discard it.

The log object of type SentryLog has the following members:

  • Timestamp Property: (DateTimeOffset) The timestamp of the log.
  • TraceId Property: (SentryId) The trace id of the log.
  • Level Property: (SentryLogLevel) The severity level of the log. Either Trace, Debug, Info, Warning, Error, or Fatal.
  • Message Property: (string) The formatted log message.
  • Template Property: (string?) The parameterized template string.
  • Parameters Property: (ImmutableArray<KeyValuePair<string, object>>) The parameters to the template string.
  • ParentSpanId Property: (SpanId?) The span id of the span that was active when the log was collected.
  • TryGetAttribute(string key, out object value) Method: Gets the attribute value associated with the specified key. Returns true if the log contains an attribute with the specified key and it's value is not null, otherwise false.
  • SetAttribute(string key, object value) Method: Sets a key-value pair of data attached to the log. Supported types are string, bool, integers up to a size of 64-bit signed, and floating-point numbers up to a size of 64-bit.

The .NET SDK automatically sets several default attributes on all log entries to provide context and improve debugging:

  • environment: The environment set in the SDK if defined. This is sent from the SDK as sentry.environment.
  • release: The release set in the SDK if defined. This is sent from the SDK as sentry.release.
  • sdk.name: The name of the SDK that sent the log. This is sent from the SDK as sentry.sdk.name.
  • sdk.version: The version of the SDK that sent the log. This is sent from the SDK as sentry.sdk.version.

If the log was parameterized, Sentry adds the message template and parameters as log attributes.

  • message.template: The parameterized template string. This is sent from the SDK as sentry.message.template.
  • message.parameter.X: The parameters to fill the template string. X can either be the number that represent the parameter's position in the template string (sentry.message.parameter.0, sentry.message.parameter.1, etc) or the parameter's name (sentry.message.parameter.item_id, sentry.message.parameter.user_id, etc). This is sent from the SDK as sentry.message.parameter.X.

  • server.address: The address of the server that sent the log. Equivalent to server_name that gets attached to Sentry errors.

If user information is available in the current scope, the following attributes are added to the log:

  • user.id: The user ID.
  • user.name: The username.
  • user.email: The email address.

If a log is generated by an SDK integration, the SDK will set additional attributes to help you identify the source of the log.

  • origin: The origin of the log. This is sent from the SDK as sentry.origin.
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").