elastic · mdbirnstiehl · Apr 4, 2025 · Apr 2, 2025 · Apr 2, 2025 · Apr 4, 2025
@@ -1,9 +1,11 @@
 ---
+navigation_title: "Act on data"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-act-on-data.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-act-on-data.html
-
-navigation_title: "Act on data"
+applies_to:
+  stack:
+  serverless:
 ---
 
 # Act on application data

@@ -1,9 +1,11 @@
 ---
+navigation_title: "Analyze monitor data"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/synthetics-analyze.html
   - https://www.elastic.co/guide/en/serverless/current/observability-synthetics-analyze.html
-
-navigation_title: "Analyze monitor data"
+applies_to:
+  stack:
+  serverless:
 ---
 
 # Analyze data from synthetic monitors

@@ -2,11 +2,18 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/analyze-monitors.html
 applies_to:
-  stack: all
+  stack: deprecated 8.15.0
+  serverless: unavailable
 ---
 
 # Analyze monitors [analyze-monitors]
 
+::::{admonition} Deprecated in 8.15.0.
+:class: warning
+
+Use [Synthetic monitoring](/solutions/observability/apps/synthetic-monitoring.md) instead of the {{uptime-app}}.
+::::
+
 To access this page, go to **{{observability}} > Uptime > Monitors**. Click on a listed monitor to view more details and analyze further.
 
 The monitor detail screen displays several panels of information.

@@ -3,13 +3,17 @@ navigation_title: "Analyze"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/uptime-analyze.html
 applies_to:
-  stack: all
+  stack: deprecated 8.15.0
+  serverless: unavailable
 ---
 
-
-
 # Analyze [uptime-analyze]
 
+::::{admonition} Deprecated in 8.15.0.
+:class: warning
+
+Use [Synthetic monitoring](/solutions/observability/apps/synthetic-monitoring.md) instead of the {{uptime-app}}.
+::::
 
 The {{uptime-app}} in {{kib}} both gives you a high-level overview of your service’s availability and allows you to dig into details to diagnose what caused downtime.
 

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-anonymous-auth.html
+applies_to:
+  stack:
 ---
 
 # Anonymous authentication [apm-anonymous-auth]

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-api-key.html
+applies_to:
+  stack:
 ---
 
 # API keys [apm-api-key]

@@ -2,7 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-auth.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 # APM agent authorization [apm-agent-auth]

@@ -3,7 +3,7 @@ navigation_title: "Centrally configure APM agents in Kibana"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-configuration.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-server-compatibility.html
+applies_to:
+  stack:
 ---
 
 # APM agent compatibility [apm-agent-server-compatibility]

@@ -2,7 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-explorer.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 # APM Agent explorer [apm-agent-explorer]

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-tls.html
+applies_to:
+  stack:
 ---
 
 # APM agent TLS communication [apm-agent-tls]

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-apis.html
+applies_to:
+  stack:
 ---
 
 # APM APIs [apm-apis]

@@ -3,7 +3,7 @@ navigation_title: "Kubernetes"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-k8s-attacher.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 

@@ -2,6 +2,8 @@
 navigation_title: "Create an APM reader user"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-app-reader.html
+applies_to:
+  stack:
 ---
 
 

@@ -3,7 +3,7 @@ navigation_title: "Advanced setup"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-setting-up-and-running.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 

@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-api.html
+applies_to:
+  stack:
 ---
 
 # APM Server API [apm-api]

@@ -2,7 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/get-started-with-apm-server-binary.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 # APM Server binary [get-started-with-apm-server-binary]

@@ -3,7 +3,7 @@ navigation_title: "Command reference"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-command-line-options.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 

@@ -1,14 +1,16 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-api-info.html
+applies_to:
+  stack:
 ---
 
 # APM Server information API [apm-api-info]
 
 The APM Server exposes an API endpoint to query general server information. This lightweight endpoint is useful as a server up/down health check.
 
 
-## Server Information endpoint [apm-api-info-endpoint] 
+## Server Information endpoint [apm-api-info-endpoint]
 
 This is the server information endpoint:
 
