banshee/hardware-collection/hardware/redfish/https/power

Power supplies of a server, by Redfish

Returns, for each power supply a server's management card serves by Redfish, and for each redundancy group of its supplies, its health; and the power each chassis draws, in watts. Three watches are offered, each one set on the probe.

Versions

Generic: one collector reads both forms of the DMTF Redfish schema, so it stays at the common level.

Power, the resource of every Redfish version, deprecated by DMTF since release 2020.4 and still served by the cards (Dell iDRAC, HPE iLO, Supermicro, Lenovo XCC). It is read when the chassis links to it.
PowerSubsystem, its successor from release 2020.4, read when the chassis links to it and not to Power.

One collector rather than one per schema: the administrator does not have to know which schema his card serves, the outputs and the watches are the same, and a card that moves from one to the other at a firmware update keeps its probe. Power is preferred when both are served: it holds the supplies, their redundancy and the power drawn in one resource.

How it works

The collector reads, the account in Basic, GET https://<host:address>/redfish/v1/Chassis, then each chassis it lists, then:

with Power: that resource;

`` {"PowerSupplies": [{"MemberId": "0", "Name": "PS1", "Status": {"State": "Enabled", "Health": "OK"}}], "Redundancy": [{"MemberId": "0", "Name": "PSU Redundancy", "Mode": "N+m", "Status": {"State": "Enabled", "Health": "OK"}}], "PowerControl": [{"PowerConsumedWatts": 212}]} ``

with PowerSubsystem only: that resource, its PowerSupplies collection and each power supply in it, and the chassis' EnvironmentMetrics for the power drawn (PowerWatts.Reading).

A power supply or a redundancy group is named by its Name. When two bear the same name (HPE iLO calls every supply alike), each is named by its name followed by its id (MemberId or Id). A redundancy group of PowerSubsystem, which has no name, is named Redundancy 1, Redundancy 2…
health is the HealthRollup of the supply or the group when the card gives it, its Health otherwise, unknown when it gives neither; in lower case: ok, warning, critical. A degraded redundancy (one supply of two lost, or unplugged) reads warning or critical on its group.
A power supply the card says Absent is an empty bay: it is left out. A supply pulled out shows only through its redundancy group and through missing, once its name is set.
consumption is the sum of the PowerConsumedWatts of the chassis' PowerControl entries, or the PowerWatts reading of its environment metrics; an instance per chassis, named chassis <Id>.
A code 401 or 403 stops the collector misconfigured; any other code but 200 stops it unreachable, with the path it was reading. A card where no chassis serves Power nor PowerSubsystem stops it misconfigured.

The password comes from protocol:http:password, a secret variable: it only goes in the Basic header. Redfish only reads with GET.

Prerequisites

The management card's address as the host's address, reachable from the poller in HTTPS (443); its certificate trusted by the TLS profile of the probe (protocol:http:fingerprint, or its authority under protocol:tls:authorities).
A read-only account on the card (the ReadOnly role of Redfish), in protocol:http:user and protocol:http:password.

Outputs

Name	Label	Unit	Per instance
`health`	Health	—	yes, per power supply or redundancy group
`consumption`	Power drawn	W	yes, per chassis

Watches

Name	Title	Kind	Defaults	Checked by default
`unhealthy`	Power supply or redundancy degraded	state to avoid, on `health`	warning on `warning`, critical on `critical`	yes
`consumption`	High power drawn	above a threshold, on `consumption`	no threshold: it raises nothing until one is set on the probe	no
`missing`	Power supply missing	expected instances, on `health`	no supply named: it raises nothing until names are set on the probe	no

Limits

The address is written into the URL as is: an IPv6 address must be given as a name.
A blade often serves no power supply of its own: they belong to its enclosure, which is read through its own card.
A collection cut into pages (Members@odata.nextLink) is read on its first page only.
A JSON null reads as '' in Keen, which the collector takes for "not given": a PowerConsumedWatts written null is not counted, a Health written null reads unknown, which raises nothing.
Not checked against a card: the paths and fields are those of the DMTF Redfish schemas (Chassis, Power, PowerSubsystem, PowerSupply, EnvironmentMetrics), read on redfish.dmtf.org. Which firmware of each brand serves PowerSubsystem is not checked.