Traces and requestsCopy Anchor Link

Requests (/observability/requests) lists HTTP and RPC spans for API services. Spans (/observability/spans) supports broader trace search when you already have a trace or span ID.

Requests listCopy Anchor Link

Each row summarizes latency, status, route, and service. Open a row to see:

• Waterfall — parent and child spans with timing bars.
• Services graph — upstream/downstream calls for that trace.
• Logs — log lines sharing the trace ID (when log-trace correlation is enabled).

ScopeCopy Anchor Link

Filter by Service to match the Home services card you clicked. Environment and time range use the same URL parameters as Logs.

Service mapCopy Anchor Link

For topology across many services, use Service map (/observability/service-map). Edge colour reflects error rate and latency between nodes.

SDK setupCopy Anchor Link

Ensure your SDK or collector exports OTLP traces with service.name and HTTP semantic conventions. Language guides live under SDKs.