We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe what happened:
With current release of datadog-operator, it seems datadog-agent pod is started with default DD_OTLP_CONFIG_LOGS_ENABLED: "false"
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
Add otlp.logs.enabled option to datadog agent to set the DD_OTLP_CONFIG_LOGS_ENABLED env variable.
otlp.logs.enabled
DD_OTLP_CONFIG_LOGS_ENABLED
The text was updated successfully, but these errors were encountered:
Hi @drazzib, apologies about that! As a workaround, you can enable OTLP logs using spec.override:
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.
Sorry, something went wrong.
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.
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: