docs: Update exploring data in {es}

docs/integrations-index.asciidoc

@@ -137,8 +137,6 @@ include::{libbeat-dir}/shared-securing-beat.asciidoc[leveloffset=+1]
 
 include::{libbeat-dir}/monitoring/monitoring-beats.asciidoc[leveloffset=+1]
 
-include::./legacy/exploring-es-data.asciidoc[leveloffset=+1]
-
 include::./legacy/troubleshooting.asciidoc[leveloffset=+1]
 
 // include::./legacy/breaking-changes.asciidoc[leveloffset=+1]

docs/legacy/exploring-es-data.asciidoc

@@ -1,58 +1,16 @@
 [[exploring-es-data]]
 = Explore data in {es}
 
-Elastic APM data is stored in data streams.
-include::../data-streams.asciidoc[tag=data-streams]
-
-The namespace default is `default`.
-To configure a custom namespace, set `data_streams.namespace`:
-
-[source,yaml]
-----
-apm-server:
-  data_streams.namespace: custom_namespace
-----
-
-[discrete]
-[[apm-data-streams-list-standalone]]
-== APM data streams
-
-By type, the APM data streams are:
-
-Traces::
-Traces are comprised of {apm-guide-ref}/data-model.html[spans and transactions].
-Traces are stored in the following data streams:
-+
-include::../data-streams.asciidoc[tag=traces-data-streams]
-
-Metrics::
-Metrics include application-based metrics, aggregation metrics, and basic system metrics.
-Metrics are stored in the following data streams:
-+
-include::../data-streams.asciidoc[tag=metrics-data-streams]
-
-Logs::
-Logs include application error events and application logs.
-Logs are stored in the following data streams:
-+
-include::../data-streams.asciidoc[tag=logs-data-streams]
-
-[float]
-[[sample-apm-document]]
-== Sample APM documents
-
-Sample documents for each of the APM event types are available on these pages:
-
-* <<transaction-indices>>
-* <<span-indices>>
-* <<error-indices>>
+* <<elasticsearch-query-examples>>
+* <<sample-apm-document>>
 * <<metricset-indices>>
-* <<sourcemap-indices>>
 
 [float]
 [[elasticsearch-query-examples]]
 == {es} query examples
 
+Elastic APM data is stored in <<apm-data-streams>>.
+
 The following examples enable you to interact with {es}'s REST API.
 One possible way to do this is using {kib}'s
 {kibana-ref}/console-kibana.html[{dev-tools-app} console].
@@ -90,9 +48,60 @@ GET  /_template/your-template-name
 ----
 // CONSOLE
 
+[float]
+[[sample-apm-document]]
+== Sample APM documents
+
+Sample documents for each of the APM event types are available below:
+
+[%collapsible]
+.Transaction documents
+====
+Example transaction documents indexed in {es}:
+
+[source,json]
+----
+include::../data/elasticsearch/generated/transactions.json[]
+----
+====
+
+[%collapsible]
+.Span documents
+====
+Example span documents indexed in {es}:
+
+[source,json]
+----
+include::../data/elasticsearch/generated/spans.json[]
+----
+====
+
+[%collapsible]
+.Error documents
+====
+Example error documents indexed in {es}:
+
+[source,json]
+----
+include::../data/elasticsearch/generated/errors.json[]
+----
+====
+
+[%collapsible]
+.Metric document
+====
+include::./metricset-indices.asciidoc[tag=example]
+====
+
+[%collapsible]
+.Source map documents
+====
+Example source map document indexed in {es}:
+
+[source,json]
+----
+include::../data/intake-api/generated/sourcemap/bundle.js.map[]
+----
+====
 
-include::./transaction-indices.asciidoc[]
-include::./span-indices.asciidoc[]
-include::./error-indices.asciidoc[]
-include::./metricset-indices.asciidoc[]
-include::./sourcemap-indices.asciidoc[]
+include::./metricset-indices.asciidoc[]

docs/legacy/metricset-indices.asciidoc

@@ -1,9 +1,5 @@
 [[metricset-indices]]
-== Metrics documents
-
-++++
-<titleabbrev>Metrics documents</titleabbrev>
-++++
+== Application metrics
 
 APM Server stores application metrics sent by agents as documents in {es}.
 Metric documents contain a timestamp, one or more metric fields,
@@ -129,6 +125,7 @@ The `@timestamp` field of these documents holds the start of the aggregation int
 [[example-metric-document]]
 === Example metric document
 
+// tag::example[]
 Below is an example of a metric document as stored in {es}, containing JVM metrics produced by the {apm-java-agent}.
 The document contains two related metrics: `jvm.gc.time` and `jvm.gc.count`. These are accompanied by various fields describing
 the environment in which the metrics were captured: service name, host name, Kubernetes pod UID, container ID, process ID, and more.
@@ -138,3 +135,4 @@ These fields make it possible to search and aggregate across various dimensions,
 ----
 include::../data/elasticsearch/metricset.json[]
 ----
+// end::example[]

docs/manage-storage.asciidoc

@@ -208,3 +208,5 @@ POST /.ds-*-apm*/_update_by_query?expand_wildcards=all
 TIP: Remember to also change the service name in the {apm-agents-ref}/index.html[{apm-agent} configuration].
 
 include::./apm-tune-elasticsearch.asciidoc[]
+
+include::./legacy/exploring-es-data.asciidoc[leveloffset=+2]