clean up cross-repo links

colleenmcginnis · colleenmcginnis · commit c5280ace86f0 · 2025-02-28T14:46:04.000-06:00
diff --git a/docs/docset.yml b/docs/docset.yml
@@ -3,6 +3,7 @@ cross_links:
   - apm-agent-rum-js
   - apm-aws-lambda
   - beats
+  - docs-content
   - ecs
   - ecs-logging
   - ecs-logging-python
diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md
@@ -189,7 +189,7 @@ For base `logging` from the standard library, the agent will get the root logger
 
 If `structlog` is installed, the agent will override any configured processors with `ecs_logging.StructlogFormatter()`.
 
-Note that this is a very blunt instrument that could have unintended side effects. If problems arise, please apply these formatters manually and leave this setting as `"off"`. See the [`ecs_logging` docs](ecs-logging-python://docs/reference/installation.md) for more information about using these formatters.
+Note that this is a very blunt instrument that could have unintended side effects. If problems arise, please apply these formatters manually and leave this setting as `"off"`. See the [`ecs_logging` docs](ecs-logging-python://reference/installation.md) for more information about using these formatters.
 
 Also note that this setting does not facilitate shipping logs to Elasticsearch. We recommend [Filebeat](https://www.elastic.co/beats/filebeat) for that purpose.
 
diff --git a/docs/reference/django-support.md b/docs/reference/django-support.md
@@ -149,7 +149,7 @@ elasticApm.init({
 })
 ```
 
-See the [JavaScript RUM agent documentation](apm-agent-rum-js://docs/reference/index.md) for more information.
+See the [JavaScript RUM agent documentation](apm-agent-rum-js://reference/index.md) for more information.
 
 
 ## Enabling and disabling the agent [django-enabling-and-disabling-the-agent]
@@ -171,7 +171,7 @@ ELASTIC_APM = {
 To easily send Python `logging` messages as "error" objects to Elasticsearch, we provide a `LoggingHandler` which you can use in your logging setup. The log messages will be enriched with a stack trace, data from the request, and more.
 
 ::::{note}
-the intended use case for this handler is to send high priority log messages (e.g. log messages with level `ERROR`) to Elasticsearch. For normal log shipping, we recommend using [filebeat](beats://docs/reference/filebeat/filebeat-overview.md).
+the intended use case for this handler is to send high priority log messages (e.g. log messages with level `ERROR`) to Elasticsearch. For normal log shipping, we recommend using [filebeat](beats://reference/filebeat/filebeat-overview.md).
 ::::
 
 
diff --git a/docs/reference/flask-support.md b/docs/reference/flask-support.md
@@ -206,7 +206,7 @@ elasticApm.init({
 })
 ```
 
-See the [JavaScript RUM agent documentation](apm-agent-rum-js://docs/reference/index.md) for more information.
+See the [JavaScript RUM agent documentation](apm-agent-rum-js://reference/index.md) for more information.
 
 
 ## Supported Flask and Python versions [supported-flask-and-python-versions]
diff --git a/docs/reference/lambda-support.md b/docs/reference/lambda-support.md
@@ -215,7 +215,7 @@ window.addEventListener("DOMContentLoaded", async () => {
                                 'COPY --from=python-agent /opt/python/ /opt/python/');
 });
 </script>
-Both the [{{apm-lambda-ext}}](apm-aws-lambda://docs/reference/index.md) and the Python APM Agent are added to your Lambda function as [AWS Lambda Layers](https://docs.aws.amazon.com/lambda/latest/dg/invocation-layers.md). Therefore, you need to add the corresponding Layer ARNs (identifiers) to your Lambda function.
+Both the [{{apm-lambda-ext}}](apm-aws-lambda://reference/index.md) and the Python APM Agent are added to your Lambda function as [AWS Lambda Layers](https://docs.aws.amazon.com/lambda/latest/dg/invocation-layers.md). Therefore, you need to add the corresponding Layer ARNs (identifiers) to your Lambda function.
 
 :::::::{tab-set}
 
@@ -308,7 +308,7 @@ The {{apm-lambda-ext}} and the APM Python agent are configured through environme
 
 For the minimal configuration, you will need the *APM Server URL* to set the destination for APM data and an *{{apm-guide-ref}}/secret-token.html[APM Secret Token]*. If you prefer to use an [APM API key](docs-content://solutions/observability/apps/api-keys.md) instead of the APM secret token, use the `ELASTIC_APM_API_KEY` environment variable instead of `ELASTIC_APM_SECRET_TOKEN` in the following configuration.
 
-For production environments, we recommend [using the AWS Secrets Manager to store your APM authentication key](apm-aws-lambda://docs/reference/aws-lambda-secrets-manager.md) instead of providing the secret value as plaintext in the environment variables.
+For production environments, we recommend [using the AWS Secrets Manager to store your APM authentication key](apm-aws-lambda://reference/aws-lambda-secrets-manager.md) instead of providing the secret value as plaintext in the environment variables.
 
 :::::::{tab-set}
 
@@ -330,7 +330,7 @@ ELASTIC_APM_SEND_STRATEGY     = background                         <4>
 1. Use this exact fixed value.
 2. This is your APM Server URL.
 3. This is your APM secret token.
-4. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://docs/reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
+4. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
 
 ![Python environment variables configuration section in AWS Console](../images/python-lambda-env-vars.png "")
 ::::::
@@ -363,7 +363,7 @@ Resources:
 ...
 ```
 
-1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://docs/reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
+1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
 
 ::::::
 
@@ -383,7 +383,7 @@ functions:
 ...
 ```
 
-1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://docs/reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
+1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
 
 ::::::
 
@@ -406,7 +406,7 @@ resource "aws_lambda_function" "your_lambda_function" {
 ...
 ```
 
-1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://docs/reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
+1. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
 
 ::::::
 
@@ -423,13 +423,13 @@ ELASTIC_APM_SEND_STRATEGY     = background                         <4>
 1. Use this exact fixed value.
 2. This is your APM Server URL.
 3. This is your APM secret token.
-4. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://docs/reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
+4. The [ELASTIC_APM_SEND_STRATEGY](apm-aws-lambda://reference/aws-lambda-config-options.md#_elastic_apm_send_strategy) defines when APM data is sent to your Elastic APM backend. To reduce the execution time of your lambda functions, we recommend to use the background strategy in production environments with steady load scenarios.
 
 ::::::
 
 :::::::
 
-You can optionally [fine-tune the Python agent](/reference/configuration.md) or the [configuration of the {{apm-lambda-ext}}](apm-aws-lambda://docs/reference/aws-lambda-config-options.md).
+You can optionally [fine-tune the Python agent](/reference/configuration.md) or the [configuration of the {{apm-lambda-ext}}](apm-aws-lambda://reference/aws-lambda-config-options.md).
 
 That’s it. After following the steps above, you’re ready to go!  Your Lambda function invocations should be traced from now on.  Spans will be captured for [supported technologies](/reference/supported-technologies.md). You can also use [`capture_span`](/reference/api-reference.md#api-capture-span) to capture custom spans, and you can retrieve the `Client` object for capturing exceptions/messages using [`get_client`](/reference/api-reference.md#api-get-client).
 
diff --git a/docs/reference/logs.md b/docs/reference/logs.md
@@ -8,7 +8,7 @@ mapped_pages:
 Elastic Python APM Agent provides the following log features:
 
 * [Log correlation](#log-correlation-ids) : Automatically inject correlation IDs that allow navigation between logs, traces and services.
-* [Log reformatting (experimental)](#log-reformatting) : Automatically reformat plaintext logs in [ECS logging](ecs-logging://docs/reference/intro.md) format.
+* [Log reformatting (experimental)](#log-reformatting) : Automatically reformat plaintext logs in [ECS logging](ecs-logging://reference/intro.md) format.
 
 ::::{note}
 Elastic Python APM Agent does not send the logs to Elasticsearch. It only injects correlation IDs and reformats the logs. You must use another ingestion strategy.  We recommend [Filebeat](https://www.elastic.co/beats/filebeat) for that purpose.
@@ -17,7 +17,7 @@ Elastic Python APM Agent does not send the logs to Elasticsearch. It only inject
 
 Those features are part of [Application log ingestion strategies](docs-content://solutions/observability/logs/stream-application-logs.md).
 
-The [`ecs-logging-python`](ecs-logging-python://docs/reference/index.md) library can also be used to use the [ECS logging](ecs-logging://docs/reference/intro.md) format without an APM agent. When deployed with the Python APM agent, the agent will provide [log correlation](#log-correlation-ids) IDs.
+The [`ecs-logging-python`](ecs-logging-python://reference/index.md) library can also be used to use the [ECS logging](ecs-logging://reference/intro.md) format without an APM agent. When deployed with the Python APM agent, the agent will provide [log correlation](#log-correlation-ids) IDs.
 
 
 ## Log correlation [log-correlation-ids]
@@ -41,7 +41,7 @@ We use [`logging.setLogRecordFactory()`](https://docs.python.org/3/library/loggi
 * `elasticapm_trace_id`
 * `elasticapm_span_id`
 
-This factory also adds these fields to a dictionary attribute, `elasticapm_labels`, using the official ECS [tracing fields](ecs://docs/reference/ecs-tracing.md).
+This factory also adds these fields to a dictionary attribute, `elasticapm_labels`, using the official ECS [tracing fields](ecs://reference/ecs-tracing.md).
 
 You can disable this automatic behavior by using the [`disable_log_record_factory`](/reference/configuration.md#config-generic-disable-log-record-factory) setting in your configuration.
 
@@ -81,7 +81,7 @@ In order to correlate logs from your app with transactions captured by the Elast
 
 If you’re using structured logging, either [with a custom solution](https://docs.python.org/3/howto/logging-cookbook.md#implementing-structured-logging) or with [structlog](http://www.structlog.org/en/stable/) (recommended), then this is fairly easy. Throw the [JSONRenderer](http://www.structlog.org/en/stable/api.md#structlog.processors.JSONRenderer) in, and use [Filebeat](https://www.elastic.co/blog/structured-logging-filebeat) to pull these logs into Elasticsearch.
 
-Without structured logging the task gets a little trickier. Here we recommend first making sure your LogRecord objects have the elasticapm attributes (see [`logging`](#logging)), and then you’ll want to combine some specific formatting with a Grok pattern, either in Elasticsearch using [the grok processor](elasticsearch://docs/reference/ingestion-tools/enrich-processor/grok-processor.md), or in [logstash with a plugin](logstash://docs/reference/plugins-filters-grok.md).
+Without structured logging the task gets a little trickier. Here we recommend first making sure your LogRecord objects have the elasticapm attributes (see [`logging`](#logging)), and then you’ll want to combine some specific formatting with a Grok pattern, either in Elasticsearch using [the grok processor](elasticsearch://reference/ingestion-tools/enrich-processor/grok-processor.md), or in [logstash with a plugin](logstash://reference/plugins-filters-grok.md).
 
 Say you have a [Formatter](https://docs.python.org/3/library/logging.md#logging.Formatter) that looks like this:
 
@@ -114,7 +114,7 @@ formatstring = formatstring + " | elasticapm " \
                               "span.id=%(elasticapm_span_id)s"
 ```
 
-Then, you could use a grok pattern like this (for the [Elasticsearch Grok Processor](elasticsearch://docs/reference/ingestion-tools/enrich-processor/grok-processor.md)):
+Then, you could use a grok pattern like this (for the [Elasticsearch Grok Processor](elasticsearch://reference/ingestion-tools/enrich-processor/grok-processor.md)):
 
 ```json
 {
diff --git a/docs/reference/upgrading-5.x.md b/docs/reference/upgrading-5.x.md
@@ -12,7 +12,7 @@ APM Server and Kibana 7.3 introduced support for collecting breakdown metrics, a
 
 ## Tags renamed to Labels [_tags_renamed_to_labels]
 
-To better align with other parts of the Elastic Stack and the [Elastic Common Schema](ecs://docs/reference/index.md), we renamed "tags" to "labels", and introduced limited support for typed labels. While tag values were only allowed to be strings, label values can be strings, booleans, or numerical.
+To better align with other parts of the Elastic Stack and the [Elastic Common Schema](ecs://reference/index.md), we renamed "tags" to "labels", and introduced limited support for typed labels. While tag values were only allowed to be strings, label values can be strings, booleans, or numerical.
 
 To benefit from this change, ensure that you run at least **APM Server 6.7**, and use `elasticapm.label()` instead of `elasticapm.tag()`. The `tag()` API will continue to work as before, but emit a `DeprecationWarning`. It will be removed in 6.0 of the agent.
 
