Request to create repository google-ipmi-bmc-health

Vijay Khemka vijaykhemka at
Fri Oct 2 05:05:28 AEST 2020

Hi Sui,

On 9/30/20, 8:30 AM, "openbmc on behalf of Sui Chen" < at on behalf of suichen at> wrote:

    Hello OpenBMC community,

    We are working on an IPMI blob-based implementation of BMC health
    monitoring. We currently have an internal working prototype version
    and would like to upload it to this newly proposed repository,
    openbmc/google-ipmi-bmc-health .

In my opinion, we can enhance existing health-monitor and add your features.

    We are aware of existing BMC health monitoring designs such as:
    1. and its

    Main differences between this implementation and existing ones are:
    - google-ipmi-bmc-health is implemented with the IPMI blob handler
    framework and exists as an IPMI blob handler, while
    phosphor-health-monitor runs as a daemon and exposes BMC health
    metrics on DBus in the same manner sensors are exposed.

Is this going to be a library or daemon, Same health-monitor daemon can 
Be enhanced to add these functionalities.

    - This implementation does not check health metric values against
    thresholds or perform actions when thresholds are crossed.

If you don't define threshold in configuration file, health-monitor will
also not monitor metrics defined.

    - This implementation currently reports uptime, memory usage, free
    disk space, CPU time consumed by processes, and file descriptor stats.

Same can be added as extra metrics. That was the goal of this repo as to
start with basic metrics and add more as required.

    - This implementation does not read a configuration file yet. It
    always reads the hard-coded set of health metrics listed above.

We can enable or disable certain metrics through this configuration file.

    - This implementation does not post-process sensor readings such as
    compute the average CPU usage over a certain time window.

Window size 1 can give latest data rather than averaged data.

    As such, this implementation differs enough from existing ones such
    that we believe we have enough reasons to have a separate repository
    for it.

I will strongly prefer to add all of the features in the existing repo.


More information about the openbmc mailing list