mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 01:13:23 -04:00
2c93de6bd5
# Backport This will backport the following commits from `main` to `8.9`: - [[APM] UX text review (#161400)](https://github.com/elastic/kibana/pull/161400) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Brandon Morelli","email":"brandon.morelli@elastic.co"},"sourceCommit":{"committedDate":"2023-07-07T14:41:46Z","message":"[APM] UX text review (#161400)\n\n## Summary\r\n\r\n@gchaps and I met to review text on some APM UI pages. Outcomes:\r\n\r\n1. Service **m**ap or Service **M**ap — there is inconsistency in the\r\nAPM UI with how we refer to Service maps. In some cases, we use title\r\ncase (Service Map). In others, we use sentence case (Service map). As\r\nper the [EUI writing\r\nguidelines](https://eui.elastic.co/#/guidelines/writing/guidelines#capitalization),\r\nwe should use title case for product features.\r\n2. Storage **e**xplorer or Storage **E**xplorer — same story here. We\r\nuse title case sometimes and sentence case others. We should use title\r\ncase as this is a product feature.\r\n3. Various text enhancements and changes.","sha":"3ced121be0caeb672a4b12c9db595fdde401d80f","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Team:APM","Team:uptime","release_note:skip","ui-copy","v8.9.0","v8.10.0"],"number":161400,"url":"https://github.com/elastic/kibana/pull/161400","mergeCommit":{"message":"[APM] UX text review (#161400)\n\n## Summary\r\n\r\n@gchaps and I met to review text on some APM UI pages. Outcomes:\r\n\r\n1. Service **m**ap or Service **M**ap — there is inconsistency in the\r\nAPM UI with how we refer to Service maps. In some cases, we use title\r\ncase (Service Map). In others, we use sentence case (Service map). As\r\nper the [EUI writing\r\nguidelines](https://eui.elastic.co/#/guidelines/writing/guidelines#capitalization),\r\nwe should use title case for product features.\r\n2. Storage **e**xplorer or Storage **E**xplorer — same story here. We\r\nuse title case sometimes and sentence case others. We should use title\r\ncase as this is a product feature.\r\n3. Various text enhancements and changes.","sha":"3ced121be0caeb672a4b12c9db595fdde401d80f"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161400","number":161400,"mergeCommit":{"message":"[APM] UX text review (#161400)\n\n## Summary\r\n\r\n@gchaps and I met to review text on some APM UI pages. Outcomes:\r\n\r\n1. Service **m**ap or Service **M**ap — there is inconsistency in the\r\nAPM UI with how we refer to Service maps. In some cases, we use title\r\ncase (Service Map). In others, we use sentence case (Service map). As\r\nper the [EUI writing\r\nguidelines](https://eui.elastic.co/#/guidelines/writing/guidelines#capitalization),\r\nwe should use title case for product features.\r\n2. Storage **e**xplorer or Storage **E**xplorer — same story here. We\r\nuse title case sometimes and sentence case others. We should use title\r\ncase as this is a product feature.\r\n3. Various text enhancements and changes.","sha":"3ced121be0caeb672a4b12c9db595fdde401d80f"}}]}] BACKPORT--> Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
36 lines
1.6 KiB
Text
36 lines
1.6 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>>.
|
|
|
|
[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>>.
|