MetricsHub
MetricsHub Community Connectors 1.0.22
-
Home
- Connector Developer Guide Sources 19
ipmi (Source)
When To Use
Use ipmi when metrics are exposed through IPMI sensor outputs and your target platform supports IPMI collection.
This source usually feeds AWK/compute normalization steps before mapping.
Syntax
sources:
sensorDump:
type: ipmi
forceSerialization: true
computes:
- type: awk
script: ${file::sdr_formatter.awk}
Properties
| Property | Required | Default | Description |
|---|---|---|---|
type |
Yes | None | ipmi. |
computes |
No | [] |
Post-processing pipeline, typically required for shaping. |
forceSerialization |
No | false |
Serialize execution via a per-connector, per-host lock (see the Sources overview). Default false. |
executeForEachEntryOf |
No | None | Fan-out context when needed. |
Recommended Pattern
- Parse IPMI command output into semicolon-delimited tables quickly.
- Branch with
copyfor multiple monitor views (status, thresholds, counters). - Keep translation logic in reusable translation tables.
Common Mistakes
- Mapping raw IPMI output without normalization.
- Mixing discrete and numeric sensors in one unstable table shape.
- Running redundant IPMI calls instead of reusing one source table.
Community Examples
- IpmiTool[1]
- LinuxIpmiTool[2]
- WindowsIpmiTool[3]
ipmi source
sensors
hardware monitoring
metricshub
community
connector
hardware
system
Links:
- [1] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/IpmiTool/IpmiTool.yaml
- [2] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/LinuxIpmiTool/LinuxIpmiTool.yaml
- [3] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/WindowsIpmiTool/WindowsIpmiTool.yaml
Search Results for {{siteSearch | truncate:'50'}}
{{resultArray.length}}
Searching...
No results.
