Skip to content

Configure Ingress for both HTTP and GRPC otelCollector #7398

@c5racing

Description

@c5racing

This doc is great for getting self hosted running behind NGINX: https://signoz.io/docs/tutorial/setting-up-tls-for-signoz. It works out of the box for GRPC and the web front end. Unfortunately, the HTTP collector doesn't receive ingress traffic.

Can I get some assistance in setting up the ingress traffic for the HTTP collector?

If I configure my values.yaml file as the following, my GRPC quits working:

ingress: enabled: true className: nginx hosts: - host: signoz-ingest.example.com paths: - path: /v1/traces pathType: ImplementationSpecific port: 4318 # HTTP ingestion - path: /v1/metrics pathType: ImplementationSpecific port: 4318 # HTTP ingestion - path: /v1/logs pathType: ImplementationSpecific port: 4318 # HTTP ingestion - path: / pathType: ImplementationSpecific port: 4317 # GRPC ingestion tls: - secretName: signoz-ingest-tls-cert hosts: - signoz-ingest.example.com annotations: cert-manager.io/cluster-issuer: letsencrypt-production nginx.ingress.kubernetes.io/ssl-redirect: "true"

If I add back in nginx.ingress.kubernetes.io/backend-protocol: "GRPC" under annotataions, then my HTTP quits working

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions