Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor additional devices in bare metal environments #95

Open
serveric opened this issue Jun 18, 2021 · 2 comments
Open

Monitor additional devices in bare metal environments #95

serveric opened this issue Jun 18, 2021 · 2 comments

Comments

@serveric
Copy link

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.

@serveric
Copy link
Author

serveric commented Jun 18, 2021

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.

@JohnGarbutt
Copy link
Contributor

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.

@itrich itrich transferred this issue from another repository Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants