Config lists every Edge configuration option.
Configuration File Edge uses a JSON configuration file. Pass the path as the first argument:
Full Example { "listen_address" : "0.0.0.0" , "listen_port" : 8080 , "upstream_url" : "https://agent-http-intake.logs.datadoghq.com" , "logs_url" : "https://agent-http-intake.logs.datadoghq.com" , "metrics_url" : "https://api.datadoghq.com" , "log_level" : "info" , "max_body_size" : 1048576 , "service" : { "name" : "edge" , "namespace" : "production" , "resource_attributes" : [ { "key" : "deployment.environment" , "value" : "production" } ], "labels" : [{ "key" : "team" , "value" : "platform" }] }, "policy_providers" : [ { "id" : "local" , "type" : "file" , "path" : "/etc/edge/policies.json" }, { "id" : "remote" , "type" : "http" , "url" : "${TERO_CONTROL_PLANE_URL}/v1/policy/sync" , "poll_interval" : 30 , "headers" : [ { "name" : "Authorization" , "value" : "Bearer ${TERO_API_TOKEN}" } ] } ] }
Any string value can reference an environment variable with ${VAR} (for
example ${TERO_API_TOKEN}). See Environment
Variables . Configuration Reference Edge supports up to 8,000 policies. Open an issue on
GitHub if you need more. Server Settings Field Type Default Description listen_addressstring "127.0.0.1"IP address to bind to listen_portnumber 8080Port to listen on max_body_sizenumber 1048576Maximum request body size in bytes (1MB default) log_levelstring "info"Logging level: debug, info, warn, err
Upstream Settings Field Type Required Description upstream_urlstring Yes Default upstream destination (fallback when specific URLs not set) logs_urlstring No Upstream destination for log endpoints (falls back to upstream_url) metrics_urlstring No Upstream destination for metrics endpoints (falls back to upstream_url)
Service Settings The service object identifies this Edge instance to the control plane and
attaches metadata to policy sync requests. Always set name, namespace, and
version — the control plane uses them to scope and match policies to this
service. resource_attributes and labels are optional but recommended.
{ "service" : { "name" : "edge" , "namespace" : "production" , "resource_attributes" : [ { "key" : "deployment.environment" , "value" : "production" } ], "labels" : [{ "key" : "team" , "value" : "platform" }] } }
Field Type Required Description namestring Recommended Service name (default "tero-edge") namespacestring Recommended Service namespace (default "tero") versionstring Recommended Service version (default "latest") resource_attributesarray No OTel resource attributes ({key, value}) sent on policy sync labelsarray No Free-form labels ({key, value}) sent on policy sync
instance_id is generated at startup and is not configurable.
Policy Providers The policy_providers array configures where Edge loads policies from.
File Provider Loads policies from a local file and watches for changes.
{ "id" : "local" , "type" : "file" , "path" : "/etc/edge/policies.json" }
Field Type Required Description idstring Yes Unique identifier for this provider typestring Yes Must be "file" pathstring Yes Path to the policy file
Edge watches the file with inotify (Linux) or kqueue (macOS) and applies changes
on save.
HTTP Provider Loads policies from an HTTP endpoint with periodic polling.
{ "id" : "remote" , "type" : "http" , "url" : "https://api.example.com/policies" , "poll_interval" : 30 , "headers" : [ { "name" : "Authorization" , "value" : "Bearer token" } ] }
Field Type Required Description idstring Yes Unique identifier for this provider typestring Yes Must be "http" urlstring Yes URL to fetch policies from poll_intervalnumber No Seconds between policy fetches headersarray No HTTP headers to include in requests
Prometheus Settings The optional prometheus object bounds memory use when filtering Prometheus
scrapes (relevant to distributions that handle metrics).
{ "prometheus" : { "max_input_bytes_per_scrape" : 10485760 , "max_output_bytes_per_scrape" : 10485760 } }
Field Type Default Description max_input_bytes_per_scrapenumber 10485760Max bytes read from upstream per scrape (10MB) max_output_bytes_per_scrapenumber 10485760Max bytes forwarded to the client per scrape (10MB)
Define policies in a JSON file:
{ "policies" : [ { "id" : "policy-1" , "name" : "Human-readable name" , "description" : "What this policy does" , "enabled" : true , "log" : { "match" : [ ... ], "keep" : "..." , "transform" : { ... } } }, { "id" : "policy-2" , "name" : "Another policy" , "metric" : { "match" : [ ... ], "keep" : true } } ] }
See the Policies section for detailed
policy configuration.
Environment Variables Edge reads environment variables two ways.
Value Substitution Any string value in the config file can reference an environment variable with
${VAR}. The variable is resolved when the config loads:
{ "upstream_url" : "https://agent-http-intake.logs.${TERO_DD_REGION}.datadoghq.com" , "policy_providers" : [ { "id" : "remote" , "type" : "http" , "url" : "${TERO_CONTROL_PLANE_URL}/v1/policy/sync" , "headers" : [ { "name" : "Authorization" , "value" : "Bearer ${TERO_API_TOKEN}" } ] } ] }
Unset variables resolve to an empty string.
Use $${VAR} to emit a literal ${VAR} without substitution.
Field Overrides A TERO_-prefixed environment variable overrides the matching config field. The
name is the field path in SCREAMING_SNAKE_CASE, with nested fields joined by
_. Overrides win over the file.
Variable Overrides TERO_LOG_LEVELlog_levelTERO_LISTEN_PORTlisten_portTERO_UPSTREAM_URLupstream_urlTERO_MAX_BODY_SIZEmax_body_sizeTERO_SERVICE_NAMEservice.name
TERO_LOG_LEVEL = debug TERO_LISTEN_PORT = 9090 ./edge config.json
Next Steps
Operations Logging, health checks, and resource requirements
Log Filtering Configure log filtering policies
