Observations
Observations are deploy-aware findings about broken URLs, route regressions, and edge regressions.
An observation is a finding that TrueClara believes a reviewer should inspect. It has a subject, evidence, severity, lifecycle state, and usually a deploy boundary.
Observation types
| Type | Subject | Evidence |
|---|---|---|
| Broken URL | Unmatched inbound path | Hits, sessions, referrers, suggested redirect, and deploy context. |
| Route regression | Route pattern | Baseline value-reach rate, current rate, sample sizes, CUSUM, and threshold. |
| Edge regression | Route-to-route transition | Baseline transition rate, current rate, sample sizes, CUSUM, and threshold. |
Severity
Severity is based on evidence and business impact.
- Critical: strong evidence on a value route, revenue route, or high-reach path.
- Warning: credible signal that needs review but has lower reach or confidence.
- Info: useful context, improvement, or low-risk signal.
Do not treat severity as an exact incident priority. Use the evidence panel, affected route, deploy, and value route status to decide what to do.
Lifecycle
| State | Meaning |
|---|---|
| Open | Needs review. |
| Acknowledged | The team has seen it and is investigating or accepting the risk. |
| False positive | The signal was not actionable or was explained by expected behavior. |
| Dismissed | The team intentionally closed the observation without remediation. |
Evidence quality
Strong observations usually have:
- A healthy route graph.
- Runtime events arriving for the current project.
- A deploy record for the relevant release.
- Enough traffic for the route or edge.
- Value routes configured when prioritizing conversion impact.
Weak observations usually come from missing graph data, no deploy context, too little traffic, or generic value route configuration.
How to review one
- Check the subject route or edge.
- Check the deploy and graph diff.
- Compare baseline and current sample sizes.
- Inspect value-route impact.
- Acknowledge, mark false positive, dismiss, or open the relevant code/deploy context.