Prompt
Do I need a dashboard for latency if I only care about correctness?
Latest observation
Not strictly, no — if you only care about correctness, a latency dashboard is not required.
That said, it can still be useful indirectly:
-
Latency spikes can be a symptom of correctness issues
Timeouts, retries, race conditions, or overload can cause both slowness and wrong behavior. -
Latency can help explain failures
If correctness checks fail under load, a latency view can help you see whether the system was slow enough to trigger timeouts or stale data. -
It helps distinguish “wrong” from “slow”
A dashboard makes it easier to tell whether an issue is a data/logic bug or a performance problem.
If you truly only want to know “is the output correct?”, better tools are:
- assertions / tests
- canary checks
- diffing against expected results
- consistency checks
- error-rate dashboards
- domain-specific correctness metrics
So: not necessary, but often helpful as supporting evidence. If you want, I can suggest a minimal observability setup for a correctness-only system.