Setting up Signals
Signals lives in Pathrule Studio. Turn it on for a workspace and it starts grouping your product's runtime incidents into the Signals view, with nothing to install and no code to add.
Signals is part of Pathrule Studio. You turn it on from inside Studio, per workspace. There is nothing to install and no code to wire up.
Turn it on
- Open the workspace you want to monitor in Pathrule Studio.
- Enable Signals for that workspace.
That is the whole setup. Signals begins grouping runtime incidents for the workspace and surfaces them in the Signals view. On Solo, one workspace can run Signals at a time; see Plans, quotas and retention for the details.
What you see
Each incident shows up in the Signals view with:
- Status. Active, observing a newer release, quiet, runtime verified, or recurred.
- What happened. The message, environment, release, count, and when it was first and last seen.
- Why here. The resolved node path and the flow it belongs to.
- Context supplied. The exact rules and memories that were attached, with their versions.
- Runtime outcome. The production evidence gathered after a fix, once observation has started.
From incident to task
When an incident crosses a worthiness threshold, Signals hands it to the same Tasks flow you already use, with a Context Brief in the card prompt. Everything after you start the card is unchanged. See How the loop works for the full path from a production event to a verified fix.
Availability
Signals runs in Pathrule Studio.
What to read next
- Signals overview for the product story.
- How the loop works for detection, context, and verification.