SigNoz-AIO

SigNoz is a self-hosted, open-source observability platform for traces, metrics, and logs.

  • Network Services
  • Tools & Utilities
SigNoz is a self-hosted, open-source observability platform for traces, metrics, and logs. This Unraid AIO (All-In-One) template packages the official SigNoz Docker stack—SigNoz, its OpenTelemetry collector, ClickHouse, and ZooKeeper—into a single container with sensible defaults, so you don't need to translate the upstream multi-container compose file yourself.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

43/100 Fair

Maintained
69last commit 156 days ago
Popular
144 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 31 days ago

GitHub stars
4
Open issues
3
Last commit
2026-06-18
Latest release
v0.129.0-aio.1
Activity
stale

Checked 9 days ago - source: GitHub (JSONbored/signoz-aio)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set free ports for the OpenTelemetry demo Before starting the OpenTelemetry demo with docker compose (a command that starts the demo's containers), edit its .env file (a text file the app reads for settings) and set ENVOY_PORT and PROMETHEUS_PORT (the network ports the demo uses) to ports that are free on your machine. If you use ports that are already taken, the demo can fail to start or interfere with other services. source
  • Point your OpenTelemetry senders at the OTLP ports Once the container is running, configure your applications' OpenTelemetry senders to target the published OTLP ports so traces, metrics, and logs are ingested by SigNoz. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which OTLP ports should OpenTelemetry senders point to in signoz-aio?

The built-in SigNoz OTel collector receives OTLP data on ports 4317 and 4318.

Can I collect telemetry from other hosts without mounting Docker socket or host logs into the main SigNoz container?

Yes, the signoz-agent template can collect telemetry from remote machines and forward it to signoz-aio. It defaults to no host root, Docker socket, or Docker log mounts.

Does using external PostgreSQL remove the need for ClickHouse in the AIO advanced settings?

No, PostgreSQL can replace SQLite for SigNoz metadata only. Traces, metrics, and logs still require ClickHouse.

Where does the AIO store SigNoz application metadata?

SigNoz application and configuration metadata is stored in an internal SQLite database persisted under /appdata/signoz.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads