RFC for Telemetry data collection

[Brad Bishop]

Hi Tom

I don’t really disagree with anything you wrote…I’m just throwing out some additional thoughts.

I would propose that we:

1 - Add support to the REST server to subscribe to DBus signals, and simply forward the signal content in JSON format out over a websocket.  This allows an external user to get any async notification that any code running on the BMC can get.  I have a lot of questions on specifics here but I’ll save those for later, in case this doesn’t work out.

2 - Write an application to run on the BMC that subscribes to DBus signals and each time it occurs, creates a DBus object with the content of the signal again in JSON format.  The signals to subscribe to (and therefore the resulting “history” DBus objects for) would be defined via per-platform YAML.

From there implementing different “eventing” interfaces like Redfish, DCMI, SNMP traps, or whatever Rick does with protobufs :-) becomes an exercise in:

1 - If the eventing interface is async, socket based: Doing the same as #1 above in a new application, but applying a transformation on the JSON.
2 - If the eventing interface is sync, history based: Write an application that transforms the objects created by #2 above.

Does anyone see this framework not enabling them to meet their requirements?  Please poke holes.

-brad



> On Sep 7, 2017, at 11:20 AM, tomjose <tomjose at linux.vnet.ibm.com> wrote:
> 
> Hello,
> 
> I am working on the issue (https://github.com/openbmc/openbmc/issues/1957) to design a telemetry application for the OpenBMC. I would be explaining a rough idea of how we plan to go about. Please share your thoughts and feedback on this proposal.