https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
@Ankit Nayan any insights on this?
s
@Blake Romano Are you using the OTLP exporter? there is likely a chance you are running into ssl/tls issues with exporter. Both SDK client and Collector need to by in sync. You may have to explicitly configure insecure connection on the exporter if you didn't setup any tls.
b
I mean I am not sure what that means.
I have this
Copy code
command: [ "opentelemetry-instrument", "--traces_exporter", "otlp_proto_http", "python3", "pywsgi.py" ]
for my command. And I know I have the endpoint proper. it is the defaults set in the helm chart.
I am seeing this now
Copy code
2022-06-20T19:45:42.688Z	warn	zapgrpc/zapgrpc.go:191	[core] grpc: Server.Serve failed to create ServerTransport:  connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"POST /v1/traces HTTP/1.1\""	{"grpc_log": true}
s
What is endpoint set to? Does it have scheme https?
b
OTEL_EXPORTER_OTLP_ENDPOINT: "<http://signoz-otel-collector.opentelemetry.svc.cluster.local:4317>"
I have it the same way as I do on a NestJS app that is sending data
s
If you are using 
otlp_proto_http
the port should 4318
b
I have tried both ports I can try changing it.
What is the difference?
s
4317 - proto/grpc 4318 proto/http
b
what is grpc?
s
RPC framework https://grpc.io/. Something like thrift in apache land.
b
That's interesting my NestJS one works with 4317
well now it works 😮
Thank you 🙂
s
Nice. Happy observing with SigNoz. You other app also works with 4317 but you explicitly mentioned you want to use proto_http instead of proto_grpc and In that case you need to make sure port is set correctly.
b
ahh makes sense
88 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by