banshee/hardware-collection/hardware/redfish/https/processors

Processors of a server, by Redfish

Returns, for each processor a server's management card serves by Redfish, its health, its type and its number of cores. Two watches are offered, each one set on the probe.

Versions

Generic: written for the ComputerSystem and Processor schemas of DMTF Redfish, whose fields read here have kept their form since the first versions (2016). Any management card that serves them: Dell iDRAC, HPE iLO, Supermicro, Lenovo XCC, OpenBMC. Hence the common level.

How it works

The collector reads, the account in Basic, GET https://<host:address>/redfish/v1/Systems, each system it lists, its Processors collection, then each processor in it.

{"Id": "CPU.Socket.1", "Name": "CPU 1", "Socket": "CPU.Socket.1", "ProcessorType": "CPU", "TotalCores": 32, "Status": {"State": "Enabled", "Health": "OK"}}

A processor is named by its Name, or its Socket without one; when two bear the same name, each is named by its name followed by its Id.
health is the processor's HealthRollup or Health, in lower case (ok, warning, critical), unknown when it gives neither.
type is its ProcessorType in lower case: cpu, and on some cards gpu, fpga, accelerator, which the system lists with its processors.
cores is its TotalCores.
A socket the card says Absent is empty: it is left out.
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 that serves no processor 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 processor
`type`	Type	—	yes, per processor
`cores`	Cores	—	yes, per processor

Watches

Name	Title	Kind	Defaults	Checked by default
`unhealthy`	Processor degraded	state to avoid, on `health`	warning on `warning`, critical on `critical`	yes
`missing`	Processor missing	expected instances, on `health`	no processor 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.
The load of a processor is not the card's to say: it is read from the system itself (linux-collection, windows-collection).
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 TotalCores written null is not returned, 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 (ComputerSystem, Processor), read on redfish.dmtf.org.