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
I'm trying to run a service on Google Cloud Run, with metrics, traces, and logs all going through OTLP to datadog via serverless-init.
However, when enabling OTLP logs, the agent fails to start up and no OTLP port is opened at all (connection refused to 0.0.0.0:4317).
2025-02-17 13:43:39 UTC | SERVERLESS_INIT | DEBUG | Launching subprocess [dotnet my-app.dll]
2025-02-17 13:43:39 UTC | SERVERLESS_INIT | ERROR | Error running the OTLP pipeline: invalid configuration: service::pipelines config validation failed: pipeline "logs": must have at least one receiver
Describe what you expected:
I expected the OTLP receiver to start and accept logs.
This is so that I can use any framework's native OTLP logging exporters, rather than having to mess with log forwarding via GCP dataflow, or manual JSON exporters and parsing in the agent.
Steps to reproduce the issue:
... compile my app
FROM base AS final
WORKDOR app
COPY --from=publish /app/publish .
COPY --from=datadog/serverless-init:1.5.6 / /app/
ENV DD_SITE=datadoghq.eu
ENV DD_SERVICE=notifications-api
ENV DD_ENV=unknown
ENV DD_VERSION=unknown
ENV DD_LOGS_ENABLED=true
ENV DD_APM_ENABLED=true
ENV DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_GRPC_ENDPOINT=0.0.0.0:4317
ENV DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT=0.0.0.0:4318
ENV DD_OTLP_CONFIG_LOGS_ENABLED=true
ENV DD_OTLP_CONFIG_TRACES_ENABLED=true
ENV DD_OTLP_CONFIG_METRICS_ENABLED=true
ENV DD_OTLP_CONFIG_DEBUG_VERBOSITY=detailed
ENV DD_OTLP_CONFIG_TRACES_ENABLED=true
ENV DD_LOG_LEVEL=debug
ENTRYPOINT ["/app/datadog-init", "dotnet", "my-app.dll"]
docker build -t test -f my-app/Dockerfile .&& \
docker run -it --rm --name test \
-p 8080:8080 \
-e DD_API_KEY=<snip> -e DD_ENV=local \
test
I've traced the code down to comp/otelcol/otlp/map_provider_config_serverless.go, which seems like it's just misconfiguring the OTLP receiver in serverless build mode?
Agent Environment
Docker, serverless-init, 1.5.6
Describe what happened:
I'm trying to run a service on Google Cloud Run, with metrics, traces, and logs all going through OTLP to datadog via serverless-init.
However, when enabling OTLP logs, the agent fails to start up and no OTLP port is opened at all (connection refused to 0.0.0.0:4317).
Describe what you expected:
I expected the OTLP receiver to start and accept logs.
This is so that I can use any framework's native OTLP logging exporters, rather than having to mess with log forwarding via GCP dataflow, or manual JSON exporters and parsing in the agent.
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc):
Reproducible running locally in docker.
I've traced the code down to
comp/otelcol/otlp/map_provider_config_serverless.go
, which seems like it's just misconfiguring the OTLP receiver in serverless build mode?datadog-agent/comp/otelcol/otlp/map_provider_config_serverless.go
Line 53 in d71f056
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: