monoscope/static
Anthony Alaribe ff8d94ee20 feat(issues): make the query-alert page show the breach
A query alert rendered its KQL string and nothing else: not the threshold,
not the value that crossed it, not a chart of the series, and no link back
to the monitor. Below that two-line box the Investigation panel reserved
lg:h-[70vh] and filled it with "No trace data available" — a query alert has
no originating request, so mTraceRef is Nothing by construction and that
~1100px of void was unreachable by design, not merely empty.

- Threshold Breach panel: actual vs threshold, with the direction carried by
  an arrow as well as colour, and the trigger time.
- The alert's own query is now plotted, with its threshold drawn across it
  (Widget already had alertThreshold/showThresholdLines; nothing new needed).
- Monitor link, reading the id tolerantly: query_id is persisted as a `show`
  of the newtype, so every stored row needs the UUID extracted. Fixing the
  writer would change targetHash, which is the alert's dedup identity, so
  that stays out of this change.
- Investigation is suppressed for the one issue type that can never have a
  trace.
- isBoilerplateAction covers both canned recommendedAction strings; only one
  was suppressed before, so query alerts printed "Review the query results
  and take appropriate action." in the subtitle slot where Sentry and
  Datadog both put the culprit.
- `bolt` was referenced but absent from both sprite sheets, so it silently
  rendered nothing; added it.

docs/issues-page-redesign.md records the findings, the Sentry/Datadog
research they were checked against, and the plan for the rest.
History 2026-09-03 21:15:15 +02:00
..
i18n Add infrastructure inventory views 2026-08-27 15:00:05 +02:00
migrations feat(errors): distil merged groups into masks that run at ingest 2026-09-03 18:17:04 +02:00
migrations-pending fix(ingest): make legacy event retries idempotent 2026-08-20 21:44:19 +02:00
public feat(issues): make the query-alert page show the breach 2026-09-03 21:15:15 +02:00