Skip to main content

Deploy with Helm Charts

Steps:

  1. Install SigNoz backend as instructed in this page
  2. Instrument your application as instructed in Instructions Page

Getting Started

The easiest way to get started with SigNoz on Kubernetes is to install using helm charts, this will install

  • Query Service (Backend service)
  • Web UI (Frontend)
  • ClickHouse instance (Datastore)
  • OpenTelemetry collector
  • Alert Manager

Steps to Deploy SigNoz

git clone https://github.com/SigNoz/signoz.git && cd signoz

helm dependency update deploy/kubernetes/platform

kubectl create ns platform

helm -n platform install signoz deploy/kubernetes/platform

*If you choose a different namespace, you need to point your applications to correct address to send traces. In our sample application just change the JAEGER_ENDPOINT environment variable in sample-apps/hotrod/deployment.yaml

Test HotROD application with SigNoz

kubectl create ns sample-application

kubectl -n sample-application apply -Rf sample-apps/hotrod/

How to generate load

kubectl -n sample-application run strzal --image=djbingham/curl \
--restart='OnFailure' -i --tty --rm --command -- curl -X POST -F \
'locust_count=6' -F 'hatch_rate=2' http://locust-master:8089/swarm

See UI

kubectl -n platform port-forward svc/signoz-frontend 3000:3000

How to stop load

kubectl -n sample-application run strzal --image=djbingham/curl \
--restart='OnFailure' -i --tty --rm --command -- curl \
http://locust-master:8089/stop

How to instrument your own applications

Checkout Instrumentation Section

Increase ClickHouse persistent volume size in EKS/GKE

Use the command below to increase PV size from default 20Gi to 25Gi:

helm -n platform upgrade signoz deploy/kubernetes/platform --set clickhouseOperator.storage=25Gi

*The above Helm upgrade command overrides the default values from values.yaml using --set flag for each execution. Alternatively, you can pass updated values.yaml file using -f flag.