Home
Available on AWS Marketplace
Community Edition

SigNoz Observability Platform

Amazon Linux 2023 | OpenTelemetry Native | ClickHouse Backend

Complete AMI guide for SigNoz observability platform. Monitor traces, metrics, and logs with OpenTelemetry-native instrumentation and powerful dashboards.

SigNoz v0.149.0 ClickHouse Backend Amazon Linux 2023

Quick Start Guide

Follow these steps to access your SigNoz observability platform and start monitoring.

1

SSH to Your Instance

Connect to your EC2 instance using SSH with your key pair.

ssh -i your-key.pem ec2-user@<your-instance-ip>
2

Find Your Credentials

View the auto-generated SigNoz admin credentials.

sudo cat /opt/signoz/credentials.txt
3

Access SigNoz UI

Open SigNoz in your browser using your instance's public IP on port 3301.

http://<your-instance-ip>:3301

Login with:
Email: (from credentials file)
Password: (from credentials file)

4

Verify Health Status

Check that SigNoz services are running properly.

# Check health endpoint curl http://localhost:3301/api/v1/health # Check all containers cd /opt/signoz/deploy && docker compose ps

Ports & Connection Details

SigNoz exposes several ports for the UI and telemetry ingestion.

SigNoz Web UI

  • URL: http://<your-ip>:3301
  • Port: 3301
  • Health Check: /api/v1/health

OpenTelemetry Endpoints

  • OTLP gRPC: Port 4317
  • OTLP HTTP: Port 4318
  • Protocol: OpenTelemetry (OTLP)

Required Security Group Rules

Port Protocol Purpose Source
3301 TCP SigNoz Web UI Your IP / VPN
4317 TCP OTLP gRPC (traces, metrics, logs) Application servers
4318 TCP OTLP HTTP (traces, metrics, logs) Application servers
22 TCP SSH Access Your IP

Sending Traces via OpenTelemetry

Configure your applications to send traces, metrics, and logs to SigNoz using OpenTelemetry.

1

OTLP gRPC Configuration

Configure your OpenTelemetry SDK to send data via gRPC (recommended for high throughput).

# Environment variables OTEL_EXPORTER_OTLP_ENDPOINT=http://<signoz-ip>:4317 OTEL_EXPORTER_OTLP_PROTOCOL=grpc
2

OTLP HTTP Configuration

Use HTTP/protobuf for environments where gRPC is not available.

# Environment variables OTEL_EXPORTER_OTLP_ENDPOINT=http://<signoz-ip>:4318 OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
3

Python Example

Instrument a Python application with OpenTelemetry.

# Install packages pip install opentelemetry-distro opentelemetry-exporter-otlp # Auto-instrument and run opentelemetry-instrument \ --traces_exporter otlp \ --metrics_exporter otlp \ --exporter_otlp_endpoint http://<signoz-ip>:4317 \ python app.py
4

Node.js Example

Instrument a Node.js application with OpenTelemetry.

# Install packages npm install @opentelemetry/auto-instrumentations-node # Run with auto-instrumentation OTEL_EXPORTER_OTLP_ENDPOINT=http://<signoz-ip>:4317 \ node --require @opentelemetry/auto-instrumentations-node/register app.js

OpenTelemetry Tips

  • Use gRPC (port 4317) for better performance and lower overhead.
  • Set OTEL_SERVICE_NAME to identify your service in SigNoz.
  • Add OTEL_RESOURCE_ATTRIBUTES for environment, version, and deployment info.
  • SigNoz supports traces, metrics, and logs - all via the same OTLP endpoint.

Creating Dashboards & Alerts

Build custom dashboards and set up alerts to monitor your applications.

1

Create a Dashboard

Build custom dashboards to visualize your metrics.

  • 1. Navigate to Dashboards in the sidebar
  • 2. Click + New Dashboard
  • 3. Add panels using the + Add Panel button
  • 4. Select visualization type (time series, table, etc.)
  • 5. Write your PromQL or ClickHouse query
  • 6. Click Save
2

Create an Alert

Set up alerts to notify you of issues.

  • 1. Go to Alerts in the sidebar
  • 2. Click + New Alert
  • 3. Define your alert condition
  • 4. Set threshold values and evaluation interval
  • 5. Configure notification channel (Slack, Email, PagerDuty)
  • 6. Click Create Alert
3

Explore Traces

Analyze distributed traces from your applications.

  • 1. Navigate to Traces in the sidebar
  • 2. Filter by service, operation, or duration
  • 3. Click on a trace to see the flame graph
  • 4. Identify slow spans and bottlenecks
  • 5. View span attributes and events
4

Analyze Logs

Search and analyze logs from your applications.

  • 1. Go to Logs in the sidebar
  • 2. Use the query builder to filter logs
  • 3. Search by service, severity, or message content
  • 4. Click on a log to see full details
  • 5. Correlate logs with traces using trace IDs

Common SigNoz Tasks

View Service Map

