<unknown>: Queue lag above threshold: <num> messages on invoices at <ip>
no frame attributed
No stack trace was sent, so the normalized message is the only thing identifying this group.
Table view
| Bucket (UTC) | Events |
|---|---|
| 2026-08-22 15:00:00 | 0 |
| 2026-08-22 16:00:00 | 0 |
| 2026-08-22 17:00:00 | 0 |
| 2026-08-22 18:00:00 | 0 |
| 2026-08-22 19:00:00 | 0 |
| 2026-08-22 20:00:00 | 0 |
| 2026-08-22 21:00:00 | 0 |
| 2026-08-22 22:00:00 | 0 |
| 2026-08-22 23:00:00 | 0 |
| 2026-08-23 00:00:00 | 0 |
| 2026-08-23 01:00:00 | 0 |
| 2026-08-23 02:00:00 | 0 |
| 2026-08-23 03:00:00 | 0 |
| 2026-08-23 04:00:00 | 0 |
| 2026-08-23 05:00:00 | 0 |
| 2026-08-23 06:00:00 | 0 |
| 2026-08-23 07:00:00 | 0 |
| 2026-08-23 08:00:00 | 0 |
| 2026-08-23 09:00:00 | 0 |
| 2026-08-23 10:00:00 | 0 |
| 2026-08-23 11:00:00 | 0 |
| 2026-08-23 12:00:00 | 0 |
| 2026-08-23 13:00:00 | 0 |
| 2026-08-23 14:00:00 | 0 |
How this group was decided
Every step below is a pure function of the event. The same event always produces the same group.
1 · Parse the stack trace
No frames were parsed from this event.
2 · Build the fingerprint input
Line numbers are dropped so that editing a line above the throw site does not open a new group. Values inside the message are replaced with placeholders.
v1 platform=unknown service=billing-worker type=<unknown> message=Queue lag above threshold: <num> messages on invoices at <ip> degraded=no_frames
3 · Hash it
SHA-256 of the text above, truncated to 128 bits. The version is part of the group key: a future algorithm opens new groups rather than rewriting these.
Fingerprint2c2f0ac56787133eb94b8bd4bf6462c8Algorithm versionv1
Similar groups
Trigram similarity computed by Postgres against a GIN index. It catches what a fingerprint cannot — the same fault one refactor away from an existing group. No model is involved.
Nothing above the 0.3 similarity threshold.