Open drazzib opened 1 month ago
Hi @drazzib, apologies about that! As a workaround, you can enable OTLP logs using spec.override
:
spec:
override:
nodeAgent:
env:
- name: DD_OTLP_CONFIG_LOGS_ENABLED
value: true
I've added a card to our backlog to add configurable otlp logs support.
Hey gang,
Just wanted to add that this got me too - I would've thought the features here would've enabled this:
features.otlp.receiver.protocols.grpc.enabled
- Enable the OTLP/gRPC endpoint. Host port is enabled by default and can be disabled.
Describe what happened:
With current release of datadog-operator, it seems datadog-agent pod is started with default
DD_OTLP_CONFIG_LOGS_ENABLED: "false"
AFAIK, there is no way to change this default value from datadog-operator (I've checked Configuration)
Describe what you expected:
As described in Ingest OpenTelemetry logs with the Datadog Agent blog post and from OTLP Ingestion by the Datadog Agent reference documentation we should be able to enable this feature
FTR, this feature has already been added into DataDog/helm-charts v3.53 release