SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

We have a avg 14 Million spans generated per hour

Hey <@U049YUKH0PM> :wave:

Troubleshooting only supports gRPC endpoint that would be `172.17.0.1:4317` instead.

You can use telemetrygen instead to check OTLP http endpoint.

<https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen@v0.76.3#section-readme>

&gt; ```Connection aborted.', RemoteDisconnected('Remote end closed connection without response'```
it is possible that either the endpoint is not right or the signoz otel-collector is not healthy.

Generating telemetry data isn;t the problem, the problem is knowing whats happening inside collector. Is there any debug log option in collector docker-compose which can enable some logs telling where exactly otel-collector might be failing?

You can use logging exporter with `loglevel` set to either `warn` or `error`.

Ref: <https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/loggingexporter/README.md>

Update otel-collector config to include the `logging` exporter. Remember to include it in all desired pipelines as well.