reorganize solutions/observability/apm/ files along team lines

Author: colleenmcginnis

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md

@@ -18,7 +18,7 @@ Starting in {{stack}} version 8.0, how you change APM settings and the settings
 :   New deployments created in {{stack}} version 8.0 and later will be managed by {{fleet}}.
 
     * This mode requires SSL/TLS configuration. Check [TLS configuration for {{fleet}}-managed mode](#ece-edit-apm-fleet-tls) for details.
-    * Check [APM integration input settings](/solutions/observability/apm/configure-apm-server.md) for all other Elastic APM configuration options in this mode.
+    * Check [APM integration input settings](/solutions/observability/apm/apm-server/configure.md) for all other Elastic APM configuration options in this mode.
 
 
 Standalone APM Server (legacy)
@@ -45,7 +45,7 @@ Pick one of the following options:
 {{ece}} supports most of the legacy APM settings. Through a YAML editor in the console, you can append your APM Server properties to the `apm-server.yml` file. Your changes to the configuration file are read on startup.
 
 ::::{important}
-Be aware that some settings could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the [latest APM settings and syntax](/solutions/observability/apm/configure-apm-server.md).
+Be aware that some settings could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the [latest APM settings and syntax](/solutions/observability/apm/apm-server/configure.md).
 ::::
 
 

deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md

@@ -24,7 +24,7 @@ This section covers the following topics:
 APM Agent central configuration was added in 7.5.1.
 :::
 
-[APM Agent configuration management](/solutions/observability/apm/apm-agent-central-configuration.md) allows you to configure your APM Agents centrally from the {{kib}} APM app. To use this feature, the APM Server needs to be configured with connection details of the {{kib}} instance. If {{kib}} is managed by ECK, you can simply add a `kibanaRef` attribute to the APM Server specification:
+[APM Agent configuration management](/solutions/observability/apm/apm-server/apm-agent-central-configuration.md) allows you to configure your APM Agents centrally from the {{kib}} APM app. To use this feature, the APM Server needs to be configured with connection details of the {{kib}} instance. If {{kib}} is managed by ECK, you can simply add a `kibanaRef` attribute to the APM Server specification:
 
 ```yaml subs=true
 cat <<EOF | kubectl apply -f -
@@ -112,7 +112,7 @@ The APM Server keystore can be used to store sensitive settings in the APM Serve
             password: "${ES_PASSWORD}"
     ```
 
-3. Reference the key in the APM Server configuration, as described in the [Secrets keystore for secure settings](/solutions/observability/apm/secrets-keystore-for-secure-settings.md).
+3. Reference the key in the APM Server configuration, as described in the [Secrets keystore for secure settings](/solutions/observability/apm/apm-server/secrets-keystore-for-secure-settings.md).
 
 
 ## Reference an existing {{es}} cluster [k8s-apm-existing-es]

deploy-manage/deploy/cloud-on-k8s/use-an-elasticsearch-cluster-managed-by-eck.md

@@ -10,7 +10,7 @@ products:
 
 # Use an {{es}} cluster managed by ECK [k8s-apm-eck-managed-es]
 
-Managing APM Server, {{kib}} and {{es}} with ECK allows a smooth and secured integration between the stack components. The output configuration of the APM Server is setup automatically to establish a trust relationship with {{es}}. Specifying the {{kib}} reference allows ECK to automatically configure the [{{kib}} endpoint](/solutions/observability/apm/configure-kibana-endpoint.md).
+Managing APM Server, {{kib}} and {{es}} with ECK allows a smooth and secured integration between the stack components. The output configuration of the APM Server is setup automatically to establish a trust relationship with {{es}}. Specifying the {{kib}} reference allows ECK to automatically configure the [{{kib}} endpoint](/solutions/observability/apm/apm-server/configure-kibana-endpoint.md).
 
 1. To deploy an APM Server and connect it to the {{es}} cluster and {{kib}} instance you created in [](/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md), apply the following specification:
 

deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md

@@ -109,7 +109,7 @@ This table compares Observability capabilities between {{ech}} deployments and O
 |---------|----------------------|-----------------------------------|------------------|
 | [**AI Assistant**](/solutions/observability/observability-ai-assistant.md) | ✅ | ✅ | |
 | **APM integration** | ✅ | ✅ | Use **Managed Intake Service** (supports Elastic APM and OTLP protocols) <br> Refer to [Managed OTLP endpoint](opentelemetry://reference/motlp.md) for OTLP data ingestion |
-| [**APM Agent Central Configuration**](/solutions/observability/apm/apm-agent-central-configuration.md) | ✅ | ❌ | Not available in Serverless |
+| [**APM Agent Central Configuration**](/solutions/observability/apm/apm-server/apm-agent-central-configuration.md) | ✅ | ❌ | Not available in Serverless |
 | [**APM Tail-based sampling**](/solutions/observability/apm/transaction-sampling.md#apm-tail-based-sampling) | ✅ | ❌ | - Not available in Serverless <br>- Consider **OpenTelemetry** tail sampling processor as an alternative |
 | [**Android agent/SDK instrumentation**](apm-agent-android://reference/edot-android/index.md) | ✅ | ✅ | |
 | [**AWS Firehose integration**](/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md) | ✅ | ✅ | |

deploy-manage/deploy/elastic-cloud/edit-stack-settings.md

@@ -43,7 +43,7 @@ For a list of supported settings, check [{{kib}} settings](kibana://reference/cl
 
 ### APM settings
 
-Refer to [APM configuration reference](/solutions/observability/apm/configure-apm-server.md) for information on how to configure the {{fleet}}-managed APM integration.
+Refer to [APM configuration reference](/solutions/observability/apm/apm-server/configure.md) for information on how to configure the {{fleet}}-managed APM integration.
 
 ## Edit settings [ec-add-user-settings]
 

deploy-manage/deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md

@@ -405,7 +405,7 @@ From the deployment **APM & Fleet** page you can also:
 
 ### Upgrading to {{stack}} 8.0 [ec-upgrade-apm-stack-8]
 
-The following APM settings have been removed in {{stack}} version 8.0. This change is only relevant to users upgrading a standalone (legacy) deployment of APM Server to {{stack}} version 8.0. Check [Add APM user settings](/solutions/observability/apm/configure-apm-server.md) for more details.
+The following APM settings have been removed in {{stack}} version 8.0. This change is only relevant to users upgrading a standalone (legacy) deployment of APM Server to {{stack}} version 8.0. Check [Add APM user settings](/solutions/observability/apm/apm-server/configure.md) for more details.
 
 ```yaml
 apm-server.api_key.enabled

deploy-manage/deploy/self-managed/air-gapped-install.md

@@ -69,7 +69,7 @@ To learn more about installing {{fleet-server}}, refer to the [{{fleet-server}}
 Air-gapped setup of the APM server is possible in two ways:
 
 * By setting up one of the {{agent}} deployments with an APM integration, as described in [Switch a self-installation to the APM integration](/solutions/observability/apm/switch-self-installation-to-apm-integration.md). See [air gapped installation guidance for {{agent}}](#air-gapped-elastic-agent).
-* Or, by installing a standalone Elastic APM Server, as described in the [APM configuration documentation](/solutions/observability/apm/configure-apm-server.md).
+* Or, by installing a standalone Elastic APM Server, as described in the [APM configuration documentation](/solutions/observability/apm/apm-server/configure.md).
 
 
 ## {{ems}} [air-gapped-elastic-maps-service]

deploy-manage/monitor/logging-configuration.md

@@ -111,7 +111,7 @@ You can also consume logs using [stack monitoring](/deploy-manage/monitor/stack-
 
 You can also collect and index the following types of logs from other components in your deployments:
 
-[**APM**](/solutions/observability/apm/configure-logging.md)
+[**APM**](/solutions/observability/apm/apm-server/configure-logging.md)
 
 * `apm*.log*`
 

deploy-manage/monitor/stack-monitoring.md

@@ -89,7 +89,7 @@ Most of these methods require that you configure monitoring of {{es}} before mon
     * [Packetbeat](beats://reference/packetbeat/monitoring.md)
     * [Winlogbeat](beats://reference/winlogbeat/monitoring.md)
 
-* [**APM Server**](/solutions/observability/apm/monitor-apm-server.md)
+* [**APM Server**](/solutions/observability/apm/apm-server/monitor.md)
 
 * **{{agent}}s**:
   * [{{fleet}}-managed {{agent}}s](/reference/fleet/monitor-elastic-agent.md)

deploy-manage/security/fips-ingest.md

@@ -1,7 +1,7 @@
 ---
 applies_to:
   deployment: ga
-navigation_title: 
+navigation_title:
 products:
   - id: apm
   - id: elastic-agent
@@ -25,59 +25,59 @@ Generally speaking FIPS 140-2 requirements can be summarized as:
 FIPS compatible binaries for {{agent}}, {{fleet}}, {{filebeat}}, {{metricbeat}}, and {{apm-server}} are available for [download](https://www.elastic.co/downloads). Look for the `Linux 64-bit (FIPS)` or `Linux aarch64 (FIPS)` platform option on the product download pages for {{agent}} and {{fleet}}, {{filebeat}}, and {{metricbeat}}. Look for the `Linux x86_64 (FIPS)` or `Linux aarch64 (FIPS)` platform option on the {{apm-server}} download page.
 
 :::{important}
-The default configurations provided in the binaries are FIPS compatible. Be sure to check and understand the implications of changing default configurations. 
+The default configurations provided in the binaries are FIPS compatible. Be sure to check and understand the implications of changing default configurations.
 :::
 
 ## Limitations [ingest-limitations-all]
 
 ### TLS [ingest-limitations-tls]
 
 Only FIPS 140-2 compliant TLS protocols, ciphers, and curve types are allowed to be used as listed below.
-* The supported TLS versions are `TLS v1.2` and `TLS v1.3`. 
+* The supported TLS versions are `TLS v1.2` and `TLS v1.3`.
 * The supported cipher suites are:
   * `TLS v1.2`: `ECDHE-RSA-AES-128-GCM-SHA256`, `ECDHE-RSA-AES-256-GCM-SHA384`, `ECDHE-ECDSA-AES-128-GCM-SHA256`, `ECDHE-ECDSA-AES-256-GCM-SHA384`
   * `TLS v1.3`: `TLS-AES-128-GCM-SHA256`, `TLS-AES-256-GCM-SHA384`
 * The supported curve types are `P-256`, `P-384` and `P-521`.
 
 Support for encrypted private keys is not available, as the cryptographic modules used for decrypting password protected keys are not FIPS validated. If an output or any other component with an SSL key that is password protected is configured, the components will fail to load the key. When running in FIPS mode, you must provide non-encrypted keys.
-Be sure to enforce security in your FIPS environments through other means, such as strict file permissions and access controls on the key file itself, for example. 
+Be sure to enforce security in your FIPS environments through other means, such as strict file permissions and access controls on the key file itself, for example.
 
-These TLS related restrictions apply to all components listed--{{agent}}, {{fleet}}, {{filebeat}}, {{metricbeat}}, and {{apm-server}}. 
+These TLS related restrictions apply to all components listed--{{agent}}, {{fleet}}, {{filebeat}}, {{metricbeat}}, and {{apm-server}}.
 
 ### General output and input limitations (Kerberos protocol) [ingest-inputoutput-limitations]
 
-The Kerberos protocol is not supported for any output or input, which also impacts the available `sasl.mechanism` for the Kafka output where only `PLAIN` is supported. 
+The Kerberos protocol is not supported for any output or input, which also impacts the available `sasl.mechanism` for the Kafka output where only `PLAIN` is supported.
 
-This impacts [Filebeat](beats://reference/filebeat/configuration-kerberos.md), [Metricbeat](beats://reference/metricbeat/configuration-kerberos.md) and {{apm-server}}, as well as output configurations for {{agent}} with {{fleet-server}}. 
+This impacts [Filebeat](beats://reference/filebeat/configuration-kerberos.md), [Metricbeat](beats://reference/metricbeat/configuration-kerberos.md) and {{apm-server}}, as well as output configurations for {{agent}} with {{fleet-server}}.
 
 
 ### APM Server [ingest-apm-limitations]
 
-* The [Secrets Keystore](/solutions/observability/apm/secrets-keystore-for-secure-settings.md) is not supported. 
+* The [Secrets Keystore](/solutions/observability/apm/apm-server/secrets-keystore-for-secure-settings.md) is not supported.
 
 ### Filebeat [ingest-filebeat-limitations]
 
-* The [Secrets Keystore](beats://reference/filebeat/keystore.md) is not supported. 
+* The [Secrets Keystore](beats://reference/filebeat/keystore.md) is not supported.
 * The [Translate GUID processor](beats://reference/filebeat/processor-translate-guid.md) is not supported.
-* The [Fingerprint processor](beats://reference/filebeat/fingerprint.md) does not support the md5 and sha1 method. 
-* The [Community ID Network Flowhash processor](beats://reference/filebeat/community-id.md) is not supported. 
-* The [Azure module](beats://reference/filebeat/filebeat-module-azure.md) including the [Azure eventhub input](beats://reference/filebeat/filebeat-input-azure-eventhub.md) and the [Azure Blob Storage Input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-blob-storage) are not currently supported. The [Add Cloud Metadata processor](beats://reference/filebeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently. 
-* The [Office 365 module (Beta)](beats://reference/filebeat/filebeat-module-o365.md) and the [Office 365 input (Deprecated)](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-o365audit) are not supported. 
-* The [GCP Pub/Sub input](beats://reference/filebeat/filebeat-input-gcp-pubsub.md) and the [Google Cloud Storage input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-gcs) are not supported for now. 
-* The [Entity Analytics input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-entity-analytics) is not supported. 
+* The [Fingerprint processor](beats://reference/filebeat/fingerprint.md) does not support the md5 and sha1 method.
+* The [Community ID Network Flowhash processor](beats://reference/filebeat/community-id.md) is not supported.
+* The [Azure module](beats://reference/filebeat/filebeat-module-azure.md) including the [Azure eventhub input](beats://reference/filebeat/filebeat-input-azure-eventhub.md) and the [Azure Blob Storage Input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-blob-storage) are not currently supported. The [Add Cloud Metadata processor](beats://reference/filebeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently.
+* The [Office 365 module (Beta)](beats://reference/filebeat/filebeat-module-o365.md) and the [Office 365 input (Deprecated)](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-o365audit) are not supported.
+* The [GCP Pub/Sub input](beats://reference/filebeat/filebeat-input-gcp-pubsub.md) and the [Google Cloud Storage input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-gcs) are not supported for now.
+* The [Entity Analytics input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-entity-analytics) is not supported.
 
 ### Metricbeat [ingest-metricbeat-limitations]
 
-* The [Secrets Keystore](beats://reference/metricbeat/keystore.md) is not supported. 
+* The [Secrets Keystore](beats://reference/metricbeat/keystore.md) is not supported.
 * The [Translate GUID processor](beats://reference/metricbeat/processor-translate-guid.md) is not supported.
-* The [Fingerprint processor](beats://reference/metricbeat/fingerprint.md) does not support the md5 and sha1 method. 
-* The [Community ID Network Flowhash processor](beats://reference/metricbeat/community-id.md) is not supported. 
-* The [Azure module](beats://reference/metricbeat/metricbeat-module-azure.md) is currently not supported. The [Add Cloud Metadata processor](beats://reference/metricbeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently. 
-* The [Google Cloud Platform module](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-module-gcp) is currently not supported. 
+* The [Fingerprint processor](beats://reference/metricbeat/fingerprint.md) does not support the md5 and sha1 method.
+* The [Community ID Network Flowhash processor](beats://reference/metricbeat/community-id.md) is not supported.
+* The [Azure module](beats://reference/metricbeat/metricbeat-module-azure.md) is currently not supported. The [Add Cloud Metadata processor](beats://reference/metricbeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently.
+* The [Google Cloud Platform module](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-module-gcp) is currently not supported.
 * The [Beta KVM module](beats://reference/metricbeat/metricbeat-module-kvm.md) is not yet supported.
-* The [Mongo DB module](beats://reference/metricbeat/metricbeat-module-mongodb.md) is not supported. 
-* The [MySQL](beats://reference/metricbeat/metricbeat-module-mysql.md), [PostgreSQL](beats://reference/metricbeat/metricbeat-module-postgresql.md), [MSSQL](beats://reference/metricbeat/metricbeat-module-mssql.md) and [SQL](beats://reference/metricbeat/metricbeat-module-sql.md) modules are not supported. 
-* The [Oracle module](beats://reference/metricbeat/metricbeat-module-oracle.md) is not supported. 
+* The [Mongo DB module](beats://reference/metricbeat/metricbeat-module-mongodb.md) is not supported.
+* The [MySQL](beats://reference/metricbeat/metricbeat-module-mysql.md), [PostgreSQL](beats://reference/metricbeat/metricbeat-module-postgresql.md), [MSSQL](beats://reference/metricbeat/metricbeat-module-mssql.md) and [SQL](beats://reference/metricbeat/metricbeat-module-sql.md) modules are not supported.
+* The [Oracle module](beats://reference/metricbeat/metricbeat-module-oracle.md) is not supported.
 
 ### Elastic Agent and Fleet Server [ingest-limitations-agent]
 
@@ -87,7 +87,7 @@ When you use {{agent}} and {{fleet-server}}, these limitations apply:
 
 ### Elastic Integrations that are not FIPS compatible [ingest-limitations-integrations]
 
-These Elastic Integrations have components that are **not** FIPS compatible, and **cannot** be used in FIPS environments, even if combined with other ingest tools that offer FIPS mode. 
+These Elastic Integrations have components that are **not** FIPS compatible, and **cannot** be used in FIPS environments, even if combined with other ingest tools that offer FIPS mode.
 
 - [Azure Logs Integration (v2 preview)](integration-docs://reference/azure/events.md)
 - [Azure Event Hub Input](integration-docs://reference/azure/eventhub.md)
@@ -99,7 +99,7 @@ These Elastic Integrations have components that are **not** FIPS compatible, and
 - [Custom Azure Logs Integration](integration-docs://reference/azure_logs.md)
 - [Azure Resource Metrics Integration](integration-docs://reference/azure_metrics.md)
 - [Azure OpenAI Integration](integration-docs://reference/azure_openai.md)
-- [SQL Input](integration-docs://reference/sql.md) 
+- [SQL Input](integration-docs://reference/sql.md)
 - [PostgreSQL Integration](integration-docs://reference/postgresql.md)
 - [MongoDB Integration](integration-docs://reference/mongodb.md)
 - [MySQL Integration](integration-docs://reference/mysql.md)