Skip to content

Commit d1e4e2d

Browse files
clean up cross-repo links
1 parent 79c146b commit d1e4e2d

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

docs/reference/aws-lambda-config-options.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ The recommended way of configuring the {{apm-lambda-ext}} and the APM agents on
99

1010
The configuration options for the APM agents are documented in the corresponding language agents:
1111

12-
* [Configuration options - Node.js APM agent](apm-agent-nodejs://docs/reference/configuration.md)
13-
* [Configuration options - Python APM agent](apm-agent-php://docs/reference/configuration.md)
14-
* [Configuration options - Java APM agent](apm-agent-java://docs/reference/configuration.md)
12+
* [Configuration options - Node.js APM agent](apm-agent-nodejs://reference/configuration.md)
13+
* [Configuration options - Python APM agent](apm-agent-php://reference/configuration.md)
14+
* [Configuration options - Java APM agent](apm-agent-java://reference/configuration.md)
1515

1616
::::{note}
1717
Some APM agent configuration options don’t make sense when the APM agent is running in a Lambda environment. For example, instead of using the Python APM agent configuration variable, `verify_server_cert`, you must use the `ELASTIC_APM_LAMBDA_VERIFY_SERVER_CERT` variable described below.

docs/reference/aws-lambda-overhead.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ When your function experiences a cold start, the Elastic APM AWS Lambda extensio
2121

2222
APM agents enrich your application’s code with measurement code that collects APM data. This measurement code introduces a small performance overhead to your application, which is usually in a negligible range. The same is true with Lambda functions. The concrete performance overhead introduced by APM agents highly depends on the configuration of the agent and on the characteristics of your function’s code. The following agent-specific documentation pages provide insights and instructions on tuning the performance the APM agents:
2323

24-
* [Performance Tuning - Node.js](apm-agent-nodejs://docs/reference/performance-tuning.md)
25-
* [Performance Tuning - Python](apm-agent-python://docs/reference/performance-tuning.md)
26-
* [Performance Tuning - Java](apm-agent-java://docs/reference/overhead-performance-tuning.md)
24+
* [Performance Tuning - Node.js](apm-agent-nodejs://reference/performance-tuning.md)
25+
* [Performance Tuning - Python](apm-agent-python://reference/performance-tuning.md)
26+
* [Performance Tuning - Java](apm-agent-java://reference/overhead-performance-tuning.md)
2727

28-
Similar to the Elastic APM AWS Lambda extension, APM agents are initialized at cold start time. As a consequence, the APM agent’s overhead will be higher for cold starts as compared to their overhead on *warm* invocations. This effect is especially relevant for the Java APM agent on AWS Lambda. Learn more about corresponding tuning options in the [Java Agent’s AWS Lambda documentation](apm-agent-java://docs/reference/aws-lambda.md#aws-lambda-caveats).
28+
Similar to the Elastic APM AWS Lambda extension, APM agents are initialized at cold start time. As a consequence, the APM agent’s overhead will be higher for cold starts as compared to their overhead on *warm* invocations. This effect is especially relevant for the Java APM agent on AWS Lambda. Learn more about corresponding tuning options in the [Java Agent’s AWS Lambda documentation](apm-agent-java://reference/aws-lambda.md#aws-lambda-caveats).
2929

docs/reference/aws-lambda-secrets-manager.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -266,9 +266,9 @@ Provide the name of the secret you created in [Step 1](#aws-lambda-secrets-manag
266266

267267
The language-specific instructions describe how to set environment variables for configuring AWS Lambda for Elastic APM:
268268

269-
* [Configure APM on AWS Lambda - Node.js](apm-agent-nodejs://docs/reference/lambda.md#_step_3_configure_apm_on_aws_lambda)
270-
* [Configure APM on AWS Lambda - Python](apm-agent-python://docs/reference/lambda-support.md#_step_3_configure_apm_on_aws_lambda)
271-
* [Configure APM on AWS Lambda - Java](apm-agent-java://docs/reference/aws-lambda.md#_step_3_configure_apm_on_aws_lambda)
269+
* [Configure APM on AWS Lambda - Node.js](apm-agent-nodejs://reference/lambda.md#_step_3_configure_apm_on_aws_lambda)
270+
* [Configure APM on AWS Lambda - Python](apm-agent-python://reference/lambda-support.md#_step_3_configure_apm_on_aws_lambda)
271+
* [Configure APM on AWS Lambda - Java](apm-agent-java://reference/aws-lambda.md#_step_3_configure_apm_on_aws_lambda)
272272

273273
That’s it. With the first invocation (cold start) of your Lambda function you should see a log message from the {{apm-lambda-ext}} indicating that a secret from the secrets manager is used:
274274

0 commit comments

Comments
 (0)