Historical Sensor Information
Joseph Reynolds
jrey at linux.ibm.com
Sat Aug 17 03:02:11 AEST 2019
On 8/15/19 5:50 PM, Wilfred Smith wrote:
> Many thanks to Emily, Milton and Kun Yi for their quick responses and
> pointers.
>
> Among the reasons for local historical data collection are independent
> auditing, disaster recovery, debugging and increasing availability
> during periods of intermittent network connectivity.
>
> Vijay is already participating in the Telemetry workgroup, so I’ll try
> to get a download from him to see what can be leveraged.
>
> The requirement at Facebook includes the ability to retrieve
> historical sensor information for a user-defined period and interval
> on the BMC console (through sensor-util, and in the same format).
> Based on my cursory review of collectd, its lossy multicast network
> protocol wouldn’t allow this information to be re-synthesized with
> fidelity on the
I share this concern and would prefer to have a more reliable way to get
sensor data off the BMC. This data may be valuable to help detect when
the BMC is being attacked.
- Joseph
> client side, but it would be a huge win if we can get a few
> concessions. I intend to study the Telemetry Workgroup’s progress
> carefully.
>
> Wilfred
>
...snip...
More information about the openbmc
mailing list