@@ -23,7 +25,7 @@ To configure authenticated access to the APM server, the instructions at [APM AP
 If an [API keys](api-keys.md) or a [Secret token](secret-token.md) is passed along with the `HTTP GET` request, in addition to an HTTP 200, the response payload will include some information about the APM server.
 
 
-### Example: GET, without credentials [apm-api-info-example-get-without-credentials] 
+### Example: GET, without credentials [apm-api-info-example-get-without-credentials]
 
 Example APM Server status request with GET, without credentials:
 

@@ -1,12 +1,14 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-performance-diagnostic.html
+applies_to:
+  stack:
 ---
 
 # APM Server performance diagnostic [apm-performance-diagnostic]
 
 
-## Diagnosing backpressure from {{es}} [apm-es-backpressure] 
+## Diagnosing backpressure from {{es}} [apm-es-backpressure]
 
 When {{es}} is under excessive load or indexing pressure, APM Server could experience the downstream backpressure when indexing new documents into {{es}}. Most commonly, backpressure from {{es}} will manifest itself in the form of higher indexing latency and/or rejected requests, which in return could lead APM Server to deny incoming requests. As a result, APM agents connected to the affected APM Server will suffer from throttling and/or request timeout when shipping APM events.
 

@@ -1,32 +1,34 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-common-response-codes.html
+applies_to:
+  stack:
 ---
 
 # APM Server response codes [apm-common-response-codes]
 
 
-## HTTP 400: Data decoding error / Data validation error [apm-bad-request] 
+## HTTP 400: Data decoding error / Data validation error [apm-bad-request]
 
 The most likely cause for this error is using incompatible versions of {{apm-agent}} and APM Server. See the [agent/server compatibility matrix](apm-agent-compatibility.md) to verify compatibility.
 
 
-## HTTP 400: Event too large [apm-event-too-large] 
+## HTTP 400: Event too large [apm-event-too-large]
 
 APM agents communicate with the APM server by sending events in an HTTP request. Each event is sent as its own line in the HTTP request body. If events are too large, you should consider increasing the [Max event size](general-configuration-options.md#apm-max_event_size) setting in the APM integration, and adjusting relevant settings in the agent.
 
 
-## HTTP 401: Invalid token [apm-unauthorized] 
+## HTTP 401: Invalid token [apm-unauthorized]
 
 Either the [Secret token](secret-token.md) in the request header doesn’t match the secret token configured in the APM integration, or the [API keys](api-keys.md) is invalid.
 
 
-## HTTP 403: Forbidden request [apm-forbidden] 
+## HTTP 403: Forbidden request [apm-forbidden]
 
 Either you are sending requests to a [RUM](real-user-monitoring-rum.md) endpoint without RUM enabled, or a request is coming from an origin not specified in the APM integration settings. See the [Allowed origins](configure-real-user-monitoring-rum.md#apm-rum-allow-origins) setting for more information.
 
 
-## HTTP 503: Request timed out waiting to be processed [apm-request-timed-out] 
+## HTTP 503: Request timed out waiting to be processed [apm-request-timed-out]
 
 This happens when APM Server exceeds the maximum number of requests that it can process concurrently. To alleviate this problem, you can try to: reduce the sample rate and/or reduce the collected stack trace information. See [Reduce storage](reduce-storage.md) for more information.
 

@@ -2,7 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-running-with-systemd.html
 applies_to:
-  stack: all
+  stack:
 ---
 
 # APM Server and systemd [apm-running-with-systemd]

@@ -2,8 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-app-api.html
 applies_to:
-  stack: all
-  serverless: all
+  stack:
 ---
 
 # APM UI API [apm-app-api]
@@ -16,7 +15,7 @@ Some Applications UI features are provided via a REST API:
 * APM agent key API ([{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-agent-keys) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-agent-keys))
 
 
-## Using the APIs [apm-api-example] 
+## Using the APIs [apm-api-example]
 
 Interact with APM APIs using cURL or another API tool. All APM APIs are Kibana APIs, not Elasticsearch APIs; because of this, the Kibana dev tools console cannot be used to interact with APM APIs.
 
@@ -62,7 +61,7 @@ curl -X POST \
 ```
 
 
-## Kibana API [kibana-api] 
+## Kibana API [kibana-api]
 
 In addition to the APM specific API endpoints, Kibana provides its own [REST API](/solutions/observability/apps/apm-server-api.md) which you can use to automate certain aspects of configuring and deploying Kibana.
 

@@ -2,6 +2,8 @@
 navigation_title: "Secure data"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-data-security.html
+applies_to:
+  stack:
 ---
 
 
@@ -19,7 +21,7 @@ Depending on the type of data, we offer several different ways to filter, manipu
 In addition to utilizing filters, you should regularly review the [sensitive fields](#apm-sensitive-fields) table to ensure sensitive data is not being ingested. If it is, it’s possible to remove or redact it. See [Delete sensitive data](delete-sensitive-data.md) for more information.
 
 
-## Built-in data filters [apm-built-in-data-filters] 
+## Built-in data filters [apm-built-in-data-filters]
 
 Built-in data filters allow you to filter or turn off ingestion of the following types of data:
 
@@ -32,7 +34,7 @@ Built-in data filters allow you to filter or turn off ingestion of the following
 | [Database statements](built-in-data-filters.md#apm-filters-database-statements) | Sensitive user or business information |
 
 
-## Custom filters [apm-custom-data-filters] 
+## Custom filters [apm-custom-data-filters]
 
 Custom filters allow you to filter or redact other types of APM data on ingestion:
 
@@ -42,7 +44,7 @@ Custom filters allow you to filter or redact other types of APM data on ingestio
 | [{{apm-agent}} filters](custom-filters.md#apm-filters-in-agent) | Not supported by all agents.Data is sanitized before leaving the instrumented service.Potential overhead implications on the instrumented service |
 
 
-## Sensitive fields [apm-sensitive-fields] 
+## Sensitive fields [apm-sensitive-fields]
 
 You should review the following fields regularly to ensure sensitive data is not being captured:
 
@@ -58,9 +60,4 @@ You should review the following fields regularly to ensure sensitive data is not
 | `stacktrace.vars` | A flat mapping of local variables captured in the stack frame | [Custom filters](custom-filters.md) |
 | `url.query` | The query string of the request, e.g. `?pass=hunter2`. | [Custom filters](custom-filters.md) |
 | `user.*` | Logged-in user information. | [Custom filters](custom-filters.md) |
-| `user_agent.*` | Device and version making the network request. | [Personal data](built-in-data-filters.md#apm-filters-personal-data) |
-
-
-
-
-
+| `user_agent.*` | Device and version making the network request. | [Personal data](built-in-data-filters.md#apm-filters-personal-data) |
@@ -2,6 +2,9 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm.html
+applies_to:
+  stack:
+  serverless:
 ---
 
 # Application performance monitoring (APM) [apm]

@@ -2,10 +2,10 @@
 navigation_title: "Create an annotation user"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-app-annotation-user-create.html
+applies_to:
+  stack:
 ---
 
-
-
 # Applications UI annotation user [apm-app-annotation-user-create]