Navigate to Services to see your service dependency map and performance metrics.

Set Up Slack Alerts

Go to Settings → Alert Channels → Add Slack webhook URL.

Import Dashboard

Click Dashboards → Import → Paste JSON or upload file.

View Error Rates

Go to Services → Select service → View error rate and p99 latency.

Create Saved View

Filter traces/logs → Click Save View → Name your view for quick access.

Compare Deployments

Use time range selector to compare metrics before and after deployments.

Data Retention Configuration

Configure how long SigNoz retains your traces, metrics, and logs data.

Configure Retention via UI

Set retention periods for each data type in the SigNoz settings.

  • 1. Navigate to Settings → General
  • 2. Find Retention Settings section
  • 3. Set retention period for:
  • • Traces: Default 7 days
  • • Metrics: Default 30 days
  • • Logs: Default 15 days
  • 4. Click Save

Configure via Docker Compose

Modify retention settings in the Docker Compose configuration.

# Edit docker-compose.yaml cd /opt/signoz/deploy sudo nano docker/clickhouse-setup/docker-compose.yaml # Set retention in query-service environment: - SIGNOZ_TRACES_TTL=604800 # 7 days in seconds - SIGNOZ_METRICS_TTL=2592000 # 30 days in seconds

Storage Impact: Longer retention periods require more disk space. Monitor your ClickHouse storage usage and adjust retention accordingly. Consider using larger EBS volumes for production workloads.

ClickHouse Storage Management

Monitor and manage ClickHouse storage for optimal performance.

Check Storage Usage

Monitor ClickHouse disk usage and database sizes.

# Check disk usage df -h /var/lib/clickhouse # Check ClickHouse database sizes docker exec signoz-clickhouse clickhouse-client \ --query "SELECT database, formatReadableSize(sum(bytes_on_disk)) as size FROM system.parts GROUP BY database"

Optimize Tables

Run optimization to merge table parts and reclaim space.

# Optimize traces table docker exec signoz-clickhouse clickhouse-client \ --query "OPTIMIZE TABLE signoz_traces.signoz_index_v2 FINAL" # Optimize metrics table docker exec signoz-clickhouse clickhouse-client \ --query "OPTIMIZE TABLE signoz_metrics.samples_v4 FINAL"

Backup ClickHouse Data

Create backups of your observability data.

# Create EBS snapshot (recommended) # From AWS Console: EC2 → Volumes → Create Snapshot # Or backup specific tables docker exec signoz-clickhouse clickhouse-client \ --query "BACKUP DATABASE signoz_traces TO Disk('backups', 'traces_backup')"

ClickHouse Configuration

Key ClickHouse settings and file locations.

  • Data: /var/lib/clickhouse
  • Config: /etc/clickhouse-server
  • Logs: /var/log/clickhouse-server

Storage Recommendations

  • Use gp3 EBS volumes for best price/performance ratio.
  • Monitor disk usage and set up CloudWatch alarms at 80% capacity.
  • Enable EBS volume encryption for data at rest security.
  • Schedule regular EBS snapshots via AWS Backup for disaster recovery.

Troubleshooting

Common issues and how to resolve them.

Can't Access SigNoz UI

Symptom: Connection refused or timeout on port 3301.

Solution:

  • 1. Check Security Group allows inbound on port 3301
  • 2. Verify containers are running: cd /opt/signoz/deploy && docker compose ps
  • 3. Check frontend logs: docker compose logs frontend

Traces Not Appearing

Symptom: Instrumented apps but no traces in SigNoz.

Solution:

  • 1. Verify OTLP endpoint is correct (ports 4317/4318)
  • 2. Check Security Group allows ports 4317, 4318
  • 3. Check otel-collector logs: docker compose logs otel-collector
  • 4. Verify OTEL_SERVICE_NAME is set in your app

High Memory Usage

Symptom: ClickHouse consuming too much memory.

Solution:

  • 1. Check memory usage: docker stats
  • 2. Reduce retention period to lower storage/memory
  • 3. Consider upgrading to larger instance type
  • 4. Optimize tables: run OPTIMIZE TABLE commands

Service Restart

Symptom: Need to restart SigNoz services.

Solution:

cd /opt/signoz/deploy docker compose restart # Or restart specific service docker compose restart query-service

Instance Sizing Guide

Choose the right EC2 instance type for your observability workload.

Use Case Instance Type vCPUs RAM Recommended For
Development t3.medium 2 4 GB Testing, evaluation, small dev teams
Small Production t3.large 2 8 GB Small apps, <100 spans/sec
Medium Production m6i.xlarge 4 16 GB Multiple services, <1000 spans/sec
Large Production m6i.2xlarge 8 32 GB High traffic, <5000 spans/sec
High Performance r6i.2xlarge 8 64 GB Enterprise, high cardinality, long retention

Need Help?

Our team is available 24/7 to assist you with any questions or issues.

support@flowopsconsulting.co.uk
24/7 Support Available