From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Vijay Khemka <vijaykhemka@fb.com>,
Vernon Mauery <vernon.mauery@linux.intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Sensor history
Date: Mon, 13 Apr 2020 16:39:20 -0400 [thread overview]
Message-ID: <85700953-1CBE-4DFB-9A5B-AF64B9735735@fuzziesquirrel.com> (raw)
In-Reply-To: <20200410210033.GA9295@mauery.jf.intel.com>
at 5:00 PM, Vernon Mauery <vernon.mauery@linux.intel.com> wrote:
> On 30-Mar-2020 08:02 PM, Vijay Khemka wrote:
>> Is there any implementation for reading sensor history. Please point me
>> to the repo or code base.
> I do not believe that the BMC is storing any sensor history.
There were some interfaces added to the openpower namespace for this kind
of thing.
https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/org/open_power/Sensor/Aggregation/History
The application implementing them is in the phosphor-power repository
(power-supply).
> To get this, you would need to poll the sensors and store the values on
> another machine.
To implement the Redfish Telemetry service would we need to store them on
the BMC as well?
-brad
next prev parent reply other threads:[~2020-04-13 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 20:02 Sensor history Vijay Khemka
2020-04-10 21:00 ` Vernon Mauery
2020-04-13 20:39 ` Brad Bishop [this message]
2020-04-14 3:12 ` [ExternalEmail] " Troy.Lee
2020-04-14 11:03 ` [ExternalEmail] " Brad Bishop
2020-04-14 19:01 ` Vijay Khemka
2020-04-14 20:41 ` Richard Hanley
2020-04-15 8:15 ` Adrian Ambrożewicz
2020-04-15 9:52 ` [ExternalEmail] " Troy.Lee
2020-04-24 11:22 ` Matuszczak, Piotr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85700953-1CBE-4DFB-9A5B-AF64B9735735@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.intel.com \
--cc=vijaykhemka@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.