-
Notifications
You must be signed in to change notification settings - Fork 0
opentelemetry setup
You will learn how to enable, configure, and disable OpenTelemetry export in update-ipsets.
Set either of these to enable export:
export UPDATE_IPSETS_OTEL=1or set an OTLP endpoint directly:
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317The daemon detects the endpoint variable and enables export automatically.
export UPDATE_IPSETS_OTEL=0This disables export even when OTEL_EXPORTER_OTLP_ENDPOINT is set. Local structured logs continue writing to stderr regardless of this setting.
The default protocol is http/protobuf (OTLP over HTTP).
To use gRPC:
export UPDATE_IPSETS_OTEL_PROTOCOL=grpcOr:
export OTEL_EXPORTER_OTLP_PROTOCOL=grpcFor gRPC, the endpoint value requires an explicit scheme:
# Correct
export OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4317
# Incorrect — gRPC exporters reject bare host:port
export OTEL_EXPORTER_OTLP_ENDPOINT=127.0.0.1:4317Disable traces when you only want metrics and logs:
export OTEL_TRACES_EXPORTER=noneOr use the daemon-specific variables:
export UPDATE_IPSETS_OTEL_TRACES=none
export UPDATE_IPSETS_OTEL_METRICS=none
export UPDATE_IPSETS_OTEL_LOGS=noneEach variable disables one signal independently.
Control how often the daemon pushes metrics:
# Push every 10 seconds (value is milliseconds)
export UPDATE_IPSETS_OTEL_METRIC_INTERVAL=10000Or use the standard variable:
export OTEL_METRIC_EXPORT_INTERVAL=10000Shorter intervals give finer resolution but consume more network and collector resources. The installed default is 10 seconds, matching Netdata's OTel chart interval.
UPDATE_IPSETS_OTEL=1 \
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 \
update-ipsets daemon --config /opt/update-ipsets/etc/configUPDATE_IPSETS_OTEL=1 \
UPDATE_IPSETS_OTEL_PROTOCOL=grpc \
OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4317 \
OTEL_METRIC_EXPORT_INTERVAL=10000 \
OTEL_TRACES_EXPORTER=none \
update-ipsets daemon --config /opt/update-ipsets/etc/config- Daemon Command Reference
- Environment Variables
- Configuration Reload
- Listener Topologies
- Admin Authentication
- Feed Families
- Source Feeds
- Processor Reference
- Static Feeds
- Merge Feeds
- Artifact Parents
- History Derivatives
- Provider Databases
- Use Roles
- Critical Infrastructure Reference Feeds
- Legal Fields
- Feed Visibility & Lifecycle
- YAML Field Reference
- Pipeline Overview
- Download Lifecycle
- Processing Lifecycle
- Feed Status Reference
- Health Classes
- What Triggers Reprocessing
- Accessing the Admin
- Runtime Status
- Feed Inventory
- Artifact Inventory
- Live Queues
- Background Work
- Schedule State
- Operator Actions
- Enable & Disable