The Services dashboard
Requests, errors and latency for every service and route, from their server spans: what every instrumented service sends, whatever its language.
Who it is for: On-call engineers and the owners of each service.
Open it from Dashboards in the Observatory: choose Services. It is a built-in board, so it is read-only; Save a copy makes one you can change. How every panel reads the range, its colors and its empty states is on Reading a board.
The toolbar: the filters Service, each All until you pick a value, and the time range. Each menu lists the values http.server.request.duration carries in the range. Each panel below names the filters that narrow it.
Overview
Server spans
Server spans in this range: one per request served, of the traces kept.
- How it is computed: The number of server spans (span kind server). One figure for the whole picked range.
- Better: Higher is better. Beside the figure, its change from the prior range of the same length: green when it moved the better way, red when it moved the other way.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Server spans in error
The share of server spans that ended in an error.
- How it is computed: Server spans that ended in an error, divided by all server spans, as a percent. One figure for the whole picked range.
- Better: Lower is better. Beside the figure, its change from the prior range of the same length: green when it moved the better way, red when it moved the other way.
- Colors: The figure turns amber above 1% and red above 5%.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Server span duration (p95)
How long server spans take at the 95th percentile.
- How it is computed: The 95th percentile duration of server spans. One figure for the whole picked range.
- Better: Lower is better. Beside the figure, its change from the prior range of the same length: green when it moved the better way, red when it moved the other way.
- Colors: The figure turns amber above 500 ms and red above 2 s.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Services with server spans
Services that sent a server span in this range.
- How it is computed: Distinct
service.namevalues on server spans. One figure for the whole picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
By service
Server spans per second by service
Server spans per second for each service.
- How it is computed: The per-second rate of server spans, one line per
service.name. Lines, one point per step across the picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
Server span duration by service (p95)
How long each service's server spans take at the 95th percentile.
- How it is computed: The 95th percentile duration of server spans, one line per service. Lines, one point per step across the picked range.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Server spans in error by service
The share of each service's server spans that ended in an error, each step.
- How it is computed: Server spans that ended in an error, divided by all server spans, per service, as a percent. Lines, one point per step across the picked range.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Responses by status code
Server spans by the status code they answered.
- How it is computed: Server spans, counted per
http.response.status_code. A ranked list, each figure for the whole picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
Error spans by service
The services with the most error spans.
- How it is computed: Server spans that ended in an error, counted per service. A ranked list, each figure for the whole picked range.
- Filters: Service narrows it.
- Opens: its title opens Traces.
Routes
Slowest routes by server span (p95)
The routes with the slowest server spans at the 95th percentile.
- How it is computed: The 95th percentile duration of server spans per
http.route, the top ten. A ranked list, each figure for the whole picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
Busiest routes
The routes with the most server spans.
- How it is computed: Server spans, counted per
http.route, the top ten. A ranked list, each figure for the whole picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
Error spans by route
The routes with the most error spans.
- How it is computed: Server spans that ended in an error, counted per
http.route, the top ten. A ranked list, each figure for the whole picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.
Server spans per second by route
Server spans per second for the six busiest routes, each step.
- How it is computed: The per-second rate of server spans, one line per
http.route. Lines, one point per step across the picked range. - Filters: Service narrows it.
- Opens: its title opens Traces.