Semaphore-exporter
Prometheus exporter for Semaphore (semaphoreui.com), which has no native /metrics endpoint.
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.
36/100 Low
- Maintained
- 69last commit 65 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 1016 GB minimum RAM
Availability: platform listings confirmed today, links checked 24 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-09-17
- Activity
- stale
Checked 8 days ago - source: GitHub (louij2/semaphore-exporter)
Resources & Compatibility
Minimum requirements: 16 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Run the setup wizard before starting Run the interactive setup wizard, such as `semaphore setup`, to enter your database connection, playbook paths, and first login. Without it, Semaphore does not know where to save settings or where to find your automation playbooks (the task scripts it runs), so the app will not work correctly. source
- Start a supported database first Start one supported database program, such as MySQL, MariaDB, or PostgreSQL, before running Semaphore. This is where Semaphore stores projects, tasks, inventory, and credentials, so if it is missing or unreachable, your data cannot be saved. source
- Fill in login keys before starting containers If you use the optional directory-login (LDAP/Authentik) example, generate and save the required .env file values before running the docker-compose command that starts the container stack. Missing keys or blank secrets can stop login from working after the stack starts. source
- Configuration Set the SEMAPHORE_URL env var to your Semaphore base URL; metrics are served on port 9825. source
- Running the exporter Set SEMAPHORE_URL to your Semaphore instance URL (and SEMAPHORE_API_TOKEN if authentication is required). Prometheus scrapes the exporter on port 9825. Stdlib-only Python, no third-party dependencies. source
Fetched 16 days ago - each note links to its source
Variants
Alternatives (4)
- Azure DevOps - Continuous Delivery Services for teams to share code, track work, and ship software – for any language, all in a single package.
- GitLab - GitLab is a self-hosted Git repository server and software delivery platform for individuals and teams to privately plan, version, build, t…
- Jenkins - Jenkins is a fork of Hudson and is a continuous build system for software projects.
- semaphore - Semaphore is a modern web interface for managing DevOps tools such as Ansible, Terraform, OpenTofu, and PowerShell.
Checked 40 days ago - source: AlternativeTo
Common questions
Can the exporter start, stop, or modify Semaphore tasks?
No. It is read-only and only performs GET requests against Semaphore's API, never changing a task or template.
Which endpoint and port should Prometheus scrape?
Run the Docker container with port 9825 mapped and scrape /metrics on that port, for example :9825/metrics.
What environment variables must be set when starting the container?
Set SEMAPHORE_URL to the Semaphore base URL and SEMAPHORE_API_TOKEN to the API token used for API access.
Which metric helps identify tasks stuck in running state?
It exports semaphore_task_running_seconds for every non-terminal task, so a task stuck running for hours is visible in Prometheus.
Does frequent Prometheus scraping hammer Semaphore's API?
The exporter polls Semaphore's REST API and caches the results briefly so a scrape storm cannot hammer it.
Answers sourced from github.com
Community
- Log In - Semaphore (other)
- Ansible Semaphore - Reddit (reddit)
- Semaphore Community Hub - Progress.com (other)
- Welcome to the Semaphore Forum! - Progress Community (other)
- What's your set up and what do you host? : r/selfhosted - Reddit (reddit)
Collected 47 days ago - public community threads