Skip to content

Commit 93e40a2

Browse files
clean up
1 parent da99443 commit 93e40a2

File tree

7 files changed

+10
-9
lines changed

7 files changed

+10
-9
lines changed

docs/reference/azure-functions-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ mapped_pages:
88

99
## Prerequisites [_prerequisites_2]
1010

11-
You need an APM Server to which you can send APM data. Follow the [APM Quick start](docs-content://solutions/observability/apps/get-started-with-apm.md) if you have not set one up yet. For the best-possible performance, we recommend setting up APM on {{ecloud}} in the same Azure region as your Azure Functions app.
11+
You need an APM Server to which you can send APM data. Follow the [APM Quick start](docs-content://solutions/observability/apps/fleet-managed-apm-server.md) if you have not set one up yet. For the best-possible performance, we recommend setting up APM on {{ecloud}} in the same Azure region as your Azure Functions app.
1212

1313
::::{note}
1414
Currently, only HTTP and timer triggers are supported. Other trigger types may be captured as well, but the amount of captured contextual data may differ.

docs/reference/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,5 +24,5 @@ More detailed information on how the Agent works can be found in the [advanced t
2424

2525
## Additional components [additional-components]
2626

27-
APM Agents work in conjunction with the [APM Server](docs-content://solutions/observability/apps/application-performance-monitoring-apm.md), [Elasticsearch](docs-content://get-started/index.md), and [Kibana](docs-content://get-started/the-stack.md). The [APM Guide](docs-content://solutions/observability/apps/application-performance-monitoring-apm.md) provides details on how these components work together, and provides a matrix outlining [Agent and Server compatibility](docs-content://solutions/observability/apps/apm-agent-compatibility.md).
27+
APM Agents work in conjunction with the [APM Server](docs-content://solutions/observability/apps/application-performance-monitoring-apm.md), [Elasticsearch](docs-content://get-started/introduction.md#what-is-es), and [Kibana](docs-content://get-started/introduction.md#what-is-kib). The [APM documentation](docs-content://solutions/observability/apps/application-performance-monitoring-apm.md) provides details on how these components work together, and provides a matrix outlining [Agent and Server compatibility](docs-content://solutions/observability/apps/apm-agent-compatibility.md).
2828

docs/reference/lambda-support.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The Centralized Agent Configuration on the Elasticsearch APM currently does NOT
1717

1818
## Prerequisites [_prerequisites]
1919

20-
You need an APM Server to send APM data to. Follow the [APM Quick start](docs-content://solutions/observability/apps/application-performance-monitoring-apm.md) if you have not set one up yet. For the best-possible performance, we recommend setting up APM on {{ecloud}} in the same AWS region as your AWS Lambda functions.
20+
You need an APM Server to send APM data to. Follow the [APM Quick start](docs-content://solutions/observability/apps/fleet-managed-apm-server.md) if you have not set one up yet. For the best-possible performance, we recommend setting up APM on {{ecloud}} in the same AWS region as your AWS Lambda functions.
2121

2222
## Step 1: Add the APM Layers to your Lambda function [add_the_apm_layers_to_your_lambda_function]
2323

@@ -167,8 +167,9 @@ To configure APM through the AWS command line interface execute the following co
167167

168168
```bash
169169
aws lambda update-function-configuration --function-name yourLambdaFunctionName \
170-
--environment "Variables={AWS_LAMBDA_EXEC_WRAPPER=/opt/python/bin/elasticapm-lambda,ELASTIC_APM_LAMBDA_APM_SERVER=<YOUR-APM-SERVER-URL>,ELASTIC_APM_SECRET_TOKEN=<YOUR-APM-SECRET-TOKEN>,ELASTIC_APM_SEND_STRATEGY=background}"
170+
--environment "Variables={AWS_LAMBDA_EXEC_WRAPPER=/opt/python/bin/elasticapm-lambda,ELASTIC_APM_LAMBDA_APM_SERVER=<YOUR-APM-SERVER-URL>,ELASTIC_APM_SECRET_TOKEN=<YOUR-APM-SECRET-TOKEN>,ELASTIC_APM_SEND_STRATEGY=background}" <1>
171171
```
172+
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.
172173
::::::
173174

174175
::::::{tab-item} SAM

docs/reference/logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The [`ecs-logging-python`](ecs-logging-python://reference/index.md) library can
2222

2323
## Log correlation [log-correlation-ids]
2424

25-
[Log correlation](docs-content://solutions/observability/apps/logs.md) allows you to navigate to all logs belonging to a particular trace and vice-versa: for a specific log, see in which context it has been logged and which parameters the user provided.
25+
[Log correlation](docs-content://solutions/observability/logs/stream-application-logs.md) allows you to navigate to all logs belonging to a particular trace and vice-versa: for a specific log, see in which context it has been logged and which parameters the user provided.
2626

2727
The Agent provides integrations with both the default Python logging library, as well as [`structlog`](http://www.structlog.org/en/stable/).
2828

docs/reference/supported-technologies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ Collected trace data:
153153
* the response status code
154154
* the count of affected rows (if available)
155155

156-
We recommend using keyword arguments only with elasticsearch-py, as recommended by [the elasticsearch-py docs](https://elasticsearch-py.readthedocs.io/en/master/api.html#api-documentation). If you are using positional arguments, we will be unable to gather the `query` element from the request body.
156+
We recommend using keyword arguments only with elasticsearch-py, as recommended by [the elasticsearch-py docs](https://elasticsearch-py.readthedocs.io/en/latest/api.html#api-documentation). If you are using positional arguments, we will be unable to gather the `query` element from the request body.
157157

158158

159159
#### SQLite [automatic-instrumentation-db-sqlite]

docs/release-notes/breaking-changes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ navigation_title: "Elastic APM Python Agent"
55
# Elastic APM Python Agent breaking changes [elastic-apm-python-agent-breaking-changes]
66
Before you upgrade, carefully review the Elastic APM RPython Agent breaking changes and take the necessary steps to mitigate any issues.
77

8-
To learn how to upgrade, check out <uprade docs>.
8+
% To learn how to upgrade, check out <upgrade docs>.
99

1010
% ## Next version [elastic-apm-python-agent-nextversion-breaking-changes]
1111
% **Release date:** Month day, year

docs/release-notes/deprecations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ navigation_title: "Elastic APM Python Agent"
55
# Elastic APM Python Agent deprecations [elastic-apm-python-agent-deprecations]
66
Review the deprecated functionality for your Elastic APM Python Agent version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade.
77

8-
To learn how to upgrade, check out <uprade docs>.
8+
% To learn how to upgrade, check out <upgrade docs>.
99

1010
% ## Next version
1111
% **Release date:** Month day, year
1212

1313
% ::::{dropdown} Deprecation title
1414
% Description of the deprecation.
1515
% For more information, check [PR #](PR link).
16-
% **Impact**<br> Impact of deprecation.
16+
% **Impact**<br> Impact of deprecation.
1717
% **Action**<br> Steps for mitigating deprecation impact.
1818
% ::::
1919

0 commit comments

Comments
 (0)