Signal Severity

Galileo AI scores every Signal LogRocket detects for severity — a measure of how likely it is to frustrate users or block them from completing a task. Severity is what LogRocket uses to decide which Signals are worth acting on: when a Signal's severity crosses Galileo's threshold, LogRocket automatically opens a High-priority Issue for it. Severity is owned by Galileo — you can't set it by hand.

🚧

Not available for self-hosted installations

Severity is not yet available for self-hosted installations of LogRocket. For further questions, contact your LogRocket representative.

AI-driven severity

Galileo scores severity using machine learning and LLMs (large language models) trained on LogRocket session and Issue data. Severity is computed over a trailing window of roughly the last 30 days and re-evaluated on a rolling basis, so it sharpens as more data accumulates for a Signal.

Natural-language titles

For a severe Signal, Galileo replaces the technical title with a plain-language description of what users actually experienced. For example, Error • TypeError: Cannot read properties of undefined (reading 'destroy') may become Users unable to access or analyze data within selected time range.

Severity in the Issue Detail view

When an Issue was opened from a severe Signal, its detail view shows a severity indicator in the header. In the event list, individual session events are flagged when they're especially good representations of the problem, and events can be sorted by severity or by time.

Severity in session replay

In session replay, when an event is associated with a Signal, a severity indicator and a link to the related Issue appear alongside it. The indicator reflects the degree of user frustration at that moment.

• JavaScript Error Signals appear in the Logs pane.
• Network Error Signals appear in the Network pane.
• All other Error Signals (Rage Clicks, Dead Clicks, Error States, Frustrating Network Requests) appear in the Event Timeline.

🚧

Network traffic is sampled

LogRocket samples network events before processing them, so not every network error will have an associated Issue link and severity rating.

Getting notified

• Issues Alerts notify your team the moment Galileo opens an Issue from a severe Signal.
• Errors Digests deliver a scheduled roundup of your most severe Errors.

Helping severity improve

Severity sharpens with your input. When you open an Issue from a Signal, override an Issue's priority, or ignore a Signal, you're teaching Galileo which problems matter to your team — making similar scoring more or less likely in the future.

🚧

Changing grouping conditions may change a severity rating

Customizing an Error's grouping conditions may cause its severity rating to change.