Align Observability Applications serverless and stateful content

raw-migrated-files/docs-content/serverless/observability-apm-agents-opentelemetry-opentelemetry-native-support.md

@@ -8,8 +8,8 @@ This is one of several approaches you can use to integrate Elastic with OpenTele
 
 Elastic natively supports the OpenTelemetry protocol (OTLP). This means trace data and metrics collected from your applications and infrastructure can be sent directly to Elastic.
 
-* Send data to Elastic from an upstream [OpenTelemetry Collector](../../../solutions/observability/apps/upstream-opentelemetry-collectors-language-sdks.md#observability-apm-agents-opentelemetry-opentelemetry-native-support-send-data-from-an-upstream-opentelemetry-collector)
-* Send data to Elastic from an upstream [OpenTelemetry language SDK](../../../solutions/observability/apps/upstream-opentelemetry-collectors-language-sdks.md#observability-apm-agents-opentelemetry-opentelemetry-native-support-send-data-from-an-upstream-opentelemetry-sdk)
+* Send data to Elastic from an upstream [OpenTelemetry Collector](../../../solutions/observability/apps/upstream-opentelemetry-collectors-language-sdks.md)
+* Send data to Elastic from an upstream [OpenTelemetry language SDK](../../../solutions/observability/apps/upstream-opentelemetry-collectors-language-sdks.md)
 
 
 ## Send data from an upstream OpenTelemetry Collector [observability-apm-agents-opentelemetry-opentelemetry-native-support-send-data-from-an-upstream-opentelemetry-collector]
@@ -105,7 +105,7 @@ java -javaagent:/path/to/opentelemetry-javaagent-all.jar \
 `OTEL_EXPORTER_OTLP_HEADERS`
 :   Authorization header that includes the Elastic APM API key: `"Authorization=ApiKey an_api_key"`. Note the required space between `ApiKey` and `an_api_key`.
 
-    For information on how to format an API key, refer to [Secure communication with APM agents](../../../solutions/observability/apps/use-apm-securely.md#observability-apm-keep-data-secure-secure-communication-with-apm-agents).
+    For information on how to format an API key, refer to [Secure communication with APM agents](../../../solutions/observability/apps/use-apm-securely.md).
 
     ::::{note}
     If you are using a version of the Python OpenTelemetry agent *before* 1.27.0, the content of the header *must* be URL-encoded. You can use the Python standard library’s `urllib.parse.quote` function to encode the content of the header.
@@ -121,7 +121,7 @@ java -javaagent:/path/to/opentelemetry-javaagent-all.jar \
 
 
 
-You are now ready to collect traces and [metrics](../../../solutions/observability/apps/collect-metrics.md) before [verifying metrics](../../../solutions/observability/apps/collect-metrics.md#open-telemetry-verify-metrics) and [visualizing metrics](../../../solutions/observability/apps/collect-metrics.md#open-telemetry-visualize).
+You are now ready to collect traces and [metrics](../../../solutions/observability/apps/collect-metrics.md) before [verifying metrics](../../../solutions/observability/apps/collect-metrics.md#apm-open-telemetry-verify-metrics) and [visualizing metrics](../../../solutions/observability/apps/collect-metrics.md#apm-open-telemetry-visualize).
 
 
 ## Proxy requests to Elastic [observability-apm-agents-opentelemetry-opentelemetry-native-support-proxy-requests-to-elastic]

raw-migrated-files/docs-content/serverless/observability-apm-agents-opentelemetry.md

@@ -15,10 +15,10 @@ For a complete overview of using OpenTelemetry with Elastic, explore [Elastic Di
 
 Elastic integrates with OpenTelemetry, allowing you to reuse your existing instrumentation to easily send observability data to the Elastic Stack. There are several ways to integrate OpenTelemetry with the Elastic Stack:
 
-* [Elastic Distributions of OpenTelemetry language SDKs](../../../solutions/observability/apps/use-opentelemetry-with-apm.md#observability-apm-agents-opentelemetry-elastic-distributions-of-opentelemetry-language-sdks)
-* [Upstream OpenTelemetry API/SDK + Elastic APM agent](../../../solutions/observability/apps/use-opentelemetry-with-apm.md#observability-apm-agents-opentelemetry-upstream-opentelemetry-apisdk-elastic-apm-agent)
-* [Upstream OpenTelemetry Collector and language SDKs](../../../solutions/observability/apps/use-opentelemetry-with-apm.md#observability-apm-agents-opentelemetry-upstream-opentelemetry-collector-and-language-sdks)
-* [AWS Lambda collector exporter](../../../solutions/observability/apps/use-opentelemetry-with-apm.md#observability-apm-agents-opentelemetry-aws-lambda-collector-exporter)
+* [Elastic Distributions of OpenTelemetry language SDKs](../../../solutions/observability/apps/use-opentelemetry-with-apm.md)
+* [Upstream OpenTelemetry API/SDK + Elastic APM agent](../../../solutions/observability/apps/use-opentelemetry-with-apm.md)
+* [Upstream OpenTelemetry Collector and language SDKs](../../../solutions/observability/apps/use-opentelemetry-with-apm.md)
+* [AWS Lambda collector exporter](../../../solutions/observability/apps/use-opentelemetry-with-apm.md)
 
 
 ## Elastic Distributions of OpenTelemetry language SDKs [observability-apm-agents-opentelemetry-elastic-distributions-of-opentelemetry-language-sdks]

raw-migrated-files/docs-content/serverless/observability-apm-create-custom-links.md

@@ -10,7 +10,7 @@ The **Editor** role or higher is required to create and manage custom links. To
 
 Elastic’s custom link feature allows you to easily create up to 500 dynamic links based on your specific APM data. Custom links can be filtered to only appear for relevant services, environments, transaction types, or transaction names.
 
-Ready to dive in? Jump straight to the [examples](../../../solutions/observability/apps/create-custom-links.md#observability-apm-create-custom-links-custom-link-examples).
+Ready to dive in? Jump straight to the [examples](../../../solutions/observability/apps/create-custom-links.md).
 
 
 ## Create a link [observability-apm-create-custom-links-create-a-link]

raw-migrated-files/docs-content/serverless/observability-apm-dependencies.md

@@ -1,6 +1,6 @@
 # Dependencies [observability-apm-dependencies]
 
-APM agents collect details about external calls made from instrumented services. Sometimes, these external calls resolve into a downstream service that’s instrumented — in these cases, you can utilize [distributed tracing](../../../solutions/observability/apps/trace-sample-timeline.md#observability-apm-trace-sample-timeline-distributed-tracing) to drill down into problematic downstream services. Other times, though, it’s not possible to instrument a downstream dependency — like with a database or third-party service. **Dependencies** gives you a window into these uninstrumented, downstream dependencies.
+APM agents collect details about external calls made from instrumented services. Sometimes, these external calls resolve into a downstream service that’s instrumented — in these cases, you can utilize [distributed tracing](../../../solutions/observability/apps/trace-sample-timeline.md) to drill down into problematic downstream services. Other times, though, it’s not possible to instrument a downstream dependency — like with a database or third-party service. **Dependencies** gives you a window into these uninstrumented, downstream dependencies.
 
 :::{image} ../../../images/serverless-dependencies.png
 :alt: Dependencies view in the Applications UI

raw-migrated-files/docs-content/serverless/observability-apm-observe-lambda-functions.md

@@ -26,7 +26,7 @@ Cold start is also displayed in the trace waterfall, where you can drill-down in
 
 ### Latency distribution correlation [observability-apm-observe-lambda-functions-latency-distribution-correlation]
 
-The [latency correlations](../../../solutions/observability/apps/find-transaction-latency-failure-correlations.md#observability-apm-find-transaction-latency-and-failure-correlations-find-high-transaction-latency-correlations) feature can be used to visualize the impact of Lambda cold starts on latency—just select the `faas.coldstart` field.
+The [latency correlations](../../../solutions/observability/apps/find-transaction-latency-failure-correlations.md) feature can be used to visualize the impact of Lambda cold starts on latency—just select the `faas.coldstart` field.
 
 
 ## AWS Lambda function grouping [observability-apm-observe-lambda-functions-aws-lambda-function-grouping]

raw-migrated-files/docs-content/serverless/observability-apm-service-overview.md

@@ -82,7 +82,7 @@ The **Dependencies** table displays a list of downstream services or external co
 
 The cold start rate chart is specific to serverless services, and displays the percentage of requests that trigger a cold start of a serverless function. A cold start occurs when a serverless function has not been used for a certain period of time. Analyzing the cold start rate can be useful for deciding how much memory to allocate to a function, or when to remove a large dependency.
 
-The cold start rate chart is currently supported for [AWS Lambda](../../../solutions/observability/apps/observe-lambda-functions.md#observability-apm-observe-lambda-functions-cold-starts) functions and Azure functions.
+The cold start rate chart is currently supported for [AWS Lambda](../../../solutions/observability/apps/observe-lambda-functions.md#apm-lambda-cold-start-info) functions and Azure functions.
 
 
 ## Instances [observability-apm-service-overview-instances]

raw-migrated-files/docs-content/serverless/observability-apm-traces.md

@@ -6,7 +6,7 @@ Traces link together related transactions to show an end-to-end performance of h
 ::::
 
 
-**Traces** displays your application’s entry (root) transactions. Transactions with the same name are grouped together and only shown once in this table. If you’re using [distributed tracing](../../../solutions/observability/apps/trace-sample-timeline.md#observability-apm-trace-sample-timeline-distributed-tracing), this view is key to finding the critical paths within your application.
+**Traces** displays your application’s entry (root) transactions. Transactions with the same name are grouped together and only shown once in this table. If you’re using [distributed tracing](../../../solutions/observability/apps/trace-sample-timeline.md), this view is key to finding the critical paths within your application.
 
 By default, transactions are sorted by *Impact*. Impact helps show the most used and slowest endpoints in your service — in other words, it’s the collective amount of pain a specific endpoint is causing your users. If there’s a particular endpoint you’re worried about, select it to view its [transaction details](../../../solutions/observability/apps/transactions-2.md#transaction-details).
 

raw-migrated-files/docs-content/serverless/observability-apm-transaction-sampling.md

@@ -39,7 +39,7 @@ In the example in *Figure 2*, `Service A` initiates four transactions and has a
 
 In addition to setting the sample rate, you can also specify which *trace continuation strategy* to use. There are three trace continuation strategies: `continue`, `restart`, and `restart_external`.
 
-The **`continue`** trace continuation strategy is the default and will behave similar to the examples in the [Distributed tracing section](../../../solutions/observability/apps/transaction-sampling.md#observability-apm-transaction-sampling-distributed-tracing).
+The **`continue`** trace continuation strategy is the default and will behave similar to the examples in the [Distributed tracing section](../../../solutions/observability/apps/transaction-sampling.md).
 
 Use the **`restart_external`** trace continuation strategy on an Elastic-monitored service to start a new trace if the previous service did not have a `traceparent` header with `es` vendor data. This can be helpful if a transaction includes an Elastic-monitored service that is receiving requests from an unmonitored service.
 

raw-migrated-files/docs-content/serverless/observability-apm-transactions.md

@@ -37,7 +37,7 @@ The **Latency**, **Throughput***, ***Failed transaction rate***, ***Time spent b
 
 
 **Cold start rate**
-:   Only applicable to serverless transactions, this chart displays the percentage of requests that trigger a cold start of a serverless function. See [Cold starts](../../../solutions/observability/apps/observe-lambda-functions.md#observability-apm-observe-lambda-functions-cold-starts) for more information.
+:   Only applicable to serverless transactions, this chart displays the percentage of requests that trigger a cold start of a serverless function. See [Cold starts](../../../solutions/observability/apps/observe-lambda-functions.md#apm-lambda-cold-start-info) for more information.
 
 
 ## Transactions table [observability-apm-transactions-transactions-table]

raw-migrated-files/docs-content/serverless/observability-apm-troubleshooting.md

@@ -25,7 +25,7 @@ The most likely cause for this error is using an incompatible version of an {{ap
 
 ### HTTP 400: Event too large [event-too-large]
 
-APM agents communicate with the Managed intake service 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 can reduce the size of the events that your APM agents send by: [enabling span compression](../../../solutions/observability/apps/spans.md) or [reducing collected stack trace information](../../../solutions/observability/apps/reduce-storage.md#observability-apm-reduce-stacktrace).
+APM agents communicate with the Managed intake service 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 can reduce the size of the events that your APM agents send by: [enabling span compression](../../../solutions/observability/apps/spans.md) or [reducing collected stack trace information](../../../solutions/observability/apps/reduce-storage.md).
 
 
 ### HTTP 401: Invalid token [unauthorized]

raw-migrated-files/docs-content/serverless/observability-monitor-synthetics.md

@@ -8,8 +8,8 @@ The Synthetics UI is for viewing result data from monitors created and managed d
 
 Synthetics periodically checks the status of your services and applications. Monitor the availability of network endpoints and services using the following types of monitors:
 
-* [Lightweight HTTP/S, TCP, and ICMP monitors](../../../solutions/observability/apps/synthetic-monitoring.md#observability-monitor-synthetics-lightweight-https-tcp-and-icmp-monitors)
-* [Browser monitors](../../../solutions/observability/apps/synthetic-monitoring.md#observability-monitor-synthetics-browser-monitors)
+* [Lightweight HTTP/S, TCP, and ICMP monitors](../../../solutions/observability/apps/synthetic-monitoring.md)
+* [Browser monitors](../../../solutions/observability/apps/synthetic-monitoring.md)
 
 :::{image} ../../../images/serverless-synthetics-monitor-page.png
 :alt: Synthetics UI

raw-migrated-files/docs-content/serverless/observability-synthetics-command-reference.md

@@ -6,7 +6,7 @@ navigation_title: "Use the CLI"
 
 
 
-## `@elastic/synthetics` [elastic-synthetics-command] 
+## `@elastic/synthetics` [elastic-synthetics-command]
 
 Elastic uses the [@elastic/synthetics](https://www.npmjs.com/package/@elastic/synthetics) library to run synthetic browser tests and report the test results. The library also provides a CLI to help you scaffold, develop/run tests locally, and push tests to Elastic.
 
@@ -57,7 +57,7 @@ You will not need to use most command line flags. However, there are some you ma
 
     Throttling can also be disabled in the configuration file using [`monitor.throttling`](../../../solutions/observability/apps/configure-synthetics-projects.md#synthetics-configuration-monitor). The value defined via the CLI will take precedence.
 
-    ::::{note} 
+    ::::{note}
     Network throttling for browser based monitors is disabled. See this [documention](https://github.com/elastic/synthetics/blob/main/docs/throttling.md) for more details.
 
     ::::
@@ -68,7 +68,7 @@ You will not need to use most command line flags. However, there are some you ma
 
     This is the same as setting [Playwright’s `headless` option](https://playwright.dev/docs/api/class-testoptions#test-options-headless) to `false` by running `--playwright-options '{"headless": false}'`.
 
-    ::::{note} 
+    ::::{note}
     Headful mode should only be used locally to see the browser and interact with DOM elements directly for testing purposes. Do not attempt to run in headful mode when running through Elastic’s global managed testing infrastructure or {{private-location}}s as this is not supported.
 
     ::::
@@ -77,20 +77,20 @@ You will not need to use most command line flags. However, there are some you ma
 `-h, --help`
 :   Shows help for the `npx @elastic/synthetics` command.
 
-::::{note} 
+::::{note}
 The `--pattern`, `--tags`, and `--match` flags for filtering are only supported when you run synthetic tests locally or push them to Elastic. Filtering is *not* supported in any other subcommands like `init` and `locations`.
 
 ::::
 
 
-::::{note} 
+::::{note}
 For debugging synthetic tests locally, you can set an environment variable, `DEBUG=synthetics npx @elastic/synthetics`, to capture Synthetics agent logs.
 
 ::::
 
 
 
-## `@elastic/synthetics init` [elastic-synthetics-init-command] 
+## `@elastic/synthetics init` [elastic-synthetics-init-command]
 
 Scaffold a new Synthetics project using Elastic Synthetics.
 
@@ -100,18 +100,18 @@ This will create a template Node.js project that includes the synthetics agent,
 npx @elastic/synthetics init <name-of-synthetics-project>
 ```
 
-Read more about what’s included in a template Synthetics project in [Create a Synthetics project](../../../solutions/observability/apps/create-monitors-with-project-monitors.md#observability-synthetics-get-started-project-create-a-synthetics-project).
+Read more about what’s included in a template Synthetics project in [Create a Synthetics project](../../../solutions/observability/apps/create-monitors-with-project-monitors.md).
 
 
-## `@elastic/synthetics push` [elastic-synthetics-push-command] 
+## `@elastic/synthetics push` [elastic-synthetics-push-command]
 
 Create monitors in by using your local journeys. By default, running `push` command will use the `project` settings field from the `synthetics.config.ts` file, which is set up using the `init` command. However, you can override these settings using the CLI flags.
 
 ```sh
 SYNTHETICS_API_KEY=<api-key> npx @elastic/synthetics push --url <kibana-url> --id <id|name>
 ```
 
-::::{note} 
+::::{note}
 The `push` command includes interactive prompts to prevent you from accidentally deleting or duplicating monitors. You will see a prompt when:
 
 * You `push` a project that used to contain one or more monitors but either no longer contains previously running monitors or has any monitors. Select `yes` to delete the monitors associated with the project ID being pushed.
@@ -120,7 +120,7 @@ The `push` command includes interactive prompts to prevent you from accidentally
 ::::
 
 
-::::{note} 
+::::{note}
 If the journey contains external NPM packages other than the `@elastic/synthetics`, those packages will be bundled along with the journey code when the `push` command is invoked. However there are some limitations when using external packages:
 
 * Bundled journeys after compression should not be more than 1500 Kilobytes.
@@ -188,7 +188,7 @@ If the journey contains external NPM packages other than the `@elastic/synthetic
 
 
 
-## Tag monitors [observability-synthetics-command-reference-tag-monitors] 
+## Tag monitors [observability-synthetics-command-reference-tag-monitors]
 
 Synthetics journeys can be tagged with one or more tags.  Use tags to filter journeys when running tests locally or pushing them to Elastic.
 
@@ -215,7 +215,7 @@ tags:
 To apply tags to all browser and lightweight monitors, configure using the `monitor.tags` field in the `synthetics.config.ts` file.
 
 
-## Filter monitors [observability-synthetics-command-reference-filter-monitors] 
+## Filter monitors [observability-synthetics-command-reference-filter-monitors]
 
 When running the `npx @elastic/synthetics push` command, you can filter the monitors that are pushed to Elastic using the following flags:
 
@@ -236,7 +236,7 @@ npx @elastic/synthetics push --config synthetics.prod.config.ts --tags env:prod
 ```
 
 
-## `@elastic/synthetics locations` [elastic-synthetics-locations-command] 
+## `@elastic/synthetics locations` [elastic-synthetics-locations-command]
 
 List all available locations for running synthetics monitors.
 
@@ -255,7 +255,7 @@ To list both locations on Elastic’s global managed infrastructure and {{privat
 :   API key used for authentication.
 
 
-## `@elastic/synthetics totp <secret>` [observability-synthetics-command-reference-elasticsynthetics-totp-lesssecretgreater] 
+## `@elastic/synthetics totp <secret>` [observability-synthetics-command-reference-elasticsynthetics-totp-lesssecretgreater]
 
 Generate a Time-based One-Time Password (TOTP) for multifactor authentication(MFA) in Synthetics.