apcupsd-influxdb-exporter
Dockerized Python script that queries UPS status from apcupsd and exports the metrics to InfluxDB for time-series monitoring.
Platform availability
Available on 1 of 9 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)
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.
15/100 Low
- Maintained
- 0last commit 2304 days ago
- Popular
- 2211 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 13 days ago
- GitHub stars
- 11
- Open issues
- 0
- Last commit
- 2020-06-23
- Activity
- stale
Checked 7 days ago - source: GitHub (atribe/apcupsd-influxdb-exporter)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 17 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start the apcupsd background program After installing apcupsd, run its starter script to start the daemon, for example /etc/rc.d/init.d/apcupsd start on Red Hat. If this background program is not running, the exporter has no UPS status to read or send. source
- Confirm startup in the log After starting it, run tail /var/log/messages and look for a line saying apcupsd startup succeeded. That confirms the UPS monitoring program is alive before you rely on the exporter. source
- Keep your apcupsd settings safe The sample starter script expects configuration files under /etc/apcupsd, with each UPS instance using its own apcupsd.*.conf file. Back up that directory and change it carefully, because bad settings can stop the daemon from seeing your UPS. source
Fetched 8 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I check when the Docker container asks for APCUPSD_HOST on UnRAID?
Check the host or service where APCUPSd is configured. The UnRAID user had an APC UPS working in UnRAID but could not find where APCUPSd was configured.
Does the exporter require an InfluxDB database?
Yes. The Docker-based APCUPSd daemon sends UPS-device information to InfluxDB.
Is there vendor guidance for using apcupsd with an SMC1500I?
A Schneider Electric community thread marked solved covers using apcupsd with an SMC1500I. The available snippet does not provide the specific configuration details or fix.
Does the Docker image include the APCUPSd tool?
The image is built to output UPS statistics using an included version of the APCUPSd tool.
Answers sourced from community.se.com, github.com, github.com, www.reddit.com
Community
- Help with APCUPSD Exporter i saw on here a while back - Reddit (reddit)
- apcupsd-influxdb-exporter APCUPSD HOST? : r/unRAID - Reddit (reddit)
- [Support] APCUPSD to InfluxDB 2.x - Docker Containers - Unraid (forum)
- Solved: apcupsd and SMC1500I - Schneider Electric Community (other)
- Problems with APC configuration via apcupsd - The FreeBSD Forums (forum)
Collected 16 days ago - public community threads