2dec2d7d25
Adds docker-compose-remote.yml and matching env example for running unifi-poller against the UniFi cloud API instead of a local controller. Uses UP_UNIFI_REMOTE and UP_UNIFI_REMOTE_API_KEY for auto-discovery of all Network-capable consoles via api.ui.com. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| docker-compose-remote.env.example | ||
| docker-compose-remote.yml | ||
| docker-compose.env.example | ||
| docker-compose.yml | ||
README.md
Docker Compose
The files in this folder can be used locally to spin up a full set of applications (minus the UniFi controller) to get UniFi Poller up and running. Including InfluxDB, Grafana, and Chronograph. This last app is useful to inspect the data stored in InfluxDB by UniFi Poller.
HOWTO
Learn more about how and when to use these Docker Compose files in the Docker Wiki.
Health Check
The UniFi Poller Docker image includes a built-in health check that validates the configuration and checks plugin connectivity. The health check runs every 30 seconds and marks the container as unhealthy if configuration issues are detected or if enabled outputs cannot be reached.
You can manually run the health check:
docker exec <container_name> /usr/bin/unpoller --health
The health check is automatically used by Docker and container orchestration platforms (Kubernetes, Docker Swarm, etc.) to determine container health status.