1.0 SigNoz - Overview

SigNoz is a fully open-source observability platform built on OpenTelemetry and ClickHouse. It provides Application Performance Monitoring (APM), distributed tracing, infrastructure metrics, and log management in a single unified interface — the self-hosted open-source alternative to Datadog and New Relic.

Key features of SigNoz include:

  • Distributed Tracing: End-to-end request tracing across microservices with flame graphs and service maps.
  • Metrics Monitoring: Infrastructure and application metrics with customisable dashboards and PromQL-style queries.
  • Log Management: Centralised log ingestion with full-text search and correlation with traces and metrics.
  • Alerts: Threshold and anomaly-based alerting with Slack, PagerDuty, and email notification channels.
  • Service Performance Maps: Automatic visualisation of inter-service dependencies and golden signals (latency, errors, throughput).
  • Exceptions Tracking: Automatic exception grouping with stack traces linked to the relevant trace.
  • OpenTelemetry Native: First-class support for all OTel SDKs — Java, Python, Go, Node.js, .NET, Ruby, and more.

You can find more details at https://signoz.io/

1.1 Prerequisites

The minimal requirements for deploying SigNoz are as follows:

  • At least 4 CPU cores
  • At least 8 GB of Memory
  • At least 30 GB of free disk space (SSD recommended)

For optimal performance in Azure, we recommend selecting the following VM sizes:

- Standard D-Series v4 & v5: D4as_v4, D8as_v4, D4as_v5 and D8as_v5

NOTE: Requirements scale with the volume of traces, metrics, and logs ingested. For production workloads or teams larger than ~10 developers, consider using at least 8 cores / 16 GB RAM and attaching a dedicated data disk of 200 GB or more. For more information, see how to attach a data disk to a Linux VM.

2.0 Deploying SigNoz

Now let's begin with the deployment process!

The first step is to create a new Virtual Machine using our Marketplace solution. Log in to the Azure Marketplace

Check the plan details and click "CREATE"

Select a name for your Virtual Machine, choose the appropriate size, configure networking, disk options, etc.


Review your configuration and create the Virtual Machine. The creation process will take a few minutes.

That's it! Once your VM is ready, all SigNoz components start automatically. You can also connect via SSH if needed. For more information, see How to use SSH with Linux on Azure.

$ssh username@yourvmIP

2.1 First Access

Once your VM is ready, open your browser and navigate to:

http://yourvmIP:8080

You will be prompted to create your admin account on first login. Fill in your name, email, and a strong password, then click "Get Started".

NOTE: SigNoz has no default credentials — you create them on first launch. Complete the setup wizard before exposing the VM to the internet to ensure no other user can claim the admin role.

After signing in you will land on the Services dashboard. It will be empty until you instrument your applications and start sending telemetry to the collector.

To send telemetry from your applications, configure your OpenTelemetry SDK or agent to use one of the following endpoints:

  • OTLP gRPC: http://yourvmIP:4317
  • OTLP HTTP: http://yourvmIP:4318

For language-specific instrumentation guides, see the official SigNoz instrumentation documentation.

2.2 Securing SigNoz

For production deployments, we recommend the following security measures:

1. Complete the account setup immediately

On first access, finish the setup wizard before the VM is reachable from the internet. This ensures no other user can claim the admin role.

2. Configure HTTPS

For production environments, we recommend setting up a reverse proxy with HTTPS using Nginx and Let's Encrypt:

sudo apt install -y nginx certbot python3-certbot-nginx

Create a server block for SigNoz (replace signoz.yourdomain.com with your domain):

server {
    server_name signoz.yourdomain.com;
    location / {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
    }
}
sudo ln -s /etc/nginx/sites-available/signoz /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl reload nginx
sudo certbot --nginx -d signoz.yourdomain.com

3. Restrict firewall access

Review your UFW rules and limit access to the SigNoz UI and collector ports to only trusted IP ranges:

# Allow SigNoz UI only from your network
sudo ufw allow from <your-ip-range> to any port 8080

# Allow OTLP only from your application subnet
sudo ufw allow from <app-subnet> to any port 4317
sudo ufw allow from <app-subnet> to any port 4318

sudo ufw reload

4. Invite team members — avoid sharing credentials

SigNoz supports multi-user accounts. Invite additional users via Settings → Organisation Settings → Invite Members in the web UI. Each team member authenticates individually — no shared passwords needed.

For more information on securing your SigNoz installation, please refer to the official SigNoz documentation.