You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While attempting to configure consul-k8s integration to datadog using Datadog's built-in OTLP receiver options for gRPC and HTTP, I found that configuring the gRPC external endpoint outside of the helm value overrides was not possible as it was with the HTTP endpoint.
Datadog Operator Values
apiVersion: datadoghq.com/v2alpha1kind: DatadogAgentmetadata:
name: datadogspec:
features:
# Sets: DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_GRPC_ENDPOINT: 0.0.0.0:4317 │# DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT: 0.0.0.0:4318otlp:
receiver:
protocols:
# Set to "0.0.0.0" as per the below reference docs# ref: https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent/?tab=host#enabling-otlp-ingestion-on-the-datadog-agentgrpc:
enabled: trueendpoint: "0.0.0.0:4317"
Description
While attempting to configure consul-k8s integration to datadog using Datadog's built-in OTLP receiver options for gRPC and HTTP, I found that configuring the gRPC external endpoint outside of the helm value overrides was not possible as it was with the HTTP endpoint.
Datadog Operator Values
Consul Overrides
Potential Resolution
CO_OTEL_HTTP_ENDPOINT
for gRPC receivershttp-collector-endpoint
for gRPC receiversVersion
Image:
hashicorp/consul-telemetry-collector:0.0.2
The text was updated successfully, but these errors were encountered: