Hi all, I'm new to SigNoz. I have a gRPC service t...
# support
Hi all, I'm new to SigNoz. I have a gRPC service that I am trying to instrument, and I verified that it is generating telemetry data using both the console exporter and using the OpenTelemetry collector running in Docker Desktop. I stopped the OpenTelemetry collector and installed SigNoz in Docker Desktop. I verified I can access the front end and checked the endpoint using troubleshoot.
Copy code
~/temp$ ./troubleshoot checkEndpoint --endpoint=localhost:4317
2022-09-16T09:59:00.676-0400    INFO    workspace/main.go:28    STARTING!
2022-09-16T09:59:00.676-0400    INFO    checkEndpoint/checkEndpoint.go:41       checking reachability of SigNoz endpoint
2022-09-16T09:59:00.681-0400    INFO    workspace/main.go:46    Successfully sent sample data to signoz ...
The problem is I am not seeing any data being captured in SigNoz when I hit my gRPC service. When I start the service, I have the OTEL_EXPORTER_OTLP_ENDPOINT environment variable set to http://localhost:4317. We use auto instrumentation using the following code:
Copy code
resource = Resource(attributes={"service.name": service_name})
Any ideas? Thanks!
What’s the SDK version you are using and how you running the service?
I forgot to mention, this is Python. We're OpenTelemetry 1.12.0 and gRPC is 1.47.0. Just starting the service from powershell.
Were you able to see data in console and in Collector via Docker desktop but you couldn’t see the same in SigNoz UI?
Right. I see the JSON in the console if I use the console exporter, and I can see the data dumped into the OpenTelemetry collector when it is running in Docker Desktop.
But no data is showing up in the SigNoz UI.
Interesting. Can you confirm all services of SigNoz deployment are running?
Copy code
PS D:\scratch\signoz\deploy> docker ps
CONTAINER ID   IMAGE                                          COMMAND                  CREATED         STATUS                   PORTS                              NAMES
b5aefb57e1ac   signoz/frontend:0.11.1                         "nginx -g 'daemon of…"   2 minutes ago   Up 2 minutes             80/tcp,>3301/tcp     frontend
84b2f9415307   signoz/alertmanager:0.23.0-0.2                 "/bin/alertmanager -…"   2 minutes ago   Up 2 minutes             9093/tcp                           clickhouse-setup_alertmanager_1
ced53b8b3c9d   signoz/signoz-otel-collector:0.55.1            "/signoz-collector -…"   3 minutes ago   Up 3 minutes   >4317-4318/tcp   clickhouse-setup_otel-collector_1
93580eeebfdc   signoz/signoz-otel-collector:0.55.1            "/signoz-collector -…"   3 minutes ago   Up 3 minutes             4317-4318/tcp                      clickhouse-setup_otel-collector-metrics_1
1dbf110062c3   signoz/query-service:0.11.1                    "./query-service -co…"   3 minutes ago   Up 3 minutes (healthy)   8080/tcp                           query-service
028cc4cc817a   jaegertracing/example-hotrod:1.30              "/go/bin/hotrod-linu…"   3 minutes ago   Up 3 minutes             8080-8083/tcp                      hotrod
92eacb09cae6   clickhouse/clickhouse-server:22.4.5-alpine     "/entrypoint.sh"         3 minutes ago   Up 3 minutes (healthy)   8123/tcp, 9000/tcp, 9009/tcp       clickhouse-setup_clickhouse_1
d72c2cbbec25   grubykarol/locust:1.2.3-python3.9-alpine3.12   "/docker-entrypoint.…"   3 minutes ago   Up 3 minutes             5557-5558/tcp, 8089/tcp            load-hotrod
Is this a windows machine you are using? We don’t support it as of today.
Okay. I saw that, but I was hopeful running in Docker would allow it to work. Thanks for the help.
Do you know if it will work in WSL?
IIRC Some were able to get it work in the past. Here is the issue tracker issue for the same https://github.com/SigNoz/signoz/issues/645
Thanks again! I'll give that a shot.
That worked!