If your team is moving beyond basic uptime checks, self-hosted SigNoz with Docker is a good next step because it brings traces, metrics, and logs into one platform.
In this guide, self-hosted SigNoz with Docker runs on one dedicated server, while OpenTelemetry sends telemetry from your apps into SigNoz. This guide follows the current SigNoz Docker install method, which uses Foundry for Docker-based deployments.
For a stable production setup, it's better to run SigNoz on a powerful dedicated server instead of a very small VPS.
What This Self-Hosted SigNoz with Docker Setup Includes
The current Docker standalone deployment includes SigNoz, a SigNoz OpenTelemetry Collector, ClickHouse, ClickHouse Keeper, and PostgreSQL. In simple terms, the web app provides the UI, the collector receives telemetry, ClickHouse stores high-volume observability data, and PostgreSQL stores platform metadata.
Main parts include:
SigNoz UI: the dashboard where you search traces, inspect logs, and view metrics.
OpenTelemetry Collector: the pipeline that receives, processes, and forwards telemetry data.
ClickHouse: the main data store for telemetry such as traces, logs, and metrics in the default single-node setup.
Traces: show the full path of one request through your app.
Metrics: show numbers over time, such as request rate, latency, memory use, and errors.
Logs: show event messages that help with debugging.
Server Requirements for Self-Hosting SigNoz
Before you install anything, you need a Linux host, Docker Engine, Docker Compose, at least 4 GB of memory, and open ports 8080, 4317, and 4318.
Suggested starting sizes include:
Use Case
CPU
RAM
Storage
Demo or Lab
4 vCPU
8 GB
100 GB NVMe
Small Production
8 vCPU
16 GB
250 GB NVMe
Growing Production
12 to 16 vCPU
32 GB or more
500 GB or more NVMe
As traffic grows, self-hosted SigNoz with Docker will write a lot of telemetry data, so SSD or NVMe storage is the right choice for a dedicated server. If your stack also includes heavier data or model workloads, you can plan that side separately with AI hosting architecture.
Prepare Your Server for SigNoz Setup
In this guide, we use Ubuntu 24.04. You must start on a fresh Ubuntu server, update your packages, and install the required tools:
The SigNoz Docker guide requires Docker Engine 20.10 or newer plus the Docker Compose v2 plugin. To install it, you can use the commands below to add the repository:
Note: For safety, self-hosted SigNoz with Docker should expose the web UI carefully and keep OTLP ports private unless remote apps really need public access.
Install SigNoz with Foundry
The current supported way to deploy self-hosted SigNoz with Docker uses Foundry, and the older install.sh with the old deploy/ bundle are deprecated.
The cast workflow validates the host, generates the Docker Compose deployment in pours/deployment/, and starts the containers.
Verify the SigNoz Deployment
After deployment, the self-hosted SigNoz with Docker should listen on port 8080, while OTLP ingestion is available on port 4317 for gRPC and 4318 for HTTP.
Check the running containers:
Bash
dockerps
Check the listening ports:
Bash
sudoss-tulpn|grep-E'8080|4317|4318'
Now you can access the SigNoz UI in a browser and create your account:
For a public-facing setup, it is better to place the SigNoz UI behind Nginx and add SSL. Let’s Encrypt HTTP-01 validation needs public access to port 80 during certificate checks.
Note: If Certbot fails with a timeout, first check DNS, firewall rules, and whether port 80 is reachable from the public internet.
Now you can access your SigNoz UI from:
Bash
https://signoz.example.com
Understand SigNoz Ingestion Endpoints and Collector
Self-hosted SigNoz accepts OTLP over gRPC on port 4317 and OTLP over HTTP on port 4318. With OTLP/HTTP, most SDKs automatically append paths such as /v1/traces, /v1/metrics, and /v1/logs to the endpoint.
SigNoz recommends using the OpenTelemetry Collector because it can receive data from many sources, batch it, enrich it, retry on failure, and give you a central place to shape telemetry before it reaches SigNoz.
In production, self-hosted SigNoz with Docker works better when you place an OpenTelemetry Collector between your apps and SigNoz.
This is helpful when you want to:
Drop noisy spans or logs before storage.
Add labels such as environment or team.
Retry and queue data when the backend is busy.
Keep app instrumentation simple while doing most routing in one place.
Send Your First Trace from Python
A first trace is the fastest way to confirm that self-hosted SigNoz with Docker is receiving data correctly.
First, install the Python tools:
Bash
sudoaptinstallpython3python3-pippython3-venv-y
Create a demo app folder, virtual environment, and activate it:
Note: Replace YOUR_SERVER_IP with the real IP or hostname of your SigNoz server. If the demo app runs on the same server, you can use http://localhost:4317 instead.
Run the app:
Bash
python3app.py
Then open the SigNoz UI and look for the service name demo-python-app.
Use Your Own Collector (Optional)
If you want more control, self-hosted SigNoz with Docker can sit behind your own OpenTelemetry Collector gateway. In this model, your apps send data to your collector first, and that collector forwards data to SigNoz.
Note: On the same server, self-hosted SigNoz with Docker already uses ports 4317 and 4318, so a second collector should listen on different host ports, such as 14317 and 14318.
Start the custom collector:
Bash
dockercomposeup-ddockerps
Check the health endpoint:
Bash
curlhttp://127.0.0.1:13133/health
Now point your apps to the custom collector instead of SigNoz directly:
Once it is running, self-hosted SigNoz with Docker gives small teams a clear path from basic monitoring to real observability. You get traces, metrics, and logs in one place, and you can grow from direct app export to a more controlled collector-based setup when your stack becomes more important.
For heavier workloads, self-hosted SigNoz with Docker is better on a PerLod dedicated server with enough CPU, RAM, and fast local storage.
We use cookies to run PerLod and to understand how the site is used. You can accept everything, or open Manage to turn individual categories off. Cookie policy.