#general

Exposing Signoz Clickhouse Setup via Ingress Controller

TLDR oluchi needed help exposing clickhouse setup using ingress. Prashant suggested checking port number and updating clickhouse.allowedNetworkIps configuration.

Join the chat

May 22, 2023 (1 week ago)

Photo of md5-0fb01baac23fe91487f6a6a93214a347

oluchi

09:01 AM

I want to take a moment to thank Signoz's team.
I am truly amazed by its functionality, ease of use, and the positive impact on our
1. developer's productivity,
2. less time trying to debug issues.
3. optimizing and improving our database and GraphQL queries
4. Cost saving ( stakeholders are happy with the impact).
Please know that your efforts are deeply appreciated and highly valued.🙇‍♂️

09:05

oluchi

09:05 AM

In between, I am trying to expose our signoz clickhouse setup via our ingress controller, Prashant, I have applied the following ingress yaml file but it seems not to work. Do I need to do any other setup

kind: Ingress
metadata:
  name: chi-signoz-clickhouse-cluster
  labels:
    : chop
    : signoz-clickhouse
    : cluster
    : infra
    : "0"
    : "0"
  annotations:
    : "cert-manager-dns"
    : "true"
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - ""
      secretName: clickhouse-staging-tls-setup
  rules:
    - host: ""
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: chi-signoz-clickhouse-cluster-0-0
                port:
                  number: 80

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

09:43 AM

it could be caused by the followings:
• port number 80 in ingress
• not allowing "Your IP" in the clickhouse.allowedNetworkIps helm configuration

09:44

Prashant

09:44 AM

oluchi may I know your use case with exposed clickhouse? it is generally recommended not expose it to public internet.

oluchi

10:53 AM

Hello Prashant, thanks for your response, we are trying to connect to the clickhouse using client libraries written in golang or python,. we no longer want to run the clickhouse query via the pod shell

May 24, 2023 (5 days ago)

Prashant

10:42 AM

oluchi are you using the same clickhouse server for your application?
It is not recommended to use one for production setup, but I don't think it is gonna be an issue in dev environment.

10:43

Prashant

10:43 AM

if your application running in K8s as well? If not, you will have to update clickhouse.allowedNetworkIps configuration

10:43

Prashant

10:43 AM

also, have you tried updating the port number from the above ingress manifest?

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Join Our Community

Similar Threads

Signoz Installation Issue on EKS due to Incorrect Credentials

Chatthana encountered an error while installing Signoz on EKS related to incorrect credentials. The issue was resolved by updating `clickhouse.allowedNetworkIps`.

1mo

SigNoz Setup Issue with External ClickHouse in Kubernetes

Ragulraj faced issues with SigNoz setup on Kubernetes using an external ClickHouse. Prashant and Srikanth provided pre-requisites and configuration steps. Ashu agreed to update the documentation.

1mo

Issues with SigNoz Setup and Data Persistence in AKS

Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.

1mo

External ClickHouse Server Installation Issue

Syed faced a connection error with an external ClickHouse server. Srikanth and Ankit suggested changing the cluster name to 'cluster'. The issue was resolved after updating the name.

1mo

Issue with Installing Latest SigNoz Version

Goutham faced issues installing latest SigNoz version with pods in initiation state. Syed suggested checking ClickHouse server. Prashant recommended running `helm upgrade` to resolve the issue.

1mo