SigNoz vs Datadog: Open-Source APM Comparison and Complete Installation Guide on a $5 VPS

Observability is no longer a "nice-to-have" for modern applications. Whether you are running a small side project or a scaling startup, knowing why a request is slow or where a memory leak is occurring is the difference between a 5-minute fix and a 5-hour outage.

For years, Datadog has been the gold standard for Application Performance Monitoring (APM). However, as your infrastructure grows, Datadog's pricing can become unpredictable and overwhelming. This has led many developers and sysadmins to look for open-source alternatives.

Enter SigNoz.

SigNoz is an open-source observability platform that provides metrics, traces, and logs in a single UI. It is built on OpenTelemetry, meaning it avoids vendor lock-in. In this guide, we will compare SigNoz with Datadog and walk through a practical installation on a low-cost VPS.

SigNoz vs Datadog: The Breakdown#

When choosing between a managed SaaS like Datadog and a self-hosted tool like SigNoz, the decision usually boils down to Budget vs. Convenience.

Feature Comparison#

The Pros and Cons#

Datadog

Pros:

• Zero infrastructure management.
• Extremely polished UI and deep integrations.
• Massive ecosystem of pre-built dashboards.

Cons:

• Cost can spiral quickly with "custom metrics."
• Proprietary agents make it harder to migrate away.
• Data is stored on their servers (privacy concerns for some).

SigNoz

Pros:

• Complete control over your data.
• No "per-host" pricing when self-hosting.
• Built on OpenTelemetry, the industry standard for observability.
• Unified view of logs, metrics, and traces.

Cons:

• You are responsible for backups and updates.
• Requires a server with decent RAM to run ClickHouse efficiently.
• Fewer "out-of-the-box" integrations than Datadog.

Who Should Use SigNoz?#

SigNoz is an excellent choice for:

• Technical Founders: Who need professional monitoring without the enterprise price tag.
• DevOps Engineers: Who prefer OpenTelemetry and want to avoid vendor lock-in.
• Privacy-Conscious Teams: Who cannot send their application traces and logs to a third-party SaaS.
• Self-Hoster Enthusiasts: Who enjoy managing their own stack via Docker.

When NOT to Use SigNoz?#

Avoid self-hosting SigNoz if:

• You have zero experience with Docker or Linux administration.
• Your team is too small to handle the overhead of maintaining a monitoring database (ClickHouse).
• You need a "plug-and-play" solution and have a large budget to throw at a SaaS.

Installing SigNoz on a $5 VPS#

Running a full APM suite on a $5 VPS (typically 1GB or 2GB RAM) is challenging because SigNoz relies on ClickHouse, which is powerful but memory-hungry. To make this work, we must optimize the OS and use a swap file.

Prerequisites#

• A VPS running Ubuntu 22.04 LTS.
• At least 2GB of RAM is recommended, but we will use a swap file for 1GB instances.
• Docker and Docker Compose installed.

Step 1: System Optimization (The "Budget" Setup)#

Before installing SigNoz, we need to ensure the server doesn't crash due to Out-Of-Memory (OOM) errors.

Create a Swap File:

sudo fallocate -l 4G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
# Make it permanent
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

Step 2: Installing SigNoz via Docker Compose#

SigNoz provides a convenient installation script that handles the Docker Compose setup for you.

Run the installer:

git clone https://github.com/SigNoz/signoz.git
cd signoz/deploy/docker
./install.sh

During the installation, the script will ask you for a few configurations. For a $5 VPS, keep the defaults but ensure you have enough disk space (at least 20GB).

Step 3: Accessing the Dashboard#

Once the containers are up and running, SigNoz will be available at: http://<your-vps-ip>:3301

You will be prompted to create an admin account on the first visit.

Step 4: Instrumenting Your Application#

The magic of SigNoz is that it doesn't use a proprietary agent for everything; it uses OpenTelemetry (OTel).

To send data from your app (e.g., a Node.js or Python app) to SigNoz:

1. Install the OpenTelemetry SDK in your app.
2. Point the OTLP exporter to your VPS IP on port 4317 (gRPC) or 4318 (HTTP).

Example (Node.js):

const { NodeSDK } = require('@opentelemetry/sdk-node');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-grpc');

const sdk = new NodeSDK({
  traceExporter: new OTLPTraceExporter({
    url: 'http://<your-vps-ip>:4317',
  }),
});

sdk.start();

Step 5: Configuring Logs, Metrics, and Alerts#

Once your data is flowing, navigate through the SigNoz UI:

1. Traces: Look for "Service Maps" to see how your microservices interact and identify which endpoint is causing latency.
2. Metrics: Create custom dashboards by querying the metrics collected by the OTel collector.
3. Logs: Use the "Logs" tab to filter through application errors. Since logs are linked to traces, you can click a log entry and jump directly to the trace that produced it.
4. Alerts: Go to the "Alerts" section and set up a threshold (e.g., "Alert me if 5xx errors exceed 5% over 5 minutes"). You can integrate this with Slack or PagerDuty.

Practical Maintenance Checklist#

Running a self-hosted monitoring tool requires a bit of discipline. Follow this checklist to keep your $5 VPS healthy:

• Monitor Disk Space: ClickHouse stores a lot of data. Set up a cron job or a script to monitor disk usage.
• Check RAM Usage: Run htop occasionally to see if the swap is being heavily used.
• Backup ClickHouse: Periodically back up your data volumes located in /root/signoz/data.
• Update Containers: Periodically run docker compose pull and docker compose up -d to get the latest SigNoz features.
• Firewall Setup: Ensure port 3301 (UI) is protected or restricted to your IP via ufw.

FAQ#

Q1: Can SigNoz really run on a $5 VPS? Yes, but it is tight. With a 4GB swap file and a lightweight application, it works. However, for production environments with high traffic, you will need at least 4GB-8GB of actual RAM.

Q2: Does SigNoz support all languages? Since it uses OpenTelemetry, it supports almost every major language, including Java, Python, Go, Node.js, and .NET.

Q3: How is SigNoz different from Prometheus/Grafana? Prometheus is primarily for metrics. Grafana is for visualization. SigNoz combines metrics, traces, and logs into one unified tool, eliminating the need to jump between three different dashboards to debug one issue.

Q4: Is my data safe in SigNoz? Since you are self-hosting, the data stays on your server. You have full control over encryption and access.

Q5: What happens if the VPS crashes? If the VPS crashes, you lose your monitoring. This is the trade-off of self-hosting. For critical production apps, consider the SigNoz Cloud version or a high-availability Kubernetes deployment.

Conclusion#

Switching from a commercial tool like Datadog to an open-source alternative like SigNoz is a strategic move for teams who want to reclaim control over their data and their budget. While Datadog offers unparalleled convenience, SigNoz provides a powerful, OTel-native alternative that can be run even on a modest budget.

If you are looking for more guides on self-hosting and DevOps optimizations, feel free to explore the tutorials at mahbuburriad.com. Happy monitoring!