mirror of
https://github.com/monoscope-tech/monoscope.git
synced 2026-11-16 10:18:01 +00:00
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
|
|
|---|---|---|
| .. | ||
| i18n | ||
| migrations | ||
| migrations-pending | ||
| public | ||