expose 4318 port from otel-collector?

[jovezhong]

Hello, I installed the helm chart on GKE, using external ClickHouse. I don't see any data in HyperDX UI. I tried to follow https://clickhouse.com/docs/use-cases/observability/clickstack/getting-started/sample-data, but this will push data to "http://localhost:4318/v1", which is not available on my mac. I even configured portforward and it doesn't work.

The remote demo server https://clickhouse.com/docs/use-cases/observability/clickstack/getting-started/remote-demo-data is not working either (it mentioned sql.clickhouse.com at beginning but use https://sql-clickhouse.clickhouse.com for the configure. I login to the play UI and cannot run SQL query with that account)

Too many things are broken..

Anyway, it'll be great if the default helm chart can expose 4318/4317 port if otel-collector is enabled, otherwise, hard to push data to hyperdx

[teeohhem]

Hi there. By default, port 4317 and 4318 is exposed in the chart for the otel-collector. Are you still having issues?

[jovezhong]

Hi @teeohhem , from https://github.com/hyperdxio/helm-charts/blob/main/charts/hdx-oss-v2/templates/ingress.yaml only the app server's 3000 port is exposed. I still having issue to push data to the otel-collector. Can I just push data to 4320 or 8000 of hyperdx app?

[teeohhem]

@jovezhong Ah you're having issues pushing data to the collector outside of the cluster. I see. This is a shortcoming in the chart. The ingress controller defined in the chart is optimized for the app. Given otel speaks http/grpc, i'm not sure exposing it through ingress is the way to go.

Would something like this work for you in the meantime?

kubectl patch svc <your-release-name>-otel-collector -p '{"spec":{"type":"LoadBalancer"}}'

I'll work on a fix

[jovezhong]

Thanks. I changed it to LoadBalancer, it does open many ports but I cannot access to them

It's a "Target-pool Network Load Balancer", I have opened 4318 on my 3 VM for the GKE. Anything else need to be configured?