Follow one request across every service it touches, including the background job your web request just enqueued. Now in beta for Ruby, Python, and PHP.
We've added a service map and updated the trace timeline on the trace detail page.
The service map shows a trace from the perspective of the services that took part: which services the request reached, and how long each call between them took. Edges are colored by how each call rates against the trace's own baseline, so the slowest calls stand out without you reading every duration. It appears once a trace crosses more than one service.
Above: one checkout across nine services. The dashed lines show work linked from another trace.
The updated trace timeline lays every span out over time, including spans that came from a different service, so you can see where the time went.
To turn it on, point collector_endpoint at a hosted collector and give each app its own service_name. PHP and custom OpenTelemetry setups already report through a collector, so there's nothing to switch on. Ruby also needs the AppSignal for Ruby 5.0 pre-release and the appsignal-opentelemetry gem. Elixir and Node.js aren't supported yet.
Read the distributed tracing docs to set it up, or the Ruby specifics for the integrations that carry the trace for you. Part of AppSignal Labs.
