From: "Adrian Ambrożewicz" <adrian.ambrozewicz@linux.intel.com>
To: Richard Hanley <rhanley@google.com>, Vijay Khemka <vijaykhemka@fb.com>
Cc: Vernon Mauery <vernon.mauery@linux.intel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Sensor history
Date: Wed, 15 Apr 2020 10:15:20 +0200 [thread overview]
Message-ID: <bbd70c99-dc36-7d2b-ef25-a17108be8de0@linux.intel.com> (raw)
In-Reply-To: <CAH1kD+b4GQFs_V13APk8123dc_vL0GVxXwZLx6pPdUHiKodZRA@mail.gmail.com>
TelemetryService is currently in development.
Integration with EventService was tested and proved to work fine. Intel
have prepared demo for 2020 Virtual OCP Summit if you are willing to
have some insight about use cases.
We should expect solution to start appearing in upstream sooner than
later as feature is almost complete - it requires legal issues to be
sorted out.
Regards,
Adrian
W dniu 4/14/2020 o 22:41, Richard Hanley pisze:
>> Hi Team,
>>
>> There is a telemetry proposal in docs and repository.
>> https://github.com/openbmc/docs/blob/master/designs/telemetry.md
>> https://github.com/openbmc/telemetry
> > The proposal seems promising and complete.
> > What is the implementation status?
>
> I'm also curious about a status update here. Were there any design
> issues that needed to be worked out, or is it ready to develop?
>
>>> To implement the Redfish Telemetry service would we need to store them on
>>> the BMC as well?
> >It will be nice if we can store it in RAM at least with larger data
> and some diskspace
> >With small log rotate.
>
> The Telemetry Service already has a concept of log rotation, but overall
> I agree that storing in RAM first with optional persistence is better
> than the other way around.
> - Richard
next prev parent reply other threads:[~2020-04-15 8:15 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
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 [this message]
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=bbd70c99-dc36-7d2b-ef25-a17108be8de0@linux.intel.com \
--to=adrian.ambrozewicz@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rhanley@google.com \
--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.