Datadog agent

Send logs and metrics from your agent to Epok using an Epok ingest key. The key selects the workspace and project. This is agent intake; no Datadog account connection or SaaS import is involved.

Configure the agent

These are the local acceptance settings for agent 7.64.3. Replace the hosts with your Epok ingest hosts and use TLS outside a local network. Your edge must route logs to port 3100 and metrics and key validation to port 8080. Edge enablement and real-agent acceptance are still pending; these paths are not a claim of availability on the hosted service.

yaml

api_key: EPOK_INGEST_KEY
hostname: my-host
dd_url: http://localhost:8080
use_v2_api:
  series: false
serializer_compressor_kind: zlib
logs_enabled: true
logs_config:
  force_use_http: true
  logs_dd_url: localhost:3100
  logs_no_ssl: true
  use_v2_api: true
apm_config:
  enabled: false
remote_configuration:
  enabled: false

Add a file source in conf.d/my-app.d/conf.yaml:

yaml

logs:
  - type: file
    path: /var/log/my-app.log
    service: my-app
    source: application

Supported intake

POST /api/v2/logs: JSON log arrays; gzip supported.
POST /api/v1/series: JSON gauges, counts and rates; gzip and deflate supported.
GET /api/v1/validate: validates the Epok ingest key locally.
POST /api/v2/series: returns 415. Set use_v2_api.series: false; recent agents default to protobuf.

Counts accumulate into running totals; rates are multiplied by their interval before accumulation. Gauges retain their values. Metric dots become underscores, so my.app.requests is queried asmy_app_requests. Tags and host are retained as labels. Retries of the newest count/rate point do not add it twice. Older out-of-order points are rejected explicitly. Malformed v1 batches are rejected before writes; shared ingest policy may report rejected points with a 400 after storing supported points.

The agent sends DD-API-KEY; older api_key query parameters also work. Both use the same ingest-key lookup asX-API-Key. Missing or unknown keys return 401; scope failures return 403, quotas 429. Metrics bodies are capped at 8 MiB, including decompressed bytes. Metering uses the normalized metrics representation. Distribution sketches, events, service checks and agent APM are outside this compatibility row; disable those senders or configure them separately.

Verify with real agents

bash

scripts/p2_agent_acceptance.sh

From a source checkout with Docker Compose, this starts an isolated local stack and asserts exact log lines and metric values from both agents. Unit tests pass independently; the real-agent run must pass before compatibility is marked verified.