You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Cloud Operator, I want to be able to get metrics from external devices in my data center. This includes PDUs, UPSs and sensors (temperature, humidity, leakage, ...).
That means the monitoring architecture needs support for scraping such devices via SNMP or Modbus exporters (in case the monitoring is realized by Prometheus).
Different devices and sensors need specific exporter configurations which usually differ from data center to data center.
The monitoring somehow (= by providing ip address and type of the device) has to be aware of such devices to apply the correct device-specific exporter configuration and eventually scrape the targets.
Alternatively, the monitoring arch. must be able to get extended for supporting additional targets.
For instance by allowing to inject additional targets into configuration files of the monitoring architecture.
The text was updated successfully, but these errors were encountered:
Since this description is generic, it depends on the exact device to determine to which category the usecase belongs.
But I guess Prio 3 = certain Prio 1 situation is upcoming, need fast action to avoid could fit.
I have found a redfish exporters quite useful for servers, node exporter works for some switches and as you say, supporting SNMP is good call out for other metrics, such as power metrics from PDUs.
it is worth calling out the need to be able to correlate between physical and logical mappings here, like what PDU each hypervisor is attached to, etc, so you understand the meaning as you move between the layers.
As a Cloud Operator, I want to be able to get metrics from external devices in my data center. This includes PDUs, UPSs and sensors (temperature, humidity, leakage, ...).
That means the monitoring architecture needs support for scraping such devices via SNMP or Modbus exporters (in case the monitoring is realized by Prometheus).
Different devices and sensors need specific exporter configurations which usually differ from data center to data center.
The monitoring somehow (= by providing ip address and type of the device) has to be aware of such devices to apply the correct device-specific exporter configuration and eventually scrape the targets.
Alternatively, the monitoring arch. must be able to get extended for supporting additional targets.
For instance by allowing to inject additional targets into configuration files of the monitoring architecture.
The text was updated successfully, but these errors were encountered: