Solutions
Trace a stalled operations workflow through its software path.
An energy company's field-operations application starts to feel slow when crews submit work orders. Telemetry from the workflow locates the service handoff where the time goes.
The situation
Field crews use an internal application to open, update and close work orders from sites that do not have strong connections. When submitting an update starts to take noticeably longer, they do not report a latency number. They report that the app is stuck.
The application team gets the message the usual way, second-hand, and an alert on the work-order service confirms that response times have risen.
What the team sees first
Service health for the work-order service shows the rise beginning shortly after the morning shift started, and no deployment in that period. The question becomes where the time is going, since the service itself is not busy.
How the investigation goes
A trace of a slow update shows the work-order service waiting almost the entire time on one call: a request to a service that checks the crew's permissions for the site. That service is healthy on its own, but its own call to an identity store is slow.
The dependency map shows the same chain for every slow request, and logs from the permissions service show it falling back to a full lookup instead of using its cache, starting at the same minute as the rise.
The team can now explain what crews felt: each update was quietly waiting for a lookup that used to be instant.
What gets shared
The team records the affected path, the three services involved, the two traces that show it and the log lines that show the cache falling back. The owner of the permissions service gets a precise request instead of a vague complaint, and the application team can tell the field crews what happened and when it cleared.
What this shows
In operations software, a slow screen is usually a slow handoff somewhere out of sight. Following one request through its dependencies finds that handoff faster than inspecting each service in turn.
These stories are illustrative examples. They describe invented scenarios in an industry, not a real customer, a real incident or any company's systems.
Start with your own services.
A trial workspace is free for 14 days. Send your telemetry and follow your own requests.