Post by fish on Oct 17, 2019 11:55:07 GMT
Hi,
I was looking at new event handling. E.g. reading in page 7+8 in powerpoint for “Redfish Events & Message changes in 2018.2”.
www.dmtf.org/sites/default/files/Redfish_School-Events_2018.2.pdf
Page 8 in presentation describes how to model clearing of “state-full” events/alerts. Using “ClearingLogic” property I can describe that one Event/Message will clear some other state-full Event/Message in the MessageRegistry file. E.g. as in the example where Message "ResourceErrorsDetected" is cleared by “"ResourceErrorsCorrected” according to:
"ResourceErrorsDetected": { }
"ResourceErrorsCorrected": {
"ClearingLogic": {
"ClearsIf": "SameOriginOfCondition",
"ClearsMessage": [
"ResourceErrorsDetected“
]} }
Using this mechanism, I need to define two Messages for all state-full events/alarms in the MessageRegistry, one for the raise-event and one for the cease/clear event.
But the Event also contains property Severity. I think this one should have values “Critical”, “Warning”,”OK”, even if there is only informal/textual reference for this string-type property to “Status” (“Health” property in Resource ?).
A more simple solution for raise and clear of state-full Events would be to use only single Event Message, by setting Severity to “Critical” or “Warning” at raise, and sending same Event Message but with Severity set to “OK” when event is cleared. This solution can be used for all simple case with one-to-one mapping between events for raise and clear. Advantage with this solution is that I don’t need to specify double amount of Event Messages and I don’t need to specify the same trivial “ClearingLogic” for all of them.
Can I assume that this “Severity-based” mechanism for raise and clear of events is also OK to use for a Redfish service? And maybe go for the more advanced features of “ClearingLogic-based” mechanism for raise and clear only when needed? I did not find anything about this in the specification document, and the PPT-file only described usage of ClearingLogic? And what is Severity=”OK” used for if not for clearing previously raised Event with same Message?
Could you also consider including some more specific type definition of Event “Severity” property using some enum?
BR
/Magnus
I was looking at new event handling. E.g. reading in page 7+8 in powerpoint for “Redfish Events & Message changes in 2018.2”.
www.dmtf.org/sites/default/files/Redfish_School-Events_2018.2.pdf
Page 8 in presentation describes how to model clearing of “state-full” events/alerts. Using “ClearingLogic” property I can describe that one Event/Message will clear some other state-full Event/Message in the MessageRegistry file. E.g. as in the example where Message "ResourceErrorsDetected" is cleared by “"ResourceErrorsCorrected” according to:
"ResourceErrorsDetected": { }
"ResourceErrorsCorrected": {
"ClearingLogic": {
"ClearsIf": "SameOriginOfCondition",
"ClearsMessage": [
"ResourceErrorsDetected“
]} }
Using this mechanism, I need to define two Messages for all state-full events/alarms in the MessageRegistry, one for the raise-event and one for the cease/clear event.
But the Event also contains property Severity. I think this one should have values “Critical”, “Warning”,”OK”, even if there is only informal/textual reference for this string-type property to “Status” (“Health” property in Resource ?).
A more simple solution for raise and clear of state-full Events would be to use only single Event Message, by setting Severity to “Critical” or “Warning” at raise, and sending same Event Message but with Severity set to “OK” when event is cleared. This solution can be used for all simple case with one-to-one mapping between events for raise and clear. Advantage with this solution is that I don’t need to specify double amount of Event Messages and I don’t need to specify the same trivial “ClearingLogic” for all of them.
Can I assume that this “Severity-based” mechanism for raise and clear of events is also OK to use for a Redfish service? And maybe go for the more advanced features of “ClearingLogic-based” mechanism for raise and clear only when needed? I did not find anything about this in the specification document, and the PPT-file only described usage of ClearingLogic? And what is Severity=”OK” used for if not for clearing previously raised Event with same Message?
Could you also consider including some more specific type definition of Event “Severity” property using some enum?
BR
/Magnus