You can customize the Atatus Java APM Agent’s behavior through Java runtime system properties or environment variables.

Configurations

You can set the following configurations in the Java agent: All Java system properties use the prefix atatus. as shown below:

Set App Version

If you use a version to identify releases of your application, you can send it to Atatus using service_version. Setting service_version helps track performance regressions and errors across different releases.

Set Environment

If you are tracking multiple environments (e.g., Development, Staging, Production) within a single APM project, you can set the environment as follows:

Enable API Analytics

API Analytics collects all requests individually with rich contextual data such as request headers, response headers, request body, and response body.

Enable Capture Body in API Analytics

The capture body option is disabled by default. If you want to view the request body in traces, you can enable this option. The body will be captured only for the following Content-Types: application/x-www-form-urlencoded, text/*, application/json, and application/xml.

Ignore Log Body URLs

Using this option, you can avoid capturing request bodies for specific URLs. This allows you to prevent sensitive data (such as login credentials or payment details) from being sent to Atatus. Ignored URLs can be specified as strings or wildcards/regex.

Ignore URLs

Using this option, you can exclude specific URLs from being monitored by Atatus. For example, you may want to exclude health check endpoints such as /health, /ping, heartbeat, or internal admin routes. Ignored URLs can be strings with wildcard patterns or regular expressions.

Ignore HTTP Methods

Used to restrict requests with certain HTTP methods from being instrumented. This property should be set to a comma-separated list or an array containing one or more HTTP method names. When an incoming HTTP request is detected, its method will be tested against each element in this list.

Enable Debug Log Level

If you are facing issues with Java APM (e.g., missing data, agent initialization issues), you can enable the debug log level in JVM options and share the logs with success@atatus.com. The available log levels are ERROR, WARN, INFO, and DEBUG.

Set log file

By default, the agent writes its logs to standard output. To write them to a file instead, set log_file to the full path of the log file. You can pass it as a Java system property:
Or set it as an environment variable:
You can use _AGENT_HOME_ in the path as a placeholder for the folder that contains atatus-java-agent.jar, for example _AGENT_HOME_/logs/atatus-java-agent.log. When the log file reaches log_file_size (default 50mb), the agent rolls it over and keeps one older file, so the logs use about twice that size on disk. To change the size, pass log_file_size as a Java system property:
Or set it as an environment variable:
Make sure the user running your application can write to the log file’s folder.

Ignore Status Codes

Using this option, you can add a list of HTTP status codes that you don’t want to see in error metrics. This option accepts comma-separated 4xx and 5xx status codes.

Set Application Package Path

You can configure your application package path so Atatus can accurately identify in-app stack frames and pinpoint the exact source line in Java exceptions.

Trace Methods

Using this option, you can create transactions or spans for specific methods using a pointcut-like syntax. This is useful for instrumenting custom code or unsupported frameworks.
For detailed syntax, matching patterns, and examples, see Trace Methods.

Disable Agent

Using this option, you can completely disable the agent, including instrumentation and remote config polling. Set enabled to false to disable the agent.

Proxy Configuration

You can configure the Atatus Java Agent to connect via a proxy server when direct internet access is restricted by a firewall. HTTPS Proxy:
HTTP Proxy: