[apm] Update APM docs to reflect changes related to the Elasticsearch apm-data plugin (#4333)

* update getting started docs

* update upgrade guide

* fix build

* audit mentions of the apm integration

* audit mentions of data streams

* audit mentions of index templates

* audit mentions of index mappings

* address feedback from @carsonip

* update diagram

* address more feedback from @carsonip

* update ilm guide

* address more feedback from @lahsivjar

* address more feedback from @lahsivjar

* add link

* fix table formatting

* address more feedback from @lahsivjar

Author: colleenmcginnis

docs/en/observability/apm/configure/general.asciidoc

@@ -173,7 +173,7 @@ Defaults to `debug/vars`.
 === Data stream namespace
 
 Change the default namespace.
-This setting changes the name of the integration's data stream.
+This setting changes the name of the data stream.
 
 For {fleet}-managed users, the namespace is inherited from the selected {agent} policy.
 

docs/en/observability/apm/configure/outputs/console.asciidoc

@@ -26,13 +26,6 @@ output.console:
   pretty: true
 ------------------------------------------------------------------------------
 
-ifdef::apm-server[]
-[float]
-=== {kib} configuration
-
-include::../../shared-kibana-endpoint.asciidoc[tag=shared-kibana-config]
-endif::[]
-
 [float]
 === Configuration options
 

docs/en/observability/apm/configure/outputs/kafka.asciidoc

@@ -37,11 +37,6 @@ output.kafka:
 
 NOTE: Events bigger than <<apm-kafka-max_message_bytes,`max_message_bytes`>> will be dropped. To avoid this problem, make sure APM Server does not generate events bigger than <<apm-kafka-max_message_bytes,`max_message_bytes`>>.
 
-[float]
-=== {kib} configuration
-
-include::../../shared-kibana-endpoint.asciidoc[tag=shared-kibana-config]
-
 [float]
 [[apm-kafka-compatibility]]
 === Compatibility

docs/en/observability/apm/configure/outputs/logstash.asciidoc

@@ -21,7 +21,6 @@ protocol, which runs over TCP.
 To send events to {ls}, you must:
 
 . <<apm-ls-output-config,Enable the {ls} output in APM Server>>
-. <<apm-ls-kib-config,Enable the {kib} endpoint in APM Server>>
 . <<apm-ls-config-pipeline,Create a {ls} configuration pipeline in {ls}>>
 
 [float]
@@ -43,12 +42,6 @@ output.logstash:
 <1> The `hosts` option specifies the {ls} server and the port (`5044`) where {ls} is configured to listen for incoming
 APM Server connections.
 
-[float]
-[[apm-ls-kib-config]]
-=== {kib} endpoint configuration
-
-include::../../shared-kibana-endpoint.asciidoc[tag=shared-kibana-config]
-
 [float]
 [[apm-ls-config-pipeline]]
 === {ls} configuration pipeline

docs/en/observability/apm/configure/outputs/redis.asciidoc

@@ -30,11 +30,6 @@ output.redis:
   timeout: 5
 ------------------------------------------------------------------------------
 
-[float]
-=== {kib} configuration
-
-include::../../shared-kibana-endpoint.asciidoc[tag=shared-kibana-config]
-
 [float]
 === Compatibility
 

docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc

@@ -165,69 +165,6 @@ See <<apm-running-on-docker, Running on Docker>> for deploying Docker containers
 [[apm-server-configuration]]
 == Step 2: Set up and configure
 
-// This content is reused in the upgrading guide
-// tag::why-apm-integration[]
-Starting in version 8.0.0, {fleet} uses the APM integration to set up and manage APM index templates,
-{ilm-init} policies, and ingest pipelines. APM Server will only send data to {es} _after_ the APM integration has been installed.
-// end::why-apm-integration[]
-
-[float]
-=== Install the APM integration
-
-// This content is reused in the upgrading guide
-// tag::install-apm-integration[]
-[%collapsible%open]
-.**If you have an internet connection**
-====
-An internet connection is required to install the APM integration via the {fleet} UI in {kib}.
-
-// lint ignore elastic-agent
-. Open {kib} and select **Add integrations** > **Elastic APM**.
-. Click **APM integration**.
-. Click **Add Elastic APM**.
-. Click **Save and continue**.
-. Click **Add Elastic Agent later**. You do not need to run an {agent} to complete the setup.
-====
-
-// tag::install-apm-integration-no-internet[]
-[%collapsible]
-.**If you don't have an internet connection**
-====
-If your environment has network traffic restrictions, there are other ways to install the APM integration.
-See {fleet-guide}/air-gapped.html[Air-gapped environments] for more information.
-
-Option 1: Update `kibana.yml`::
-+
-Update `kibana.yml` to include the following, then restart {kib}.
-+
-[source,yaml]
-----
-xpack.fleet.packages:
-- name: apm
-  version: latest
-----
-+
-See {kibana-ref}/settings.html[Configure Kibana] to learn more about how to edit the Kibana configuration file.
-
-Option 2: Use the {fleet} API::
-+
-Use the {fleet} API to install the APM integration. To be successful, this needs to be run against the {kib}
-API, not the {es} API.
-+
-["source","yaml",subs="attributes"]
-----
-POST kbn:/api/fleet/epm/packages/apm/{apm_server_version}
-{ "force": true }
-----
-+
-See {kibana-ref}/api.html[Kibana API] to learn more about how to use the Kibana APIs.
-====
-// end::install-apm-integration-no-internet[]
-// end::install-apm-integration[]
-
-[float]
-=== Configure APM
-
 Configure APM by editing the `apm-server.yml` configuration file.
 The location of this file varies by platform--see the <<apm-directory-layout>> for help locating it.
 

docs/en/observability/apm/getting-started-apm/get-started-with-fleet-apm-server.asciidoc

@@ -32,7 +32,7 @@ include::{observability-docs-root}/docs/en/observability/tab-widgets/add-apm-int
 An internet connection is required to install the APM integration via the Fleet UI in Kibana.
 
 --
-include::{observability-docs-root}/docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc[leveloffset=+2,tag=install-apm-integration-no-internet]
+include::{observability-docs-root}/docs/en/observability/apm/shared/install-apm-integration-no-internet.asciidoc[]
 --
 ****
 

docs/en/observability/apm/getting-started-apm/index.asciidoc

@@ -12,9 +12,8 @@ The {es} Service is available on AWS, GCP, and Azure.
 *To get started in minutes, follow the steps in <<get-started-with-fleet-apm-server>>.*
 ****
 
-// TODO: MOVE THIS
-IMPORTANT: Starting in version 8.0.0, {fleet} uses the APM integration to set up and manage APM index templates,
-{ilm-init} policies, and ingest pipelines. APM Server will only send data to {es} _after_ the APM integration has been installed.
+IMPORTANT: Starting in version 8.15.0, the {es} apm-data plugin manages APM index templates,
+lifecycle policies, and ingest pipelines.
 
 The APM Server receives performance data from your APM agents,
 validates and processes it, and then transforms the data into {es} documents.

docs/en/observability/apm/images/bin-ov.png

@@ -20,7 +20,7 @@ See the {fleet-guide}/data-streams.html[{fleet} and {agent} Guide] to learn more
 
 // tag::data-streams[]
 APM data follows the `<type>-<dataset>-<namespace>` naming scheme.
-The `type` and `dataset` are predefined by the APM integration,
+The `type` and `dataset` are predefined by the {es} apm-data plugin,
 but the `namespace` is your opportunity to customize how different types of data are stored in {es}.
 There is no recommendation for what to use as your namespace--it is intentionally flexible.
 For example, you might create namespaces for each of your environments,