Platform telemetry and health monitoring

[Neeraj Ladkani]

  1.  How do define what data to be collected and how ?  We need a way to let BMC know
     *   What data to read ?
     *   When to read ?
     *   How to read ?


  1.  Does redfish support  pulling telemetry from system?


Neeraj


On 6/12/19 11:58 AM, Neeraj Ladkani wrote:
Thanks Kun for summarizing notes.

For detailed notes: https://github.com/openbmc/openbmc/wiki/Platform-telemetry-and-health-monitoring-Work-Group<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fopenbmc%2Fwiki%2FPlatform-telemetry-and-health-monitoring-Work-Group&data=02%7C01%7Cneladk%40microsoft.com%7Cf658bdd374f44f32401408d6f3fa4174%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964653505825428&sdata=co4X%2Fx5bXgvix9IWeAc%2B6ndRE%2FA0utcFs05O8Y1uYOQ%3D&reserved=0>

Neeraj

From: openbmc <openbmc-bounces+neladk=microsoft.com at lists.ozlabs.org><mailto:openbmc-bounces+neladk=microsoft.com at lists.ozlabs.org> On Behalf Of Kun Yi
Sent: Tuesday, June 11, 2019 11:24 AM
To: Alexander Amelkin <a.amelkin at yadro.com><mailto:a.amelkin at yadro.com>
Cc: OpenBMC Maillist <openbmc at lists.ozlabs.org><mailto:openbmc at lists.ozlabs.org>
Subject: Re: Platform telemetry and health monitoring

Neeraj mentioned he will send out the meeting minutes. He will also look into setting up a wiki page holding the contents as well as minutes.

A few quick notes from top of my head from the kick-off meeting:
- did a round table, all the orgs have similar requirements
- need to look into how existing infra fit into the needs and what falls short
- will have workstreams for:
    - what to collect
    - how to collect
    - how to store
    - how to export
- collectd sounds interesting and promising for collecting metrics
- IPMI SELs have limitations as an event reporting mechanism, possibly need to have a new events or error log reporting mechanism to aggregate fault logs from different components
- will need to look into Redish and expand the specs as necessary to fit our needs

On Tue, Jun 11, 2019 at 2:02 AM Alexander Amelkin <a.amelkin at yadro.com<mailto:a.amelkin at yadro.com>> wrote:
I second the idea of reusing collectd. It's pretty standard and popular.

With best regards,
Alexander Amelkin,
Leading BMC Software Engineer, YADRO
https://yadro.com<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyadro.com&data=02%7C01%7Cneladk%40microsoft.com%7Cf658bdd374f44f32401408d6f3fa4174%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964653505835416&sdata=w67kPLkBQrb3LuZFr4wi24z9CcwawmRs6PLBAxpH49k%3D&reserved=0>

05.06.2019 15:49, Brad Bishop wrote:
> On Tue, Jun 04, 2019 at 12:35:05PM -0700, Kun Yi wrote:
>> FYI: Srinivas, Neeraj, and I are finalizing a time slot for the kick off
>> meeting. We are thinking about a bi-weekly discussion.
>>
>> Also, I'm drafting a version of BMC metrics collection daemon. The first
>> draft is up on https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/22257<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.openbmc-project.xyz%2Fc%2Fopenbmc%2Fdocs%2F%2B%2F22257&data=02%7C01%7Cneladk%40microsoft.com%7Cf658bdd374f44f32401408d6f3fa4174%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964653505845417&sdata=41DNGtt2iaKVo426GNvcpFL6RBzmpsNeYl7ns88BKPc%3D&reserved=0>,
>> which we probably will go over during the meeting.
>
> I just wanted to point out the collectd project:  https://collectd.org/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcollectd.org%2F&data=02%7C01%7Cneladk%40microsoft.com%7Cf658bdd374f44f32401408d6f3fa4174%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964653505845417&sdata=l30Ftw%2B0qh31WaWIW6nVHI7UaLbvJwvODh%2Buh99TJJ0%3D&reserved=0>
>
> I'm not sure if it is suitable or not but it seems like a pretty close match to what you are trying to do and it would be a lot of code you don't have to write.
>
> Just something to consider.
>
> thx - brad


--
Regards,
Kun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190618/3bbc5164/attachment-0001.htm>