mirror of
https://github.com/unpoller/unpoller.git
synced 2026-04-05 00:44:09 -04:00
6c5ff5482d
Add a per-controller `<namespace>_controller_up` Prometheus GaugeVec with a `source` label (controller URL or configured ID). The gauge is set to 1 after each successful poll and 0 on failure, giving operators a standard metric to alert on controller connectivity issues. Changes: - pkg/poller/config.go: add ControllerStatus type and ControllerStatuses field to Metrics so any output plugin can consume per-controller health. - pkg/poller/inputs.go: merge ControllerStatuses when AppendMetrics is called (multiple input sources). - pkg/inputunifi/interface.go: populate ControllerStatuses with Up=true on success and Up=false (while still continuing) on per-controller error. - pkg/promunifi/collector.go: declare and register a prometheus.GaugeVec `<namespace>_controller_up`; set the gauge for each controller status after every Collect cycle. Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
poller
UniFi Poller Core
This module ties the inputs together with the outputs.
Aggregates metrics on request. Provides CLI app and args parsing.
Ideal
This library has no notion of "UniFi" or controllers, or Influx, or Prometheus.
This library simply provides an input interface and an output interface.
Each interface uses an []any type, so any type of data can be used.
That is to say, you could write input and output plugins that work with, say,
Cisco gear, or any other network (or even non-network) data. The existing plugins
should provide ample example of how to use this library, but at some point the
godoc will improve.
Features
- Automatically unmarshal's plugin config structs from config file and/or env variables.
- Initializes all "imported" plugins on startup.
- Provides input plugins a Logger, requires an interface for Metrics and Events retrieval.
- Provides Output plugins an interface to retrieve Metrics and Events, and a Logger.
- Provides automatic aggregation of Metrics and Events from multiple sources.