https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
hey @Brian Richardson the troubleshooting tool returning returning 404 means that your SigNoz cluster is not reachable by the application - and hence you dont see any data in SigNoz just wanted to check - you have set address as suggseted in this grid right? - https://signoz.io/docs/install/troubleshooting/#signoz-otel-collector-address-grid
b
well no, that's what I am getting at. I am proxying the request into that port via a reverse proxy
I have tested via kubectl port-forward and it works, so sadly it seems that Traefik can't forward either Protobuf or gRPC traffic correctly, over http or https.
I don't suppose you would know of a reverse proxy configuration that would work?
p
I don't but paging @Prashant Shahi if he has any insights on this
a
@Brian Richardson I worked out nginx config to terminate ssl and do auth before otel-collectors. One difference, I am routing grpc request to relevant namespace based on response from auth. Attaching the nginx config if it helps
you can remove 
access_by_lua_block
section and directly use
Copy code
grpc_pass <grpc://my-release-signoz-otel-collector.platform.svc.cluster.local:4317>;
you can also remove the auth section
Or you can use keycloak as mentioned in the blog, though a bit harder to setup https://medium.com/opentelemetry/securing-your-opentelemetry-collector-1a4f9fa5bd6f
b
that's excellent, tyvm
8 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