Deduced Tags

When searching for events in Bugsink, you can filter them by tags. Tags are key-value pairs that provide additional context to events. For example, you can filter events by the release tag to see all events from a specific version of your application.

This raises the question: where do these tags come from? There are basically two kinds: those explicitly set by the SDK, and those that Bugsink itself deduces from the event data, and then explicitly stores.

For deduced tags, Bugsink extracts relevant metadata from events into tags. Examples include information like browser name, OS version, or whether an exception was handled. Bugsink also extracts top-level event attributes like release, environment, or server_name.

Here’s the list of tags that Bugsink deduces from event data.

Event Data Tags

• server_name – The name of the server where the event occurred.
• release – The release version of the application.
• environment – The environment in which the event happened (e.g., production, staging).
• transaction – The transaction associated with the event.

Exception Data Tags

• handled – Whether the main exception was handled by a mechanism. (‘true’ or ‘false’ – the tag’s value is stored and searchable as a string).

Contextual Tags

• trace – The trace ID for distributed tracing.
• trace.span – The span ID within the trace.
• trace.ctx – A combined value of trace and trace.span (trace_id.span_id).
• browser.name – The name of the browser.
• browser.version – The version of the browser.
• browser – A combined value of browser.name and browser.version.
• os.name – The name of the operating system.
• os.version – The version of the operating system.
• os – A combined value of os.name and os.version.

User Tags

• user – The most relevant identifier available (in order: id, username, email, or ip_address).
• user.id – The user ID.
• user.username – The username.
• user.email – The email address.
• user.ip_address – The IP address of the user.