Skip to main content
A signal is one piece of external feedback about a trace, a step, or a session: a thumbs-up/down, a star rating, or a written complaint. Signals let real-world feedback drive what Glassray investigates.

​
Where signals come from

Slack

Report a problem to the Glassray bot in a channel.

The dashboard

A teammate flags a trace directly in Glassray.
A signal carries a source (human, end_user, api, slack, or external), an optional valence (positive, negative, or neutral), and optional rating, body, and author.

​
What gets actioned

A negative signal pinned to a resolved trace is actioned: Glassray classifies that trace into a flow and appends it to a matching deviation, or logs a new 🔎 Suspected one - a single report isn’t yet confirmed to recur, so Glassray then scans for more examples to confirm it.
Positive or neutral feedback, and feedback pinned only to a session or step (with no resolved trace), is stored for context but not actioned.
Report misbehavior from Slack and Glassray turns it into a deviation.