Sabnzbd_exporter

A Prometheus metrics exporter that collects and exposes download statistics from SABnzbd Usenet downloader instances.

  • Monitoring & Logging
  • Tools & Utilities
A Prometheus metrics exporter that collects and exposes download statistics from SABnzbd Usenet downloader instances.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • 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.

44/100 Fair

Maintained
35last commit 378 days ago
Popular
3342 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

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

GitHub stars
42
Open issues
5
Last commit
2025-11-07
Latest release
0.1.80
License
MIT
Activity
stale

Checked 20 days ago - source: GitHub (msroest/sabnzbd_exporter)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Save your settings in /config Start with a named volume (Docker's managed storage folder) attached to /config. This keeps SABnzbd's settings and account data safe instead of losing them when the container is removed or rebuilt. source
  • Open port 8080 for the web page Run the container with -p 8080:8080 so the app's web interface is exposed on port 8080. Without this port mapping, your computer or phone cannot reach the SABnzbd login page. source
  • Point downloads to folders on your PC/NAS Map /downloads and /incomplete-downloads to folders on your PC or NAS where you want files saved. SABnzbd writes finished and partial downloads there, so without these folders the files may stay hidden inside the container and be lost. source
  • Required Environment Variables Set SABNZBD_BASEURLS (comma-separated SABnzbd server URLs) and SABNZBD_APIKEYS (comma-separated API keys, positionally matched to each server) as environment variables. source

Fetched 44 days ago - each note links to its source

Alternatives (4)

  • GrabIt - GrabIt is a free application that enables you to easily find and download content from Usenet news servers.
  • JDownloader - JDownloader is a self-hosted JDownloader 2 download manager that runs in a pre-configured dark-mode Selkies web desktop with automatic firs…
  • NZBGet - NZBGet is a lightweight C++ Usenet downloader that fetches NZB files at maximum speed while using minimal system resources, making it well…
  • SABnzbd - Sabnzbd is a Usenet downloader that automatically downloads, verifies, repairs, extracts, and organizes .nzb files for homelab users who wa…

Checked 41 days ago - source: AlternativeTo

Common questions

Which API key should sabnzbd_exporter use to talk to SABnzbd?

Use the API key from SABnzbd's Config -> General, because an incorrect API key is the documented issue for third-party programs.

Why might the exporter not be able to reach my SABnzbd instance?

One documented fix is to edit the host field in sabnzbd.ini to 0.0.0.0 so SABnzbd can be reached from outside its local interface.

What port mapping is needed for the SABnzbd web interface in a Docker deployment?

Map port 8080, for example with -p 8080:8080, so the SABnzbd web interface can be reached.

Where should SABnzbd store its configuration in Docker so it survives container removal?

Attach a named volume to /config so SABnzbd settings and account data persist instead of being lost when the container is removed or rebuilt.

Answers sourced from github.com, github.com, sabnzbd.org

Community

Collected 48 days ago - public community threads