Deploying Datadog

Overview

The Datadog Agent collects metrics, logs, and events from a host and the containers running on it and forwards them to Datadog. Running it as a container on an ALPON X5 AI or ALPON X4 gives you host and container monitoring for the device without installing anything on the host OS: the deployment mounts the host's /proc, cgroup, Docker container, and Docker socket paths read-only so the agent can observe them.

The steps below are identical on ALPON X4 and ALPON X5 AI. For the current region, environment-variable, and integration settings, see the official Datadog Agent documentation.

1. 1

   Add the Datadog Agent container

   Make sure the gcr.io/datadoghq/agent:7 image is available to your device. The recommended path is to push it to your Sixfab Container Registry so deployments are fast and work offline. From your build machine, pull the arm64 image:

   bash · pull the image

   docker pull --platform linux/arm64 gcr.io/datadoghq/agent:7

   Then log in to Sixfab Registry, click + Add Container, and follow the prompts to push the image.

   Pushing images to the Sixfab Container Registry

   For the full walkthrough of tagging and pushing an image, see Update Containers from the Sixfab Container Registry.

   Alternative: deploy straight from the public registry

   If you prefer not to use the Sixfab Container Registry, choose “I would like to use my own container path” during deployment and enter gcr.io/datadoghq/agent:7. The container is then pulled directly from Google Container Registry (the device needs internet access at deploy time).

2. 2

   Deploy the container on ALPON

   Open your device in ALPON Cloud, go to the Applications section, and click + Deploy. In the Deploy Container window, use these settings:

   Container Name datadog

   Image The Datadog image and tag you pushed to the Sixfab Container Registry — or, using the alternative option, gcr.io/datadoghq/agent:7.

   Environment Click + Add More and add the three variables in the first table below.

   Volumes Click + Add More and add the four read-only volumes in the second table below.

   Environment variables — replace the placeholders with the site and API key from your Datadog account:

   Key	Value
   DD_SITE	YOUR_DATADOG_REGION
   DD_API_KEY	YOUR_DATADOG_TOKEN
   DD_DOGSTATSD_NON_LOCAL_TRAFFIC	true

   Volumes — all four are mounted read-only:

   Access	Local Path	Target Path
   Read-only	/var/run/docker.sock	/var/run/docker.sock
   Read-only	/proc/	/host/proc/
   Read-only	/sys/fs/cgroup/	/host/sys/fs/cgroup/
   Read-only	/var/lib/docker/containers	/var/lib/docker/containers

   Click + Deploy to launch the Datadog Agent on the device.

3. 3

   Verify the device reports to Datadog

   Once the deployment finishes, confirm the datadog container shows as running in the Applications section and review its logs for authentication or permission errors — an invalid DD_API_KEY or wrong DD_SITE shows up there first.

   Then open your Datadog account and confirm the device appears as a host. Reporting delay depends on network connectivity and the Datadog service, so allow a few minutes for the first data to arrive.