https://signoz.io logo
Join Slack
Powered by
<@U02SS3ZAMKQ> <@U01NT95GV8B> <@U01HWQ1RTC2> today...
# support
a
@Prashant Shahi @Srikanth Chekuri @Ankit Nayan today I logged in sample-django-deployment-6fd7b76ccc-694gz pod to test my-release-signoz-otel-collector and my-release-signoz-otel-collector-metrics if working properly, and found the command mentioned in https://signoz.io/docs/instrumentation/python run successfully but seems no any data logged in otel-collector or otel-collector-metric , I can' t see any logs in otel-collector or otel-collector-metrics as well as the dashboard , but if I telnet those endpoint, it is working and shows the logs in both , can you help on that ? yesterday @Prashant Shahi helped to checked everything I deployed cannot find any issue but Signoz just can show any data in dashboard and didn't work properly.
s
Which version of sdk/instrumentations are you using?
a
I am not sure , how to check , basically I used the same in https://github.com/SigNoz/sample-django.git
s
What does your app logs show?
a
@Srikanth Chekuri
s
My guess is that image was not built successfully with grpc. Can you configure the 
OTEL_TRACES_EXPORTER=otlp_proto_http
and 
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<http://localhost:4318/v1/traces>
and see what happens
replace localhost with correct host
a
sure
@Srikanth Chekuri I just tried on simple python and check logs seems nothing changed
Copy code
DJANGO_SETTINGS_MODULE=mysite.settings  OTEL_RESOURCE_ATTRIBUTES=service.name=c10 OTEL_TRACES_EXPORTER=otlp_proto_http  OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<http://my-release-signoz-otel-collector:4317/v1/traces> opentelemetry-instrument --traces_exporter otlp_proto_http python c10.py
even though just simple python, it should give some logs in collector ,right ?
s
4318 should be port
a
Copy code
C02XGC2HJG5H:apmtest ah1000259263$ k get svc -n edgetestteam-dev
NAME                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                                                AGE
clickhouse-operator-metrics                ClusterIP   172.30.241.212   <none>        8888/TCP                                                                               165m
my-release-clickhouse                      ClusterIP   172.30.241.222   <none>        8123/TCP,9000/TCP                                                                      160m
my-release-signoz-alertmanager             ClusterIP   172.30.240.193   <none>        9093/TCP                                                                               165m
my-release-signoz-alertmanager-headless    ClusterIP   None             <none>        9093/TCP                                                                               165m
my-release-signoz-frontend                 ClusterIP   172.30.240.21    <none>        3301/TCP                                                                               165m
my-release-signoz-otel-collector           ClusterIP   172.30.240.212   <none>        4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP,8889/TCP   165m
my-release-signoz-otel-collector-metrics   ClusterIP   172.30.240.28    <none>        4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP            165m
my-release-signoz-query-service            ClusterIP   172.30.240.208   <none>        8080/TCP                                                                               165m
my-release-zookeeper                       ClusterIP   172.30.240.51    <none>        2181/TCP,2888/TCP,3888/TCP                                                             165m
my-release-zookeeper-headless              ClusterIP   None             <none>        2181/TCP,2888/TCP,3888/TCP                                                             165m
sample-django-service                      ClusterIP   172.30.241.2     <none>        8000/TCP
I dont see 4318 port @Srikanth Chekuri @Prashant Shahi
s
even though just simple python, it should give some logs in collector ,right ?
No it doesn't if you don't have any instrumentation
It is there 4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP
a
ok
I tried both I don;t the log
Copy code
DJANGO_SETTINGS_MODULE=mysite.settings  OTEL_RESOURCE_ATTRIBUTES=service.name=c10 OTEL_TRACES_EXPORTER=otlp_proto_http  OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<http://my-release-signoz-otel-collector:4318/v1/traces> opentelemetry-instrument --traces_exporter otlp_proto_http python c10.py

DJANGO_SETTINGS_MODULE=mysite.settings  OTEL_RESOURCE_ATTRIBUTES=service.name=c10 OTEL_TRACES_EXPORTER=otlp_proto_http  OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<http://my-release-signoz-otel-collector-metrics:4318/v1/traces> opentelemetry-instrument --traces_exporter otlp_proto_http python c10.py
s
As I mentioned earlier you don't get anything if there is no instrumentation. Your c10.py has nothing that produces telemetry
✅ 1
a
got it I 'll change deployment yaml to see what happen
@Srikanth Chekuri awesome! it is working Thank you very much for your help , appreciate!
can you let me know why this is so difference between 4317 and 4318
and what scenario for 55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP,8889/TCP
@Srikanth Chekuri *^ ^
s
4317 is for gRPC and 4318 is for HTTP. Some language/runtime version may not go well with gRPC and might cause problems. You may want to take a look at the OTEL collector for all the details.
a
can you provide link ?
I only found some link for troubleshooting https://signoz.io/docs/install/troubleshooting/#signoz-otel-collector-address-grid but it just mentioned out 4317
3 Views
Open in Slack
PreviousNext
Powered by