Skip to main content
A signal feed is only as good as what it watches. The Coverage tab on the Signals page shows every monitoring rule Hive runs on your connected tools, so you always know what a quiet feed does — and does not — mean. Open it from Signals → Coverage (/signals?tab=watching). Older links to /monitoring open the same view.
Four coverage states: watched, limited, paused, and not yet covered, each explaining what silence does and does not prove.

Coverage separates 'we checked' from 'we could not check'. Zero alerts about an area Hive cannot see means nothing about that area.

The illustration above shows the full coverage design. Today the tab lists each rule and marks it Watching, Learning or Paused; the richer “limited” and “not yet covered” states are part of the Signal Cases pilot.

​
How monitoring rules are created

When you connect a tool, Hive writes a monitoring plan for it: a set of metrics it can read from that tool and a reason each one matters to your business. Before a metric is added, Hive dry-runs the read and keeps it only if it returns a real number, so the plan never contains a metric that cannot actually be measured. Rules are grouped by connected tool. Each row shows the metric, why it matters, whether it can lead to an action (Can create an action) or is Watch only, and its status.

​
Statuses

Metrics come in two kinds:
  • State (threshold) — is something true right now, such as “more than 3 invoices overdue”. A state metric is ready immediately.
  • Trend (baseline) — is something moving unusually compared with its own history. Hive learns the normal range first, then flags readings well outside it.

​
Add, edit or pause a rule

People with the Operator role or higher can change the plan.
1

Add a rule

Choose Add rule and pick the provider. Tell Hive what to watch in plain words and add a rationale. For each remaining field — the kind of metric, the threshold — you can set a value or leave it on Hive decides. Choose Create rule.
2

Edit a rule

Choose Edit on the rule, change what you need, then choose Save changes. Clearing the consequence or next-step field keeps its current value.
3

Pause a rule

Choose Pause on the rule. It shows as Paused and stops producing signals. Choose Resume to turn it back on.
Pausing a rule is the right way to stop something permanently. Signal mutes always expire (after at most 90 days), but a paused rule stays paused — and stays visible here, so nobody mistakes it for a broken detector.

​
When the feed is quiet

Silence can mean nothing unusual happened. It can also mean a source is delayed, a permission is missing, a rule is still learning, or an area is not covered at all. Before treating a quiet feed as an all-clear:
  1. Open Signals → Coverage.
  2. Confirm the rule you expect is listed and marked Watching, not Learning or Paused.
  3. Check the tool’s connection on the Integrations page (see Health and disconnecting).
  4. If the rule you need does not exist, add it.
If the page shows Nothing watched yet, no connected tool has a monitoring plan. Connect a tool first — see Connect an app.

Signals overview

How detection, baselines and gating work.

Triage signals

Act on, snooze or dismiss what Hive raises.

Trustworthy signals

Why Hive states its limits instead of guessing.

Integrations catalog

What each connected tool can feed into Signals.