You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/configuration.md
+20-20
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ ELASTIC_APM = {
29
29
30
30
The precedence is as follows:
31
31
32
-
*[Central configuration](#config-central_config) (supported options are marked with [](#dynamic-configuration))
32
+
*[Central configuration](#config-central_config) (supported options are marked with [](#dynamic-configuration))
33
33
* Environment variables
34
34
* Inline configuration
35
35
* Framework-specific configuration
@@ -38,7 +38,7 @@ The precedence is as follows:
38
38
39
39
## Dynamic configuration [dynamic-configuration]
40
40
41
-
Configuration options marked with the  badge can be changed at runtime when set from a supported source.
41
+
Configuration options marked with the  badge can be changed at runtime when set from a supported source.
42
42
43
43
The Python Agent supports [Central configuration](docs-content://solutions/observability/apps/apm-agent-central-configuration.md), which allows you to fine-tune certain configurations from in the APM app. This feature is enabled in the Agent by default with [`central_config`](#config-central_config).
44
44
@@ -108,7 +108,7 @@ Enable or disable the agent. When set to false, the agent will not collect any d
Copy file name to clipboardExpand all lines: docs/reference/django-support.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -171,7 +171,7 @@ ELASTIC_APM = {
171
171
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.
172
172
173
173
::::{note}
174
-
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).
174
+
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/index.md).
Copy file name to clipboardExpand all lines: docs/reference/lambda-support.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Both the [{{apm-lambda-ext}}](apm-aws-lambda://reference/index.md) and the Pytho
29
29
To add the layers to your Lambda function through the AWS Management Console:
30
30
31
31
1. Navigate to your function in the AWS Management Console
32
-
2. Scroll to the Layers section and click the *Add a layer* button 
32
+
2. Scroll to the Layers section and click the *Add a layer* button 
33
33
3. Choose the *Specify an ARN* radio button
34
34
4. Copy and paste the following ARNs of the {{apm-lambda-ext}} layer and the APM agent layer in the *Specify an ARN* text input:
35
35
* APM Extension layer:
@@ -44,7 +44,7 @@ To add the layers to your Lambda function through the AWS Management Console:
44
44
```
45
45
1. Replace `{AWS_REGION}` with the AWS region of your Lambda function.
46
46
47
-

47
+

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.
161
161
162
-

162
+

0 commit comments