See what the API is doing.
Track latency, errors, and throughput for the operations your services report. When something slows down, open the related traces and inspect which calls took the time.
operation
mutation checkout
p99
318ms▲ 7.6×
p95
42ms
throughput
1.2k/m
errors
0.3%
OpenTelemetry-native, end to end.
Configured services export supported traces, metrics, and logs over plain OTLP. Nitro links reported operation signals to the related distributed traces for investigation.
- Vendor-neutral OTLP in, no proprietary agent
- Hot Chocolate is auto-instrumented
- Works with any OpenTelemetry backend, not just Nitro
builder.Services
.AddNitro()
.AddOpenTelemetry();
builder.Services
.AddGraphQLServer()
.AddInstrumentation();What’s slow. How bad.
And for whom.
Rank operations to investigate with the impact score.
The impact score combines traffic, latency, and error rate to help you decide which reported operations to investigate first.
Operations
ranked by impact · last 1h
The whole latency picture, not an average.
An average can look healthy while a small number of requests are much slower. Percentiles show you where the tail starts, so you can find and fix those slow paths before they affect more users.
Latency · checkout
p95 / p99 · ms
- p99
- 318ms
- p95
- 42ms
- throughput
- 1.2k/m
- error rate
- 0.31%
Know which identified clients are affected.
See which client apps and versions are behind an operation. When one starts causing trouble, you can tell whether it affects everyone or only a particular client.
Clients · checkout
share of impact
Move from a metric spike to the related traces.
Follow one request through its reported trace.
Open the trace waterfall to inspect the services and spans that reported timing for one request, including which calls contributed the most latency.
Inspect the trace behind a failed operation.
When errors spike, open the failing operation and inspect its traces, spans, and captured exception details without correlating logs by hand.
The whole story, from spike to span.
Follow an incident from the latency chart to the affected operation and down to the spans behind it, without leaving Nitro.