#support

Troubleshooting: No Tracing Data Exported from Docker Container

TLDR Hassan couldn't export tracing data from the otel-collector, but resolved it by running all containers on the same external network. Olawale experienced a similar issue.

2mo

Join the chat

Sep 14, 2023 (2 months ago)

Photo of md5-f65268c6d9abf7caf32b1b3cb9d79051

Hassan

03:38 PM

My app_backend is running inside docker container on shared network (clickhouse_setup_default) and i could ping otel-collector from inside my app_backend container but the service is not being created and no tracing data is exported.

I have tried almost everything and not sure what could be the issue
tried both gprc and http port for export url and also with out /v1/traces
exportUrls tried
otel-collector:4318/v1/traces
otel-collector:4317/v1/traces
otel-collector:4318
otel-collector:4317
<http://172.18.0.6:4318/v1/traces>
while 172.18.0.6 is ip of the signoz-otel-collector container.

Image 1 for My app_backend is running inside docker container on shared network (clickhouse_setup_default) and i could ping `otel-collector` from inside my app_backend container but the service is not being created and no tracing data is exported.

I have tried almost everything and not sure what could be the issue
tried both gprc and http port for export url and also with out `/v1/traces`
exportUrls tried
`otel-collector:4318/v1/traces`
`otel-collector:4317/v1/traces`
`otel-collector:4318`
`otel-collector:4317`
`<http://172.18.0.6:4318/v1/traces>`
while `172.18.0.6` is ip of the signoz-otel-collector container.

03:47

Hassan

03:47 PM

I have checked with Console Exporter the telemetry data is being generated

Sep 16, 2023 (2 months ago)

Photo of md5-2f0cae259808980d42cc78426ad1396e

Olawale

02:41 PM

I have the same issue. Check the log of the Signoz-otel-collector container. You might see the error.

In my case, the error is
"error": "clickhouse: dateTime overflow. timestamp must be between 1925-01-01 00:00:00 and 2283-11-11 00:00:00"}

Sep 20, 2023 (2 months ago)

Hassan

12:36 AM

Just to clear for future viewer in my case the issue was this
Signoz containers run on network clickhouse-setup-default which comes from docker-compose spec that your network is created with project name (i.e directory name) suffixed with -default.
And my app containers were running on network my-app-name-default so i had to run all of these on same network.
I created an external network and added them to all services of docker-compose.yml in Signoz as well as my app's docker compose services. In such case they no more create and join default network and containers are able to communicate with each other over docker network.

This resolved issue for me.

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Troubleshooting Clickhouse Exporter Error

ELLIOTTCABLE encountered an error with Clickhouse exporters, likely due to a misconfiguration hinted by Srikanth. This was confirmed when ELLIOTTCABLE realized that Clickhouse's HTTP protocol was not implemented. The user subsequently inquired about HTTP-protocol support or alternative configurations.

1mo

Issues with Installing Signoz on Standalone VM with Two Additional Disks

vvpreo is having difficulty installing Signoz on a standalone VM due to an issue with OTEL collector not starting because of migration problems. Ankit and vishal-signoz proposed various solutions, but the issue remained unresolved. They planned a screen-sharing session to resolve it.

2mo

Configuring Logs in Signoz and Clickhouse

Varaprasad queries on pushing logs to ClickHouse and analyzing from SigNoz. Srikanth advises using `signoz-otel-collector` and shares a guide. Varaprasad explains their plan of action. Ankit confirms vector parsing and sharding setup in ClickHouse.

1mo