This message was deleted.

My docker-compose for the web app has the following

- OTEL_EXPORTER_OTLP_SPAN_INSECURE=true
       - OTEL_EXPORTER_OTLP_METRIC_INSECURE=true
       - OTEL_METRICS_EXPORTER=none
       - OTEL_SERVICE_NAME=web1
       - OTEL_EXPORTER_OTLP_ENDPOINT=host.docker.internal:4317

I can hit "host.docker.internal:4317" from my Application, if i docker-compose run .. bash and curl/netcat/telnet to the endpoint

@Alan Ryan are you able to see your application data in SigNoz?

Hi @Pranay no, I don't see any data flow -I am going to run sample-django app now and see if that behaves differrently

@Alan Ryan The env

OTEL_EXPORTER_OTLP_*_INSECURE

are never read by SDK so it doesn't change anything. What does your setup look like? Are you running SigNoz on your machine and you services with docker-compose? It shouldn't be the issue but did you try specifying the scheme in endpoint

<http://host.docker.internal:4317>

?

Hi @Srikanth Chekuri - I am running a the dockerised clickhouse on my local machine. With hot rod running, this was giving me traces, metrics etc I then added a shared docker network, to the docker-compose, and removed hot-rod. restarted the apps came up , I could see no services listed as I expected I then bring up my dockerised django, with the same shared network

If your django is already part of same network why are you using host.docker.interal?

debugging and trying various 'hints' I saw. I had it set to

clickhouse-setup_otel-collector-metrics_1

but I got same error

That's a container name not the service name. If the djano app is already part of same n/w use the

<http://otel-collector:4317>

Same issues, I see the same message in the logs, when I run a bash shell in the container I get

root@0e12f257feb1:/home/app/# curl otel-collector:4317
curl: (1) Received HTTP/0.9 when not allowed

You can't test the grpc server (on port 4317) with curl.

just establishing that it was reachable

You are having issues with the python gRPC.

ahh..

Let's try with HTTP exporter meanwhile. Use following and check again

OTEL_TRACES_EXPORTER=otlp_proto_http
OTEL_EXPORTER_OTLP_ENDPOINT=<http://otel-collector:4318>

👍

there is definitely some issue with your n/w setup.

yeah, starting to this this is local. I'll do some debugging and get back to you 🙇