Agent Profiling Check

Supported OS Linux Mac OS Windows

Overview

This check should be used when troubleshooting a memory or CPU issue in the Agent. After a user-configured memory or CPU threshold is exceeded, a flare with profiles is automatically generated. This flare can be generated locally or sent directly to a Datadog Support case. A valid ticket_id and user_email must be provided in the conf.yaml for the flare to be sent directly to a Support case. It is otherwise generated locally.

Setup

Installation

The System check is included in the Datadog Agent package. No additional installation is needed on your server.

Configuration

  1. Edit the agentprofiling.d/conf.yaml file in the conf.d/ folder at the root of your Agent’s configuration directory. See the sample agentprofiling.d/conf.yaml for all available configuration options. Note: At least one entry is required under instances to enable the check, for example:

    init_config:
    instances:
        - memory_threshold: 1GB
          cpu_threshold: 50
          ticket_id: # Given by Support
          user_email: # Email used in correspondence with Support
    
  2. Restart the Agent.

Validation

Run the Agent’s status subcommand and look for agentprofiling under the Checks section.

Data collected

Metrics

The Agent Profiling check does not include any metrics.

Events

The Agent Profiling check does not include any events.

Service checks

The Agent Profiling check does not include any service checks.

PREVIEWING: guacbot/translation-pipeline