IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Core configuration options Logging configuration options »

›

HTTP configuration options

edit

HTTP configuration options

edit

`capture_body`

edit

For transactions that are HTTP requests, the Java agent can optionally capture the request body (e.g. POST variables).

Possible values: errors, transactions, all, off.

If the request has a body and this setting is disabled, the body will be shown as [REDACTED].

For requests with a content type of multipart/form-data, any uploaded files will be referenced in a special _files key. It contains the name of the field, and the name of the uploaded file, if provided.

request bodies often contain sensitive values like passwords, credit card numbers etc.If your service handles data like this, we advise to only enable this feature with care.

Valid options: OFF, ERRORS, TRANSACTIONS, ALL

Default	Type	Dynamic
`OFF`	EventType	true

Java System Properties	Property file	Environment
`elastic.apm.capture_body`	`capture_body`	`ELASTIC_APM_CAPTURE_BODY`

`ignore_urls`

edit

Used to restrict requests to certain URLs from being instrumented.

This property should be set to an array containing one or more strings. When an incoming HTTP request is detected, its URL will be tested against each element in this list. Entries can have a wildcard at the beginning and at the end. Prepending an element with (?i) makes the matching case-insensitive.

All errors that are captured during a request to an ignored URL are still sent to the APM Server regardless of this setting.

Default	Type	Dynamic
`/VAADIN/, (?i)/heartbeat/, /favicon.ico, .js, .css, .jpg, .jpeg, .png, .webp, .svg, .woff, *.woff2`	List	true

Java System Properties	Property file	Environment
`elastic.apm.ignore_urls`	`ignore_urls`	`ELASTIC_APM_IGNORE_URLS`

`ignore_user_agents`

edit

Used to restrict requests from certain User-Agents from being instrumented.

When an incoming HTTP request is detected, the User-Agent from the request headers will be tested against each element in this list. Entries can have a wildcard at the beginning and at the end. Prepending an element with (?i) makes the matching case-insensitive. Example: curl/*, (?i)*pingdom*

All errors that are captured during a request by an ignored user agent are still sent to the APM Server regardless of this setting.

Default	Type	Dynamic
`<none>`	List	true

Java System Properties	Property file	Environment
`elastic.apm.ignore_user_agents`	`ignore_user_agents`	`ELASTIC_APM_IGNORE_USER_AGENTS`

« Core configuration options Logging configuration options »