# SigNoz Generated on 31 Jul 2025 from [the SigNoz catalog page](https://marketplace.digitalocean.com/apps/signoz) SigNoz is designed from the ground up to integrate with OpenTelemetry seamlessly and is open source. This native compatibility ensures that SigNoz can fully leverage the rich, standardised data produced by OpenTelemetry without *requiring complex workarounds* or *additional translation layers*. This *holistic approach* simplifies debugging and performance analysis by allowing developers to correlate logs, traces, and metrics effortlessly. - **Application Performance Monitoring**: Monitor metrics, logs, and traces across your entire Railway application stack. - **Debugging and Troubleshooting**: Correlate logs, metrics, and traces to quickly identify and resolve issues. - **Infrastructure Observability**: Monitor system health, resource usage, and service dependencies in real time. - **Alerting and Incident Response**: Set up alerts based on metrics and log patterns for proactive incident management. ## Software Included *This Marketplace listing does not include a detailed software list.* ## Creating an App using the Control Panel Click the **Deploy to DigitalOcean** button to install a Kubernetes 1-Click Application. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account. [![Deploy to DO](https://www.deploytodo.com/do-btn-blue.svg)](https://cloud.digitalocean.com/kubernetes/clusters/new?addonslug=signoz&nodePools=s-1vcpu-2gb%3A3) ## Creating an App using the API In addition to creating SigNoz using the control panel, you can also use the [DigitalOcean API](https://docs.digitalocean.com/reference/api). As an example, to create a 3 node DigitalOcean Kubernetes cluster made up of Basic Droplets in the SFO2 region, you can use the following `doctl` command. You need to authenticate with `doctl` with your [API access token](https://docs.digitalocean.com/reference/api/create-personal-access-token/index.html.md) and replace the `$CLUSTER_NAME` variable with the chosen name for your cluster in the command below. ```shell doctl kubernetes clusters create --size s-4vcpu-8gb $CLUSTER_NAME --1-clicks signoz ``` ## Getting Started After Deploying SigNoz ## Getting Started with SigNoz on DigitalOcean Kubernetes ## Prerequisites - A DigitalOcean Kubernetes cluster (1.19+) - `kubectl` configured to connect to your cluster - `doctl` CLI tool installed and configured - Helm 3.x installed ## Connect to Your Cluster Follow the [DigitalOcean Kubernetes connection guide](https://docs.digitalocean.com/products/kubernetes/how-to/connect-to-cluster/index.html.md) to connect to your cluster with `kubectl`. ## Install SigNoz Add-on The SigNoz add-on will be automatically installed in your cluster through the DigitalOcean Marketplace. ## Verify SigNoz Installation ### Check Helm Installation Status First, check if the Helm installation was successful by running the following command: ``` helm ls -n signoz ``` You should see output similar to: ``` NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION signoz signoz 1 2025-07-04 04:00:51.260047 +0530 IST deployed signoz-0.85.0 v0.88.0 ``` ### Check SigNoz Pods Next, verify that all SigNoz pods are running correctly: ``` kubectl get pods -n signoz ``` You should see all pods in `Running` status: ``` NAME READY STATUS RESTARTS AGE chi-signoz-clickhouse-cluster-0-0-0 1/1 Running 0 5m signoz-0 1/1 Running 0 5m signoz-otel-collector-6b7c8d9f5e-abc34 1/1 Running 0 5m signoz-clickhouse-operator-abc123 1/1 Running 0 5m signoz-zookeeper-0 1/1 Running 0 5m ``` ### Check Services Verify that SigNoz services are created and accessible: ``` kubectl get services -n signoz ``` ## Access SigNoz Dashboard ### Port Forward (for testing) To quickly access the SigNoz dashboard for testing: ``` kubectl port-forward -n signoz svc/signoz 8080:8080 ``` Then open your browser and navigate to `http://localhost:8080` ### LoadBalancer (for production access) For production access, you may want to expose SigNoz through a LoadBalancer: ``` kubectl patch service signoz -n signoz -p '{"spec": {"type": "LoadBalancer"}}' ``` OR Use the helm values with helm upgrade ``` signoz: service: # signoz.service.type - The service type (`ClusterIP`, `NodePort`, `LoadBalancer`) type: LoadBalancer ``` ``` helm upgrade signoz signoz/signoz -n signoz -f values.yml ``` Get the external IP: ``` kubectl get service signoz-frontend -n signoz ``` ## Configure Data Sources ### Configure SigNoz OpenTelemetry Collector You need to configure your `signoz-otel-collector` as per your need. By default if you can use following urls to send signals to signoz-otel-collector from your cluster. For your applications to send data to SigNoz, configure them to send telemetry data to: - **Logs, Traces & Metrics**: `http://signoz-otel-collector.signoz.svc.cluster.local:4317` (gRPC) - **Logs, Traces & Metrics**: `http://signoz-otel-collector.signoz.svc.cluster.local:4318` (HTTP) ## Troubleshooting ### Check Pod Logs If any pods are not running, check their logs: ``` kubectl logs -n signoz ``` ### Check Resource Usage Monitor resource consumption: ``` kubectl top pods -n signoz kubectl top nodes ``` ### Verify Persistent Volumes Check if persistent volumes are bound correctly: ``` kubectl get pv kubectl get pvc -n signoz ``` ## Next Steps 1. **Configure Alerting**: Set up alert rules in the SigNoz dashboard 2. **Instrument Applications**: Add OpenTelemetry instrumentation to your applications 3. **Set Up Dashboards**: Create custom dashboards for your monitoring needs 4. **Configure Retention**: Adjust data retention policies based on your requirements ## Support For additional support and documentation: - [SigNoz Documentation](https://signoz.io/docs/) - [SigNoz GitHub Repository](https://github.com/SigNoz/signoz) - [DigitalOcean Kubernetes Documentation](https://docs.digitalocean.com/products/kubernetes/index.html.md) ## Cleanup To remove SigNoz from your cluster: ``` helm uninstall signoz -n signoz kubectl delete namespace signoz ```