![]() |
VOOZH | about |
Datadog App and API Protection (AAP) is built on top of APM and runs alongside Infrastructure Monitoring by default. While Datadog recommends using AAP together with APM and Infrastructure Monitoring to adopt DevSecOps practices, you can also run AAP on its own. This configuration is referred to as Standalone App and API Protection.
Running standalone allows to be billed primarily for App and API Protection. Some APM intake is still present to support AAP features (for example, security traces), and is expected to appear on your bill.
This guide explains how to disable APM tracing and infrastructure monitoring.
This guide assumes you have the following:
Standalone App and API Protection is supported for the following SDK versions:
| Language | Version |
|---|---|
| .NET | 3.12.0 |
| Go | 1.73.0 |
| Java | 1.47.0 |
| Node.js | 5.40.0 |
| PHP | 1.8.0 |
| Python | 3.2.0 |
| Ruby | 2.13.0 |
Standalone App and API Protection requires two pieces of configuration: disabling Infrastructure Monitoring on the Datadog Agent, and disabling APM tracing on the SDK while enabling AAP.
Standalone App and API Protection uses the same Datadog Agent installation as APM. For installation steps, see Install the Datadog Agent.
To disable Infrastructure Monitoring, set the Datadog Agent infrastructure mode to none (requires Datadog Agent 7.77.0 or newer) using either:
DD_INFRASTRUCTURE_MODE=none environment variableinfrastructure_mode: none setting in the datadog.yaml configuration fileFor more details, see Datadog Agent infrastructure mode.
On the instrumented service, set the following environment variables:
DD_APM_TRACING_ENABLED=falseDD_APPSEC_ENABLED=trueDD_APM_TRACING_ENABLED=false disabled APM tracing and limits the amount of APM data sent to the minimum required by App and API Protection. This environment variable can be combined with other App and API Protection configuration options.
| |