Configure the gateway and instrumentation

Connect a local collector to the DDOSCOM Eyenode gateway to send metrics with OAuth 2.0 and OTLP/HTTP. Choose the agent you already operate; both use the same gateway contract.

Before you start

You need a Prometheus endpoint reachable from the collector, an OAuth 2.0 client enabled for the gateway, and secure environment-variable delivery. Do not commit secrets or place them in shared configuration files.

Gateway variables

Provide these values through your secret manager, deployment system, or an untracked local .env file:

OTEL_GATEWAY_ENDPOINT=https://otel-gateway.ddoscom.tech
OTEL_GATEWAY_OAUTH_TOKEN_URL=https://auth.ddoscom.tech/application/o/token/
OTEL_GATEWAY_OAUTH_CLIENT_ID=eyenode-gateway

# Use base64(username:app_password). Do not use the OAuth provider client secret.
OTEL_GATEWAY_OAUTH_CLIENT_SECRET=base64-client-username-and-app-password
OTEL_GATEWAY_OAUTH_SCOPE=openid

Get OTEL_GATEWAY_OAUTH_CLIENT_SECRET from the Secrets section in the Eyenode Dashboard. It is sensitive: rotate it under your organization’s policy and do not expose it in logs, shared terminals, or tickets.

Choose your guide

1. OpenTelemetry Collector for OTel YAML configuration.
2. Grafana Alloy for Alloy configurations with Prometheus and OTel components.
3. Gateway troubleshooting if authentication, scraping, or delivery does not work as expected.

[!NOTE] The initial configurations enable only the metrics pipeline. Add independent pipelines when you are ready to send logs or traces.