Source
APM, tracing & profiling — found from sitemap — AppSignal
Checked for AppSignal on 6 Nov 2026
- Page
- https://docs.appsignal.com/distributed-tracing
- Checked
- 6 Nov 2026, 04:19 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b32175dae9177d951f8938a53b99e03f3aa793d0e2100b8ef16e1ad74fcc07ee
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Distributed tracing purpose Report an error
“Distributed tracing lets you follow that one request across those boundaries. AppSignal groups the work from every service into one trace, so you can see the full path before you start comparing timestamps across apps.”
-
Distributed tracing basis Report an error
“AppSignal builds traces on top of OpenTelemetry, so these terms line up with OpenTelemetry’s.”
-
Distributed tracing language support Report an error
“Distributed tracing is available through AppSignal integrations for Python, Ruby, and PHP, and through OpenTelemetry for Go and Java. Elixir and Node.js are not supported yet.”
-
Distributed tracing beta Report an error
“Distributed tracing is a beta AppSignal Labs feature, only available when using the AppSignal hosted collector.”
-
Browser trace start Report an error
“In the browser, AppSignal for Browser starts the trace for requests to your API.”
-
Ruby collector requirements Report an error
“Collector mode arrived in AppSignal for Ruby 5.0 and needs the appsignal-opentelemetry gem alongside it, on Ruby 3.1 or newer.”
-
Trace page views Report an error
“open the trace page to inspect them in two ways: the service map, which shows the services in the trace and the calls between them, and the trace timeline, which lays every span out over time.”
-
Cross application traces Report an error
“a single trace can also cross services that belong to entirely separate applications.”
-
Service map cross application errors Report an error
“The service map on an error trace also shows services that report to another application in your organization by name. You see this on the error trace page and in the browser error side panel.”
-
Sampling behavior Report an error
“Sampling favors the traces you most want to see, the ones with errors and the slowest requests.”
-
Service name config Report an error
“You name a service with the service_name option (or the APPSIGNAL_SERVICE_NAME environment variable), and AppSignal uses that name to tell services apart in a trace.”
-
Browser trace propagation Report an error
“Browser: set tracePropagationTargets to your API hosts. Each matching request carries a traceparent header.”
-
Trace log linking Report an error
“Link traces with logs Connect a trace to its related logs so you can move between them while debugging.”
-
Custom instrumentation Report an error
“Custom instrumentation Add your own spans and attributes when the default instrumentation is not enough.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Agency Tech Lead APM, tracing & profiling
- The Data Protection Officer APM, tracing & profiling
- The Mobile Team Lead APM, tracing & profiling
- The SaaS CTO APM, tracing & profiling
- The SaaS CTO Data scrubbing, retention & volume control
- The Skeptic APM, tracing & profiling
- The Site Reliability Engineer APM, tracing & profiling