Error tracking in Osuite
Osuite surfaces errors from the spans your services already send — any span marked with an error status, and any exception recorded on a span, feeds error tracking. No separate error-reporting SDK is required.
Error groups
Section titled “Error groups”Individual errors are noisy, so Osuite groups them. Errors are collapsed by exception type and by a fingerprint of the stack trace, so the same failure raised across thousands of requests appears as one group. For each group you see:
- the exception type and message
- the endpoint or operation it originates from
- how often it occurs, and whether it is trending up or down over time
From an error to its trace
Section titled “From an error to its trace”Each error group links directly to example traces that hit it. Open one to land in the Trace Explorer on the exact request that failed, with the failing span and its attributes in context. From there you can read the logs correlated to that span to see what the service logged as it failed.
Related
Section titled “Related”- APM overview — golden signals and the error-rate signal per service.
- Trace Explorer — inspect the failing request span by span.