Product Guides
Errors
Use Errors to review grouped failing resources, latest examples, and the traces or logs that explain them.
Overview
Use Errors to group repeated failures so you can prioritize real failure patterns and open the best trace or log example instead of chasing isolated exceptions.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Start with the group list to avoid chasing one-off failures. Use latest examples to confirm the error still matches the current symptom. Open related traces and logs when you need the request path and event sequence.
- Group freshness
- Recent examples matter more than stale groups when deciding current incident priority.
- Affected surface
- Service, route, status, and message identify likely ownership and user impact.
- Example quality
- A useful group has a trace or log example that represents the current symptom.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
Open the group with the highest current impact.
- 2
Check latest example, affected service, and route before assigning ownership.
- 3
Open trace detail and logs to see whether the error came from code, a dependency, or a release.
Interpretation note
Do not prioritize old groups only because they have large historical counts. Do not close an error group until recent examples stop matching the symptom. Do not assign ownership before checking the failed span or dependency path.