93faa5fbc3
* docs: initial APM UI updates * docs: using-the-apm-ui updates * more docs updates * quick edits * docs: apply feedback and fix screenshots * docs: incorporate feedback, bold page names * finishing touches and clean up * docs: incorporate feedback from sarah * docs: add feedback * docs: incorporate feedback from gchaps
36 lines
1.9 KiB
Plaintext
36 lines
1.9 KiB
Plaintext
[[traces]]
|
||
=== Traces overview
|
||
|
||
The *Traces* overview displays the entry transaction for all traces in your application.
|
||
If you're using <<distributed-tracing>>, this view is key to finding the critical paths within your application.
|
||
Transactions with the same name are grouped together and only shown once in this table.
|
||
|
||
By default, transactions are sorted by _Impact_.
|
||
Impact helps show the most used and slowest endpoints in your service - in other words,
|
||
it's the collective amount of pain a specific endpoint is causing your users.
|
||
If there's a particular endpoint you're worried about, you can click on it to view the <<transaction-details, transaction details>>.
|
||
|
||
[role="screenshot"]
|
||
image::apm/images/apm-traces.png[Example view of the Traces overview in APM UI in Kibana]
|
||
|
||
[float]
|
||
[[distributed-tracing]]
|
||
==== Distributed tracing
|
||
|
||
Elastic APM supports distributed tracing.
|
||
Distributed tracing is a key feature of modern application performance monitoring as application architectures are shifting from monolithic to more distributed,
|
||
service-based architectures.
|
||
|
||
Distributed tracing allows APM users to automatically trace requests all the way through the service architecture,
|
||
and visualize those traces in one single view in the APM UI.
|
||
This is accomplished by tracing all of the requests, from the initial web request to your front-end service,
|
||
to queries made to your back-end services.
|
||
This makes finding possible bottlenecks throughout your application much easier and faster.
|
||
|
||
By definition, a distributed trace includes more than one transaction.
|
||
You can use the <<spans,span timeline visualization>> to view a waterfall display of all of the transactions from individual services that are connected in a trace.
|
||
|
||
[role="screenshot"]
|
||
image::apm/images/apm-distributed-tracing.png[Example view of the distributed tracing in APM UI in Kibana]
|
||
|
||
TIP: Distributed tracing is supported by all APM agents and there’s no additional configuration needed. |