Product Guides
Service Detail
Use service detail as the main workspace for one service: endpoints, external calls, dependencies, traces, logs, runtime, errors, and versions.
Overview
Use Service Detail as the investigation workbench for one service. It keeps endpoints, external calls, dependencies, traces, logs, runtime pressure, errors, and versions in the same service context.
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
Use overview cards for the current service snapshot, then move into the relevant tab. Use Endpoints for inbound request behavior and External calls for outbound dependency behavior. Use Dependencies, Traces, Logs, Runtime, Errors, and Versions to collect evidence without leaving the service context.
- Endpoint behavior
- Inbound routes show whether user-facing requests are slower, failing, or changing traffic shape.
- External calls
- Outbound behavior shows whether the service is waiting on another service or external dependency.
- Local pressure
- Runtime, logs, errors, and versions show whether the issue is inside this service or near a release.
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 service from Services after noticing elevated latency.
- 2
Check Endpoints first. If one route dominates, open recent traces for that route.
- 3
If traces show broad delay, compare Runtime and Logs for the same time window.
Interpretation note
Do not read service-level latency without checking which endpoint caused it. Do not treat external call latency as application code latency. Do not mix versions when judging whether a deployment caused a regression.