Issues

Issues are the single funnel every Monita detector feeds. Whatever finds a problem — an automatic engine, a compliance monitor, an audit, a change watch or one of your own alert rules — it files an issue here, with one lifecycle and one triage surface: app.monita.ai/issues.

What files issues

The Sources tab on the Issues page shows the live version of this table — what each source has filed and where to tune it.

Source	What it files
Auto — volume anomalies	The seasonal engine scans every vendor-event signal on your chosen frequency. Zeros, drops, spikes and traffic bleed file here; recoveries auto-resolve after three healthy hours.
Auto — data anomalies	Payload drift with an AI verdict: vanished keys, blanked values, format breaks — each issue carries a concrete recommendation.
Compliance monitor	PII-shaped values detected in vendor payloads, blocked vendors still firing, and findings you file from the PII deep scan.
Audits	Real-browser audit runs: blocked vendors still loading, unreviewed vendors piggybacking in through other vendors’ scripts.
Change confidence	Detected stack changes (a GTM publish, a TMS/CMS/CMP swap) open watch windows on the signals they can affect; a regressed verdict files an issue.
Custom alerts	Your own alert rules — data validation, thresholds, volume changes, journeys — with your own channels and severity.

The issue lifecycle

Every source writes into the same lifecycle:

• Deduplicated per signal. A recurring problem is one issue that accrues occurrences, not a fresh page every hour. Occurrences keep counting even while notifications are throttled — the Details panel shows both numbers.
• Notified on open and on recovery. You hear when an issue opens and when it recovers; in between, further firings land on its timeline without paging anyone.
• Auto-resolved where the detector can prove recovery. Volume anomalies resolve themselves after three consecutive healthy hours; other sources resolve when you (or Jira — see below) close them.

Paused notifications after a traffic-mix change

When a property’s traffic mix shifts abruptly — one hostname goes quiet, another starts sending significant volume — Monita treats it as a likely environment cutover rather than broken tags. Automatic anomaly notifications pause briefly while baselines re-learn; occurrences are still recorded and your own alert rules still deliver. A banner on the Issues page shows any active pause.

Severity

Issues carry a severity of critical, high, medium or low. Automatic engines assign severity from the size of the deviation; custom rules use whatever severity you set on the rule. The four cards at the top of the list are also filters — click one to focus the table.

Triage

• Statuses: open → acknowledged → resolved, plus muted for known noise. Reopen anytime.
• Resolve inline from the list, or open an issue for its full detail: the live signal chart behind the issue (actual vs the expected band), the detected payload, a per-day occurrence history, the notification timeline and free-text notes.
• Bulk triage: select any set of rows and resolve, acknowledge or reopen them together.
• Filters live in the URL — property, host, type, source, status, severity — so a triaged view is a shareable link. The search box queries the server, reaching issues older than the loaded window.
• Value protected: rules can carry a dollar impact; resolved issues accrue it on the Value page.

Jira two-way sync

With the Jira integration connected, issues can be filed to Jira automatically (above a severity floor you choose) or manually from any issue’s Create Jira issue button. The link is two-way:

• Moving the Jira ticket to a Done-category status resolves the Monita issue.
• Recoveries and resolutions in Monita comment on the Jira ticket.

The linked ticket key appears on the issue and in the list. Issues can also route to Slack, Teams, webhooks and email through your alert rules.