Post by thalerj on Jun 6, 2019 17:46:55 GMT
Hi,
I'm looking for a few recommendations for how to handle a couple of different situations regarding subscribing to data from a BMC. I'm not sure if this is more of a feature request or if a way exists to do this leveraging the existing REST API.
My first big question is around Event subscriptions. The model outlined for event subscriptions seems to require having a full REST server running to receive notifications for new events. I wanted to ask if there's a good way to get notifications without a full REST server running as this adds a significant amount of overhead if I want to listen for new alerts on an HTTP5 based application or with a bash script. I'm also concerned from a scale perspective as the push notifications are an entire log entry and I didn't know if there's a way to scale back to only get certain fields from the log entries. Considering an event storm across a hundred nodes (for example powering up 100 systems) would generate a lot of events and an enormous amount of network traffic since the full log entry is passed along.
I may have misunderstood some of how the event subscription service works though as is outlined here: redfishforum.com/board/1/protocol-specification
My second question is around subscribing to sensor readings. Is there a way to subscribe to sensor readings that is being tracked by the BMC, such that, they can be streamed to an external application? For example, as part of the openbmc project they had a basic subscription protocol methodology which can be found here:
I didn't know if there's something similar available using redfish.
Any help would be greatly appreciated.
