Follow the signal.

One request, seen from every useful angle.

Amber light travels through connected optical fibers on a graphite laboratory bench
Developer workflowService context

Back to capabilities

Service context

Service context

Keep relationships visible as you investigate.

Keep relationships visible as you investigate.

A duration becomes more useful when it has an owner and a place in the system. Record the service, operation and relationship to the parent request. This helps distinguish time spent doing work from time spent waiting for a dependency. Build an investigation around a specific question: which component changed, what evidence would support that explanation, and who can test it? Keep environmental differences visible rather than comparing unrelated requests. Before connecting an actual observability system, agree on instrumentation, data access, redaction and retention. Product integration and deployment details belong in the implementation plan.

tracepilot.REQUEST WORKSPACE
Request / service map/ request 4a7bc8184 ms
092 ms184 ms
Parent / child relationshipSample trace
SERVICE CONTEXT

api.gateway

service.namegateway
duration184 ms
parent requestapi.gateway

The request enters the gateway. Keep its full path in view.

Read the full request

Create a free website with Framer, the website builder loved by startups, designers and agencies.