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

Add CPU-Utiliziation #137

Open
HaWit opened this issue Oct 22, 2024 · 6 comments
Open

Add CPU-Utiliziation #137

HaWit opened this issue Oct 22, 2024 · 6 comments
Labels
awaiting reply waiting for a reply, close issue after 14 days of no response
Milestone

Comments

@HaWit
Copy link

HaWit commented Oct 22, 2024

Hello,
it is possible to add the CPU utility to the "check_redfish.py --proc" or to create your own query.
Background, the CPU usage of the server should be measured even without OS access.
For this purpose, the performance data of the CPU Utilization should be added to the check, ideally per CPU

e.g. at Dell

/redfish/v1/Chassis/System.Embedded.1/Sensors/SystemBoardCPUUsage

@bb-Ricardo
Copy link
Owner

bb-Ricardo commented Oct 22, 2024

Hi,

I, do you know from which version of iDRAC this is supported?

I checked a few Mockups, and none of them had this Attribute.

@bb-Ricardo
Copy link
Owner

Hi @HaWit @lpohle,

Any Updates?

@bb-Ricardo bb-Ricardo added the awaiting reply waiting for a reply, close issue after 14 days of no response label Dec 6, 2024
@HaWit
Copy link
Author

HaWit commented Dec 12, 2024

The example is from a Dell Inc. PowerEdge R740xd, BIOS: 2.22.2,BMC: iDRAC 9 (Firmware: 7.00.00.173)
As returns come:

{
  "@odata.context": "/redfish/v1/$metadata#Sensor.Sensor",
  "@odata.id": "/redfish/v1/Chassis/System.Embedded.1/Sensors/SystemBoardCPUUsage",
  "@odata.type": "#Sensor.v1_6_0.Sensor",
  "Name": "System Board CPU Usage",
  "Id": "SystemBoardCPUUsage",
  "Description": "Instance of Sensor Id",
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  },
  "Reading": 54.0,
  "PhysicalContext": "SystemBoard",
  "Oem": {
    "Dell": {
      "@odata.type": "#DellOemSensor.v1_0_0.DellOemSensor",
      "CurrentState": "Normal",
      "DeviceID": "iDRAC.Embedded.1#SystemBoardCPUUsage",
      "PossibleStates": [
        "Unknown",
        "Fatal",
        "Normal",
        "Upper Fatal",
        "Upper Critical",
        "Upper Non-Critical",
        "Lower Non-Critical",
        "Lower Critical",
        "Lower Fatal"
      ],
      "[email protected]": 9,
      "RequestedState": "NotApplicable"
    }
  },
  "Thresholds": {
    "UpperCritical": {
      "Reading": null
    },
    "UpperCaution": {
      "Reading": 101
    },
    "LowerCaution": {
      "Reading": null
    },
    "LowerCritical": {
      "Reading": null
    },
    "UpperCautionUser": {
      "Reading": 101
    }
  }

@bb-Ricardo
Copy link
Owner

Hi @HaWit,

I just pushed a commit to next-release. can you please check it and see if it works? thank you

@HaWit
Copy link
Author

HaWit commented Jan 2, 2025

Please do the same for HPE
The example is from a HPE

/redfish/v1/TelemetryService/MetricReports/CPUUtilCustom1/  |jq
{
  "@odata.context": "/redfish/v1/$metadata#MetricReport.MetricReport",
  "@odata.etag": "W/\"21D55655\"",
  "@odata.id": "/redfish/v1/TelemetryService/MetricReports/CPUUtilCustom1/",
  "@odata.type": "#MetricReport.v1_0_0.MetricReport",
  "Id": "CPUUtilCustom1",
  "Description": "Metric report of CPU Utilization for 10 minutes with sensing interval of 20 seconds.",
  "MetricReportDefinition": {
    "@odata.id": "/redfish/v1/TelemetryService/MetricReportDefinitions/CPUUtilCustom1/"
  },
  "MetricValues": [
    {
      "MetricDefinition": {
        "@odata.id": "/redfish/v1/TelemetryService/MetricDefinitions/CPUUtil/"
      },
      "MetricId": "CPUUtil",
      "MetricValue": "39",
      "Timestamp": "2025-01-02T13:28:29Z"
    },
    {
      "MetricDefinition": {
        "@odata.id": "/redfish/v1/TelemetryService/MetricDefinitions/CPUUtil/"
      },
      "MetricId": "CPUUtil",
      "MetricValue": "39",
      "Timestamp": "2025-01-02T13:28:49Z"
    },

@bb-Ricardo
Copy link
Owner

Hi,

Added it for HPE systems as well. Can you please test it with the next-release branch?

Thank you

@bb-Ricardo bb-Ricardo added this to the 1.10.0 milestone Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting reply waiting for a reply, close issue after 14 days of no response
Projects
None yet
Development

No branches or pull requests

2 participants