Monitor
In short
Monitor is where Solcoro watches your Jira configuration over time. Explore shows you the current state; Monitor shows you movement: what changed, when, and whether it matters.
Monitor has four sub-surfaces, each answering a different question:
Surface | The question it answers | How it works |
|---|---|---|
What changed since last time? | Scheduled scans compared to the previous scan, with Watches defining what to alert on | |
How far have we moved from the state we approved? | Scheduled scans compared to a fixed Gold Scan, with Signals on Checks defining what counts as drift | |
What is the full record of change? | The running log of configuration change across all scans | |
What is different between these two specific scans? | On-demand comparison of any two scans from the same integration |
Choosing between Pulse and Drift
Pulse and Drift are parallel, self-contained products, each with its own Reports and Settings tabs, its own schedule, and its own alerting model.
The difference is the reference point. Pulse always compares to the previous scan: it is ambient awareness, telling you what moved in the last cycle. Drift always compares to your Gold Scan: it is governance tracking, telling you the accumulated distance from a state you deliberately approved.
The alerting models differ to match. Pulse uses Watches (specific items, item types, checks, or space scopes to monitor for change). Drift uses Signals (checks classified as Alert or Trend, with severities and thresholds). A check can be watched in Pulse and carry a Signal in Drift at the same time; the two never interact.
Most teams run both: Pulse weekly for awareness, Drift on a schedule against the Gold Scan for governance. When both are scheduled in the same window, Solcoro runs one scan and uses it for both, so you never pay double API load on your Jira instance.
The scheduled vs on-demand split
Pulse and Drift are scheduled: they run on a cadence and produce dated reports with history. Compare Scans is on-demand: you pick any two scans and get the answer now. Change History is continuous: it accumulates as scans run, regardless of schedule.
A common investigation flows through all of them: a Drift report flags an alert → View in analyzer opens the same comparison in Compare Scans for structural detail → Change History tells you when the change first appeared → Explore shows you the object's current state.
Before you begin
You need a connected integration. Pulse and Drift additionally need their schedules configured (each in its own Settings tab); Compare Scans needs at least two completed scans.
What's next
Pulse — scan-over-scan monitoring with Watches
Drift — Gold Scan monitoring with Signals on Checks
Change History — the running change log
Compare Scans — on-demand comparison of any two scans