mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
7b0d842096
Closes https://github.com/elastic/observability-docs/issues/3292 ## Summary Updates documentation related to the APM UI based on issues found during the Observability docs bug bash last week. ### Checklist Delete any items that are not applicable to this PR. - [x] @colleenmcginnis [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials: - [x] Clarify that distributed traces aren't the only colorful traces in [Trace sample timeline](https://www.elastic.co/guide/en/kibana/current/spans.html#distributed-tracing) (b707c3936b) - [x] Clarify the implications of the traces table only showing root transactions in [Traces](https://www.elastic.co/guide/en/kibana/current/traces.html) (c1de678f91) - [x] Add beta admonition to APM [Infrastucture](https://www.elastic.co/guide/en/kibana/current/infrastructure.html) page (d3bc4a972d) - [x] @bmorelli25 review
40 lines
1.9 KiB
Text
40 lines
1.9 KiB
Text
[role="xpack"]
|
|
[[traces]]
|
|
=== Traces
|
|
|
|
TIP: Traces link together related transactions to show an end-to-end performance of how a request was served
|
|
and which services were part of it.
|
|
In addition to the Traces overview, you can view your application traces in the <<spans,trace sample timeline waterfall>>.
|
|
|
|
*Traces* displays your application's entry (root) transactions.
|
|
Transactions with the same name are grouped together and only shown once in this table.
|
|
If you're using <<distributed-tracing,distributed tracing>>,
|
|
this view is key to finding the critical paths within your application.
|
|
|
|
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, select it to view its
|
|
<<transaction-details,transaction details>>.
|
|
|
|
You can also use queries to filter and search the transactions shown on this page.
|
|
Note that only properties available on root transactions are searchable.
|
|
For example, you can't search for `label.tier: 'high'`, as that field is only available on non-root transactions.
|
|
|
|
[role="screenshot"]
|
|
image::apm/images/apm-traces.png[Example view of the Traces overview in APM app in Kibana]
|
|
|
|
[float]
|
|
[[trace-explorer]]
|
|
==== Trace explorer
|
|
|
|
preview::[]
|
|
|
|
**Trace explorer** is an experimental top-level search tool that allows you to query your traces using <<kuery-query,Kibana Query Language (KQL)>> or {ref}/eql.html[Event Query Language (EQL)].
|
|
|
|
Curate your own custom queries, or use the <<service-maps,**Service Map**>> to find and select edges to automatically generate queries based on your selection:
|
|
|
|
[role="screenshot"]
|
|
image::apm/images/trace-explorer.png[Trace explorer]
|
|
|
|
Enable **Trace explorer** in <<apm-labs,APM Labs>> or in <<observability-apm-trace-explorer-tab,{kib} advanced settings>>.
|