https://signoz.io logo
#general
Title
# general
p

prasanth kumar

03/01/2023, 12:25 PM
I haved setup the signoz with opentelemetry on kubernetes cluster, Installed the Opentelemetry collector, opentelemetry collector, and signoz. But not getting the traces on the signoid dashboard. Can anybody help me in this?
s

Srikanth Chekuri

03/02/2023, 12:30 AM
This is vauge. Please provide some context to help people to help you with troubleshooting. How did you configure the SDK? What language/framework are you using? What do the logs show? The more context the better.
p

prasanth kumar

03/02/2023, 5:55 AM
I installed the opentelemetry-collector helm chart and opentelemetry-operator for collecting the metrics,logs and traces. Then I followed this https://signoz.io/docs/install/kubernetes/aws/ blog, and installed the signoz/signoz helm chart. And I also added instrumentation.opentelemetry.io/inject-nodejs: "true" to all the deployments. To auto instrumenting the node JS application, Is the pods and the opentelemetry operator should be on the same namespace? or there anything I need to configure in signoz to collect the OLTP metrics,logs and tracing? In the dashboard there are no services visible
@Srikanth Chekuri
s

Srikanth Chekuri

03/02/2023, 6:55 AM
Did you configure the operator to send the data to SigNoz?
p

prasanth kumar

03/02/2023, 8:01 AM
No what are the things to configure in opentelemetry operator?
I just used the default helm chart values @Srikanth Chekuri bro
s

Srikanth Chekuri

03/02/2023, 8:03 AM
no worries bro, you need to set the
OTEL_EXPORTER_OTLP_ENDPOINT
to signoz collector instance with the appropriate host and port https://github.com/open-telemetry/opentelemetry-operator/#opentelemetry-auto-instrumentation-injection
p

prasanth kumar

03/02/2023, 9:13 AM
Okay thank you @Srikanth Chekuri I have added the same and replaced the OTEL_EXPORTER_OTLP_ENDPOINT with the service name and port. Do we need to add the operator and signoz on the same namespace where the deployments are present?
Can you send the exact annotation that need to add to the deployment files which is present in other namespace
Because still not getting any metrics
Hello @Srikanth Chekuri, this is the error found in the signoz otel agent {"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 172.20.8.1944317 connect: connection refused\"", "interval": "29.487567842s"}
@Vishal Sharma bro can you please check?
s

Srikanth Chekuri

03/02/2023, 11:27 AM
It says the exporter can’t establish the connection. Please configure with the correct endpoint.
p

prasanth kumar

03/02/2023, 11:42 AM
@Srikanth Chekuri bro I have used this as endpoint opentelemetry-collector.monitoring.svc.cluster.local:4318 opentelemetry-collector:4318 http://opentelemetry-collector:4318 I have tried all the above three ways to connect
@Srikanth Chekuri bro , do we need to add anything to the code?
s

Srikanth Chekuri

03/02/2023, 1:55 PM
no bro, you don’t need to add anything to the code. I don’t think you are setting the endpoint correctly. the above urls you shared don’t appear to be correct. Are these the signoz namespace collector endpoints?
p

prasanth kumar

03/03/2023, 4:39 AM
yes @Srikanth Chekuri bro signoz is deployed on monitoring namespace
5 Views