Source
Error capture, grouping & triage — found from sitemap — Bugsink
Checked for Bugsink on 6 Nov 2026
- Page
- https://www.bugsink.com/docs/grouping/
- Checked
- 6 Nov 2026, 04:21 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:4a86ccf6aa48565e9351b658b46dbd0a079caf04baf8497ff6a9f865857dceea
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Auto grouping Report an error
“In Bugsink, events are automatically grouped into issues based on their characteristics. This minimizes noise from duplicate errors, so you can focus on solving real problems.”
-
Exception grouping Report an error
“For events that contain an exception, Bugsink extracts the exception type and message. If multiple exceptions are chained, it uses the last one, which is usually the most relevant.”
-
Message normalization Report an error
“Before grouping, variable-looking parts of the message are normalized.”
-
Normalization patterns Report an error
“Network and contact values: email addresses, URLs, hostnames, and IPv4 and IPv6 addresses.”
-
Normalization hashes Report an error
“Identifiers and hashes: UUIDs, SHA-1-shaped strings, MD5-shaped strings, and hexadecimal values.”
-
Normalization numbers Report an error
“Numbers and time: integers, floats, dates and times, and durations such as 123ms or 1.5s.”
-
Normalization keyvalues Report an error
“Key/value literals: quoted strings in values such as name='alice', and booleans in values such as active=true.”
-
Normalization scope Report an error
“Normalization changes the internal grouping key only: the issue title and event data continue to show the original values.”
-
Log grouping Report an error
“For log messages, Bugsink uses a simpler approach. The event is labeled as “Log Message”, and the first line of the log becomes the issue title.”
-
Grouping tab Report an error
“To help you understand how events are grouped, Bugsink provides a Grouping tab in the issue details. Here you can see the automatic grouping keys attached to the issue.”
-
Fingerprinting Report an error
“Bugsink allows you to customize how events are grouped using fingerprinting. You can specify your own fingerprints to control how errors are grouped together. The string "{{ default }}" can be used to include Bugsink’s automatic grouping key”
-
New project grouping Report an error
“New projects use Value-normalized (latest) automatically.”
-
Old project optin Report an error
“Projects created before Bugsink 2.5.0 keep their original grouping behavior until a project administrator selects Value-normalized (latest) in the project settings.”
-
Transition period Report an error
“Changing the setting starts a 30-day transition. When an active issue recurs, Bugsink attaches its normalized key to the same issue, preserving its history and state.”
-
V1 grouping Report an error
“Exception Type and Value: Bugsink extracts the type and message of the last exception in the chain.”
-
V1 transaction factor Report an error
“Transaction: If the event contains a transaction, Bugsink incorporates it into the grouping key.”
-
V1 no normalization Report an error
“It does not normalize variable-looking parts of exception values or log messages.”
-
“🇪🇺 Made & Hosted in the EU”
Scores citing this record
- The Agency Tech Lead Error capture, grouping & triage
- The Data Protection Officer Error capture, grouping & triage
- The Mobile Team Lead Error capture, grouping & triage
- The SaaS CTO Error capture, grouping & triage
- The Skeptic Error capture, grouping & triage
- The Site Reliability Engineer Error capture, grouping & triage
- The Site Reliability Engineer APM, tracing & profiling