infoopennode-demojavascript

<unknown>: demo run finished

no frame attributed

Events3
First seen14d ago2026-08-09 15:27:10 UTC
Last seen14d ago2026-08-09 16:11:54 UTC
Releasesnode-demo-1.0.0 → node-demo-coldstart
no_frames

No stack trace was sent, so the normalized message is the only thing identifying this group.

Frequency

24 hours7 days30 days
Events per hour, from the rollups0 in this window · peak 1
15:00
 
 
 
19:00
 
 
 
23:00
 
 
 
03:00
 
 
 
07:00
 
 
 
11:00
 
 
 
Table view
Bucket (UTC)Events
2026-08-22 15:00:000
2026-08-22 16:00:000
2026-08-22 17:00:000
2026-08-22 18:00:000
2026-08-22 19:00:000
2026-08-22 20:00:000
2026-08-22 21:00:000
2026-08-22 22:00:000
2026-08-22 23:00:000
2026-08-23 00:00:000
2026-08-23 01:00:000
2026-08-23 02:00:000
2026-08-23 03:00:000
2026-08-23 04:00:000
2026-08-23 05:00:000
2026-08-23 06:00:000
2026-08-23 07:00:000
2026-08-23 08:00:000
2026-08-23 09:00:000
2026-08-23 10:00:000
2026-08-23 11:00:000
2026-08-23 12:00:000
2026-08-23 13:00:000
2026-08-23 14:00:000

How this group was decided

Every step below is a pure function of the event. The same event always produces the same group.

  1. 1 · Parse the stack trace

    No frames were parsed from this event.

  2. 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=javascript
service=node-demo
type=<unknown>
message=demo run finished
degraded=no_frames

  3. 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.

    Fingerprint
    49c608c7c0cbd20e64880c3d411b02f5
    Algorithm version
    v1

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.