* Sensor history @ 2020-03-30 20:02 Vijay Khemka 2020-04-10 21:00 ` Vernon Mauery 0 siblings, 1 reply; 10+ messages in thread From: Vijay Khemka @ 2020-03-30 20:02 UTC (permalink / raw) To: openbmc [-- Attachment #1: Type: text/plain, Size: 118 bytes --] Is there any implementation for reading sensor history. Please point me to the repo or code base. Regards -Vijay [-- Attachment #2: Type: text/html, Size: 1562 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Sensor history 2020-03-30 20:02 Sensor history Vijay Khemka @ 2020-04-10 21:00 ` Vernon Mauery 2020-04-13 20:39 ` Brad Bishop 0 siblings, 1 reply; 10+ messages in thread From: Vernon Mauery @ 2020-04-10 21:00 UTC (permalink / raw) To: Vijay Khemka; +Cc: openbmc 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. To get this, you would need to poll the sensors and store the values on another machine. --Vernon ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Sensor history 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 19:01 ` Vijay Khemka 0 siblings, 2 replies; 10+ messages in thread From: Brad Bishop @ 2020-04-13 20:39 UTC (permalink / raw) To: Vijay Khemka, Vernon Mauery; +Cc: openbmc 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [ExternalEmail] Re: Sensor history 2020-04-13 20:39 ` Brad Bishop @ 2020-04-14 3:12 ` Troy.Lee 2020-04-14 11:03 ` [ExternalEmail] " Brad Bishop 2020-04-14 19:01 ` Vijay Khemka 1 sibling, 1 reply; 10+ messages in thread From: Troy.Lee @ 2020-04-14 3:12 UTC (permalink / raw) To: Brad Bishop, Vijay Khemka, Vernon Mauery; +Cc: openbmc 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? Thanks, Troy Lee -----Original Message----- From: openbmc <openbmc-bounces+troy.lee=vertiv.com@lists.ozlabs.org> On Behalf Of Brad Bishop Sent: Tuesday, April 14, 2020 4:39 AM To: Vijay Khemka <vijaykhemka@fb.com>; Vernon Mauery <vernon.mauery@linux.intel.com> Cc: openbmc@lists.ozlabs.org Subject: [ExternalEmail] Re: Sensor history 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 CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ExternalEmail] Sensor history 2020-04-14 3:12 ` [ExternalEmail] " Troy.Lee @ 2020-04-14 11:03 ` Brad Bishop 0 siblings, 0 replies; 10+ messages in thread From: Brad Bishop @ 2020-04-14 11:03 UTC (permalink / raw) To: Troy.Lee; +Cc: Vijay Khemka, Vernon Mauery, openbmc at 11:12 PM, Troy.Lee@vertiv.com wrote: > 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 Oops - I had forgotten about this. This is a much better answer/pointer, thanks Troy! -brad ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Sensor history 2020-04-13 20:39 ` Brad Bishop 2020-04-14 3:12 ` [ExternalEmail] " Troy.Lee @ 2020-04-14 19:01 ` Vijay Khemka 2020-04-14 20:41 ` Richard Hanley 1 sibling, 1 reply; 10+ messages in thread From: Vijay Khemka @ 2020-04-14 19:01 UTC (permalink / raw) To: Brad Bishop, Vernon Mauery; +Cc: openbmc On 4/13/20, 1:39 PM, "Brad Bishop" <bradleyb@fuzziesquirrel.com> wrote: 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? It will be nice if we can store it in RAM at least with larger data and some diskspace With small log rotate. -brad ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Sensor history 2020-04-14 19:01 ` Vijay Khemka @ 2020-04-14 20:41 ` Richard Hanley 2020-04-15 8:15 ` Adrian Ambrożewicz 0 siblings, 1 reply; 10+ messages in thread From: Richard Hanley @ 2020-04-14 20:41 UTC (permalink / raw) To: Vijay Khemka; +Cc: Brad Bishop, Vernon Mauery, openbmc [-- Attachment #1: Type: text/plain, Size: 787 bytes --] > 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 [-- Attachment #2: Type: text/html, Size: 1642 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Sensor history 2020-04-14 20:41 ` Richard Hanley @ 2020-04-15 8:15 ` Adrian Ambrożewicz 2020-04-15 9:52 ` [ExternalEmail] " Troy.Lee 0 siblings, 1 reply; 10+ messages in thread From: Adrian Ambrożewicz @ 2020-04-15 8:15 UTC (permalink / raw) To: Richard Hanley, Vijay Khemka; +Cc: Vernon Mauery, openbmc, Brad Bishop 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [ExternalEmail] Re: Sensor history 2020-04-15 8:15 ` Adrian Ambrożewicz @ 2020-04-15 9:52 ` Troy.Lee 2020-04-24 11:22 ` Matuszczak, Piotr 0 siblings, 1 reply; 10+ messages in thread From: Troy.Lee @ 2020-04-15 9:52 UTC (permalink / raw) To: Adrian Ambrożewicz, Richard Hanley, Vijay Khemka Cc: Vernon Mauery, openbmc, Brad Bishop Adrian, Thanks for the update! Thanks Troy Lee -----Original Message----- From: openbmc <openbmc-bounces+troy.lee=vertiv.com@lists.ozlabs.org> On Behalf Of Adrian Ambro?ewicz Sent: Wednesday, April 15, 2020 4:15 PM To: Richard Hanley <rhanley@google.com>; Vijay Khemka <vijaykhemka@fb.com> Cc: Vernon Mauery <vernon.mauery@linux.intel.com>; openbmc@lists.ozlabs.org; Brad Bishop <bradleyb@fuzziesquirrel.com> Subject: [ExternalEmail] Re: Sensor history 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 CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [ExternalEmail] Re: Sensor history 2020-04-15 9:52 ` [ExternalEmail] " Troy.Lee @ 2020-04-24 11:22 ` Matuszczak, Piotr 0 siblings, 0 replies; 10+ messages in thread From: Matuszczak, Piotr @ 2020-04-24 11:22 UTC (permalink / raw) To: Troy.Lee, Adrian Ambrożewicz, Richard Hanley, Vijay Khemka Cc: Vernon Mauery, openbmc, Brad Bishop Hi, I would like to upload a patch for the telemetry documentation that addresses the report storage in non-volatile memory and some D-Bus API extensions for better alignment with the Redfish Telemetry Service. The changes are results of integration with the Event Service. Piotr Matuszczak --------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173, 80-298 Gdansk KRS 101882 NIP 957-07-52-316 -----Original Message----- From: openbmc <openbmc-bounces+piotr.matuszczak=intel.com@lists.ozlabs.org> On Behalf Of Troy.Lee@vertiv.com Sent: Wednesday, April 15, 2020 11:53 AM To: Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com>; Richard Hanley <rhanley@google.com>; Vijay Khemka <vijaykhemka@fb.com> Cc: Vernon Mauery <vernon.mauery@linux.intel.com>; openbmc@lists.ozlabs.org; Brad Bishop <bradleyb@fuzziesquirrel.com> Subject: RE: [ExternalEmail] Re: Sensor history Adrian, Thanks for the update! Thanks Troy Lee -----Original Message----- From: openbmc <openbmc-bounces+troy.lee=vertiv.com@lists.ozlabs.org> On Behalf Of Adrian Ambro?ewicz Sent: Wednesday, April 15, 2020 4:15 PM To: Richard Hanley <rhanley@google.com>; Vijay Khemka <vijaykhemka@fb.com> Cc: Vernon Mauery <vernon.mauery@linux.intel.com>; openbmc@lists.ozlabs.org; Brad Bishop <bradleyb@fuzziesquirrel.com> Subject: [ExternalEmail] Re: Sensor history 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 CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-04-24 11:24 UTC | newest] Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2020-04-15 9:52 ` [ExternalEmail] " Troy.Lee 2020-04-24 11:22 ` Matuszczak, Piotr
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.