Ubuntu 24.04 LTS | OpenTelemetry Native | ClickHouse Backend
Complete AMI guide for SigNoz observability platform. Monitor traces, metrics, and logs with OpenTelemetry-native instrumentation and powerful dashboards.
Follow these steps to access your SigNoz observability platform and start monitoring.
Connect to your EC2 instance using SSH with your key pair.
ssh -i your-key.pem ubuntu@<your-instance-ip>
View the auto-generated SigNoz admin credentials.
sudo cat /opt/signoz/credentials.txt
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)
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
SigNoz exposes several ports for the UI and telemetry ingestion.
| 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 |
Configure your applications to send traces, metrics, and logs to SigNoz using OpenTelemetry.
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
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
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
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
Build custom dashboards and set up alerts to monitor your applications.
Build custom dashboards to visualize your metrics.
Set up alerts to notify you of issues.
Analyze distributed traces from your applications.
Search and analyze logs from your applications.
Navigate to Services to see your service dependency map and performance metrics.
Go to Settings → Alert Channels → Add Slack webhook URL.
Click Dashboards → Import → Paste JSON or upload file.
Go to Services → Select service → View error rate and p99 latency.
Filter traces/logs → Click Save View → Name your view for quick access.
Use time range selector to compare metrics before and after deployments.
Configure how long SigNoz retains your traces, metrics, and logs data.
Set retention periods for each data type in the SigNoz settings.
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.
Monitor and manage ClickHouse storage for optimal performance.
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"
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"
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')"
Key ClickHouse settings and file locations.
Common issues and how to resolve them.
Symptom: Connection refused or timeout on port 3301.
Solution:
3301cd /opt/signoz/deploy && docker compose psdocker compose logs frontendSymptom: Instrumented apps but no traces in SigNoz.
Solution:
docker compose logs otel-collectorSymptom: ClickHouse consuming too much memory.
Solution:
docker statsSymptom: Need to restart SigNoz services.
Solution:
cd /opt/signoz/deploy
docker compose restart
# Or restart specific service
docker compose restart query-service
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 |
Our team is available 24/7 to assist you with any questions or issues.
support@flowopsconsulting.co.uk