add traces

Author: mdbirnstiehl

raw-migrated-files/docs-content/serverless/observability-apm-traces.md

@@ -217,7 +217,6 @@ toc:
       - file: docs-content/serverless/observability-apm-act-on-data.md
       - file: docs-content/serverless/observability-apm-agents-elastic-apm-agents.md
       - file: docs-content/serverless/observability-apm-get-started.md
-      - file: docs-content/serverless/observability-apm-traces.md
       - file: docs-content/serverless/observability-ecs-application-logs.md
       - file: docs-content/serverless/observability-plaintext-application-logs.md
       - file: docs-content/serverless/observability-stream-log-files.md
@@ -445,7 +444,6 @@ toc:
       - file: observability-docs/observability/apm-act-on-data.md
       - file: observability-docs/observability/apm-agents.md
       - file: observability-docs/observability/apm-getting-started-apm-server.md
-      - file: observability-docs/observability/apm-traces.md
       - file: observability-docs/observability/index.md
       - file: observability-docs/observability/obs-ai-assistant.md
   - file: security-docs/security/index.md

raw-migrated-files/observability-docs/observability/apm-traces.md

@@ -4,11 +4,37 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-traces.html
 ---
 
-# Traces
+# Traces [apm-traces]
 
-% What needs to be done: Align serverless/stateful
+::::{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 [trace sample timeline waterfall](../../../solutions/observability/apps/trace-sample-timeline.md).
+::::
 
-% Use migrated content from existing pages that map to this page:
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/apm-traces.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-traces.md
+**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](../../../solutions/observability/apps/trace-sample-timeline.md#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](../../../solutions/observability/apps/transactions-2.md#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.
+
+:::{image} ../../../images/observability-apm-traces.png
+:alt: Example view of the Traces overview in Applications UI in Kibana
+:class: screenshot
+:::
+
+
+## Trace explorer [trace-explorer]
+
+::::{warning}
+This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
+::::
+
+
+**Trace explorer** is an experimental top-level search tool that allows you to query your traces using [{{kib}} Query Language (KQL)](../../../explore-analyze/query-filter/languages/kql.md) or [Event Query Language (EQL)](../../../explore-analyze/query-filter/languages/eql.md).
+
+Curate your own custom queries, or use the [**Service Map**](../../../solutions/observability/apps/service-map.md) to find and select edges to automatically generate queries based on your selection:
+
+:::{image} ../../../images/observability-trace-explorer.png
+:alt: Trace explorer
+:class: screenshot
+:::