Deploying Datadog
This guide provides clear, step-by-step instructions for deploying the Datadog Agent on ALPON X4 to enable robust device and container monitoring.
This guide deploys the Datadog Agent on ALPON X4 and configures host and container telemetry. The deployment mounts sensitive host paths, including the Docker socket; review the security boundary below before proceeding.
Before deployment, start the Datadog Agent installation flow in your Datadog account and enable the Docker integration. Use the official Datadog Agent documentation for current region, environment-variable, and integration settings.
Deployment
Ensure the gcr.io/datadoghq/agent:7 container is available in your Sixfab Container Registry. If it is not, follow these steps to add it:
- Open a terminal on your personal computer and pull the Datadog Agent container:\
docker pull --platform linux/arm64 gcr.io/datadoghq/agent:7 - Log in to ALPON Cloud, navigate to the Sixfab Container Registry page
- Click on + Add Container and follow the prompts to push container to Sixfab Container Registry.\
Deploy ApplicationsVisit the Deploy Applications page for all the necessary details on pushing your container image to the Sixfab Container Registry.
Alternative Deployment Option:
If you prefer not to use the Sixfab Container Registry, select the I would like to use my own container path option during deployment and enter: gcr.io/datadoghq/agent:7
This will deploy the container directly from Docker Hub.
Configuration
-
Go to the Applications section of your asset on ALPON Cloud.
-
Click the + Deploy button to configure and deploy the container.
-
In the Deploy Container window, use the following settings:
-
Container Name: datadog
-
Image: Select the Datadog image and tag pushed to the Sixfab Container Registry, or follow the steps mentioned in the 'Alternative Deployment Option'.
-
Environment: Click "+ Add More" in the environment section and add the following values:
Key Value DD_SITE YOUR_DATADOG_REGION DD_API_KEY YOUR_DATADOG_TOKEN DD_DOGSTATSD_NON_LOCAL_TRAFFIC true
-
Volumes: Click "+ Add More" in the Volumes section and configure the following volumes:
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
-
Security boundary: Access to the Docker socket is effectively host-administrator access even when mounted read-only. Deploy only a trusted, pinned Datadog Agent image; restrict who can edit the deployment and rotate the API key if it is exposed.
- Click the "+ Deploy" button to deploy Datadog.
Final Steps: Launch and Monitor
After deployment, verify that the container is running, review its logs for authentication or permission errors, and then confirm that the device appears in Datadog. Reporting delay depends on network connectivity and the Datadog service.
Related guides
Updated about 8 hours ago
