SQL Exporter
SQL Exporter is a thin SQL client for Prometheus, allowing querying and browsing of any JDBC-compliant database.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- 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.
71/100 Good
- Maintained
- 100last commit 19 days ago
- Popular
- 56605 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 80no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 5.8/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 605
- Open issues
- 2
- Last commit
- 2026-11-02
- Latest release
- 0.24.13
- License
- MIT
- Activity
- rising
Checked 15 days ago - source: GitHub (burningalchemist/sql_exporter)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Check datasource access on port 9200 Before starting, confirm you can reach the OpenSearch datasource endpoint on port 9200 and include your username and password. If the port is blocked or authentication is missing, the app cannot read that datasource and queries will fail. source
- Use the exact datasource name When testing the endpoint, replace my_prometheus with the exact datasource name you created. A typo or missing name causes a not-found error, even if OpenSearch itself is working. source
- Configure your queries in a YAML file Create a YAML configuration file defining the SQL queries and metric mappings for your target database, then pass that file to the exporter at startup. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can sql_exporter connect to SQL Server and expose built-in metrics?
Yes, one user reported a successful connection and being able to read all built-in metrics.
Is sql_exporter configuration driven?
Yes, the repository describes it as a configuration driven SQL exporter.
Where can users ask questions about sql_exporter?
GitHub Discussions is described as a forum for discussing code, asking questions, and collaborating with the developer community.
Answers sourced from github.com, github.com, stackoverflow.com
Community
Collected 48 days ago - public community threads