[8.10](backport #3476) [apm docs consolidation] Clean up (#3493)

* [apm docs consolidation] Clean up (#3476) * use tagged regions for release notes * rename apm-breaking, point to apm-server * remove data and spec directories, point to apm-server (cherry picked from commit d4309b5) # Conflicts: # docs/en/apm-server/apm-breaking.asciidoc # docs/en/apm-server/release-notes.asciidoc * fix conflicts --------- Co-authored-by: Colleen McGinnis <[email protected]>
elastic · Dec 21, 2023 · fb47825 · fb47825
1 parent ec3d887
commit fb47825
Show file tree

Hide file tree

Showing 34 changed files with 20 additions and 9,139 deletions.
diff --git a/docs/en/apm-server/api-error.asciidoc b/docs/en/apm-server/api-error.asciidoc
@@ -12,5 +12,5 @@ APM Server uses JSON Schema to validate requests. The specification for errors i
 
 [source,json]
 ----
-include::./spec/v2/error.json[]
+include::{apm-server-root}/docs/spec/v2/error.json[]
 ----
diff --git a/docs/en/apm-server/api-event-example.asciidoc b/docs/en/apm-server/api-event-example.asciidoc
@@ -5,5 +5,5 @@ A request body example containing one event for all currently supported event ty
 
 [source,json]
 ----
-include::./data/intake-api/generated/events.ndjson[]
+include::{apm-server-root}/docs/data/intake-api/generated/events.ndjson[]
 ----
diff --git a/docs/en/apm-server/api-metadata.asciidoc b/docs/en/apm-server/api-metadata.asciidoc
@@ -62,5 +62,5 @@ APM Server uses JSON Schema to validate requests. The specification for metadata
 
 [source,json]
 ----
-include::./spec/v2/metadata.json[]
+include::{apm-server-root}/docs/spec/v2/metadata.json[]
 ----
diff --git a/docs/en/apm-server/api-metricset.asciidoc b/docs/en/apm-server/api-metricset.asciidoc
@@ -12,5 +12,5 @@ APM Server uses JSON Schema to validate requests. The specification for metrics
 
 [source,json]
 ----
-include::./spec/v2/metricset.json[]
+include::{apm-server-root}/docs/spec/v2/metricset.json[]
 ----
diff --git a/docs/en/apm-server/api-span.asciidoc b/docs/en/apm-server/api-span.asciidoc
@@ -12,5 +12,5 @@ APM Server uses JSON Schema to validate requests. The specification for spans is
 
 [source,json]
 ----
-include::./spec/v2/span.json[]
+include::{apm-server-root}/docs/spec/v2/span.json[]
 ----
diff --git a/docs/en/apm-server/api-transaction.asciidoc b/docs/en/apm-server/api-transaction.asciidoc
@@ -12,5 +12,5 @@ APM Server uses JSON Schema to validate requests. The specification for transact
 
 [source,json]
 ----
-include::./spec/v2/transaction.json[]
+include::{apm-server-root}/docs/spec/v2/transaction.json[]
 ----
diff --git a/docs/en/apm-server/data-model.asciidoc b/docs/en/apm-server/data-model.asciidoc
@@ -88,7 +88,7 @@ This example shows what span documents can look like when indexed in {es}.
 ====
 [source,json]
 ----
-include::./data/elasticsearch/generated/spans.json[]
+include::{apm-server-root}/docs/data/elasticsearch/generated/spans.json[]
 ----
 ====
 
@@ -159,7 +159,7 @@ This example shows what transaction documents can look like when indexed in {es}
 ====
 [source,json]
 ----
-include::./data/elasticsearch/generated/transactions.json[]
+include::{apm-server-root}/docs/data/elasticsearch/generated/transactions.json[]
 ----
 ====
 
@@ -212,7 +212,7 @@ This example shows what error documents can look like when indexed in {es}.
 ====
 [source,json]
 ----
-include::./data/elasticsearch/generated/errors.json[]
+include::{apm-server-root}/docs/data/elasticsearch/generated/errors.json[]
 ----
 ====
 
@@ -265,7 +265,7 @@ These fields make it possible to search and aggregate across various dimensions,
 
 [source,json]
 ----
-include::./data/elasticsearch/metricset.json[]
+include::{apm-server-root}/docs/data/elasticsearch/metricset.json[]
 ----
 ====
 
@@ -315,7 +315,7 @@ This example shows what breakdown metric documents can look like when indexed in
 
 [source,json]
 ----
-include::./data/elasticsearch/span_breakdown.json[]
+include::{apm-server-root}/docs/data/elasticsearch/span_breakdown.json[]
 ----
 ====
 
@@ -386,7 +386,7 @@ This example shows what transaction documents can look like when indexed in {es}
 
 [source,json]
 ----
-include::./data/elasticsearch/transaction_metric.json[]
+include::{apm-server-root}/docs/data/elasticsearch/transaction_metric.json[]
 ----
 ====
 
@@ -432,7 +432,7 @@ This example shows what service-transaction documents can look like when indexed
 
 [source,json]
 ----
-include::./data/elasticsearch/service_transaction_metric.json[]
+include::{apm-server-root}/docs/data/elasticsearch/service_transaction_metric.json[]
 ----
 ====
 
@@ -480,7 +480,7 @@ This example shows what service-destination documents can look like when indexed
 
 [source,json]
 ----
-include::./data/elasticsearch/service_destination_metric.json[]
+include::{apm-server-root}/docs/data/elasticsearch/service_destination_metric.json[]
 ----
 ====
 
@@ -515,7 +515,7 @@ This example shows what service-summary documents can look like when indexed in
 
 [source,json]
 ----
-include::./data/elasticsearch/service_summary_metric.json[]
+include::{apm-server-root}/docs/data/elasticsearch/service_summary_metric.json[]
 ----
 ====