Agent Setup

Deploy the Datadog-compatible agent to start collecting infrastructure telemetry.

Deploy the agent

Go to Monitoring → Hosts in the dashboard and click Add Host. Moneat will generate a ready-to-run Docker command with your API key and endpoint already filled in - just paste it on your server.

The agent collects system metrics, processes, containers, APM traces, and logs.

Full configuration (datadog.yaml)

The generated Docker command covers basic metrics, APM, and logs. For full functionality - including container images, SBOM, database monitoring, synthetics, profiling, and other advanced tracks - the agent requires a datadog.yaml file that redirects each telemetry type to Moneat.

Copy the configuration below and save it to /etc/datadog-agent/datadog.yaml on your host (or mount it into the Docker container at that path):

YAML

# Datadog Agent configuration for Moneat
# Redirects each telemetry track to your Moneat backend

# Increase Docker check timeout (default 5s is too short on loaded hosts)
docker_query_timeout: 15

# Log Collection
logs_config:
  # Host:port only, without scheme or path. Example: api.moneat.io:443
  logs_dd_url: __MONEAT_BACKEND_URL__
  logs_no_ssl: false

# Container (contlcycle-intake, contimage-intake, sbom-intake)
container_lifecycle:
  dd_url: __MONEAT_BACKEND_URL__
container_image:
  dd_url: __MONEAT_BACKEND_URL__
sbom:
  dd_url: __MONEAT_BACKEND_URL__

# Network Device Monitoring
network_devices:
  metadata:
    dd_url: __MONEAT_BACKEND_URL__
  snmp_traps:
    forwarder:
      dd_url: __MONEAT_BACKEND_URL__
  netflow:
    forwarder:
      dd_url: __MONEAT_BACKEND_URL__

# Network Config Management
network_config_management:
  forwarder:
    dd_url: __MONEAT_BACKEND_URL__

# Network Path
network_path:
  forwarder:
    dd_url: __MONEAT_BACKEND_URL__

# Synthetics
synthetics:
  forwarder:
    dd_url: __MONEAT_BACKEND_URL__

# Data Streams
data_streams:
  forwarder:
    dd_url: __MONEAT_BACKEND_URL__

# Event Management
event_management:
  forwarder:
    dd_url: __MONEAT_BACKEND_URL__

# Database Monitoring
database_monitoring:
  metrics:
    dd_url: __MONEAT_BACKEND_URL__
  samples:
    dd_url: __MONEAT_BACKEND_URL__
  activity:
    dd_url: __MONEAT_BACKEND_URL__

# Continuous Profiling - full URL required (agent uses it verbatim, no path appended)
apm_config:
  profiling_dd_url: __MONEAT_BACKEND_URL__/api/v2/profile?api_key=<YOUR_MONEAT_AGENT_KEY>
  telemetry:
    dd_url: __MONEAT_BACKEND_URL__/dd/telemetry/proxy

Mount this file when running the agent in Docker:

Shell

docker run \
 -e DD_API_KEY=<YOUR_KEY> \
 -v /path/to/datadog.yaml:/etc/datadog-agent/datadog.yaml:ro \
 -v /var/run/docker.sock:/var/run/docker.sock:ro \
 -v /proc/:/host/proc/:ro \
 -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
 --pid host \
  gcr.io/datadoghq/agent:7

Without this configuration, tracks like container images, SBOM, database monitoring, and profiling will attempt to send to Datadog's servers instead of Moneat.

Verifying the agent

After deploying, the host appears in Monitoring → Hosts within a few minutes with CPU, memory, platform info, and agent version.

Managing API keys

Agent keys live in Settings → Agent Keys. You can see when each key was last used or revoke one to immediately block that agent from sending data.