Set Up Logs

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.

Requirements

Logs for Native are supported in Sentry Native SDK version 0.12.0 and above.

Setup

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

sentry_options_t *options = sentry_options_new();
sentry_options_set_enable_logs(options, true);
// set other options
sentry_init(options);

Usage

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

The API exposes six methods that you can use to log messages at different log levels: trace, debug, info, warn, error, and fatal.

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.

import io.sentry.Sentry;

sentry_log_info("A simple log message");
sentry_log_error("A %s log message", "formatted");

Options

before_send_log

To filter logs, or update them before they are sent to Sentry, you can use the before_send_log option.

static sentry_value_t
before_send_log_callback(sentry_value_t log, void *user_data)
{
    (void)user_data;
    sentry_value_t attribute = sentry_value_new_object();
    sentry_value_set_by_key(
        attribute, "value", sentry_value_new_string("little"));
    sentry_value_set_by_key(
        attribute, "type", sentry_value_new_string("string"));
    sentry_value_set_by_key(sentry_value_get_by_key(log, "attributes"),
        "coffeepot.size", attribute);
    return log;
}

sentry_options_set_before_send_log(options, before_send_log_callback, NULL);

The before_send_log function receives a log object and optional user_data, and should return the log object if you want it to be sent to Sentry, or it should free the log using sentry_value_decref(log) and return a sentry_value_new_null() if you want to discard it.

Default Attributes

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

Core Attributes

• 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.
• trace.parent_span_id: The span ID of the span that was active when the log was collected (only set if there was an active span). This is sent from the SDK as sentry.trace.parent_span_id.
• 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.

Message Template Attributes

If the log was paramaterized, 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.

For example, with the following log:

sentry_log_error("A %s log message", "formatted");

Sentry will add the following attributes:

• message.template: "A %s log message"
• message.parameter.0: "formatted"

User Attributes

• user.id: The user ID. Maps to id in the User payload, which is set by default by the SDKs.

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

• user.name: The username. Maps to username in the User payload.
• user.email: The email address. Maps to email in the User payload.