Cette page n'est pas encore disponible en français, sa traduction est en cours. Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
Universal Service Monitoring requires that the Datadog Agent installed alongside your containerized service be at least version 6.40 or 7.40. As noted below, some features in Preview require higher versions.
Supported Linux platforms
Linux Kernel 4.14 and greater CentOS or RHEL 8.0 and greater
Supported Windows platforms
Windows 2012 R2 and greater
Supported application-layer protocols
HTTP HTTPS (OpenSSL)
Known limitations
Universal Service Monitoring requires the use of Datadog’s system-probe, which is not supported on Google Kubernetes Engine (GKE) Autopilot.
Additional protocols and traffic encryption methods are in Preview. If you have feedback about what platforms and protocols you'd like to see supported, contact Support.
Enable Universal Service Monitoring in your Agent by using one of the following methods depending on how your service is deployed and your Agent configured:
To enable Universal Service Monitoring with the Datadog Operator, update your datadog-agent.yaml manifest. In the DatadogAgent resource, set spec.features.usm.enabled to true:
Enable Universal Service Monitoring with the following environment variables in the Agent daemonset. If you are running a container per Agent process, add the following environment variables to the process-agent container. Otherwise, add them to the agent container.
As Docker Swarm does not yet support the changing of security_opt, the operating system
must not have a running apparmor instance.
If the operating system does not have a running apparmor instance, use the same docker-compose.yml file from the Docker-Composesection beside the field security_opt.
If you are not using Helm Charts or environment variables, set the following in your system-probe.yaml file:
service_monitoring_config:enabled:true
If you configure the system-probe with environment variables, as is common with Docker and ECS installations, pass the following environment variable to both the process-agent and system-probe:
If you use load balancers with your services, enable additional cloud integrations to allow Universal Service Monitoring to discover cloud-managed entities:
Install the AWS Integration for visibility in AWS Load Balancer.
Enable ENI and EC2 metric collection.
Add the following tags to each load balancer:
ENV=<env>
SERVICE=<service>
For services running on IIS:
Install the Datadog Agent (version 6.41 or 7.41 and later) with the network kernel device driver component enabled.
For Agent version 7.44 or earlier, you must pass ADDLOCAL="MainApplication,NPM" to the msiexec command during installation, or select Cloud Network Monitoring when running the Agent installation through the GUI.
Edit C:\ProgramData\Datadog\system-probe.yaml to set the enabled flag to true:
service_monitoring_config:enabled:true
For non-IIS services:
Discovery of non-IIS services is enabled by default starting with Agent version 7.57. Previous Agent versions may require the following configuration change to system-probe.yaml:
Universal Service Monitoring is available to monitor services behind Istio mTLS and to capture encrypted HTTPs, HTTP/2, and gRPC traffic.
Requires Agent version 7.50 or greater.
Use http_replace_rules or DD_SYSTEM_PROBE_NETWORK_HTTP_REPLACE_RULES to configure the Agent to drop HTTP endpoints that match a regex, or to convert matching endpoints into a different format.
Support for additional protocols and encryption methods
USM is in Preview for discovering cloud services and decoding additional protocols and traffic encryption methods. For more information and to request access to the Preview, read Cloud Service Discovery and Additional Protocols.