As mentioned above this function seems to assume that the only DIMM
send are DIMM health events. It's ok to save other object monitoring to a later
but let's at least support DIMM health
...and DIMM detected events:
There should be an event type included in the json. Along with 'timestamp' and
I think we need an 'event' field so that consumer code can make assumptions
the format of the event record. I think 'dimm-health' and 'dimm-detect'
are the only
event record types we need to support in this initial version.
I would like to confirm whether my understanding of the feature in each dimm-event is
right or not.
Checking the Spare Block Remaining Trip in Alarm Trips, if set then the notification is
Checking the NVDIMM Media Temperature Trip in Alarm Trips, if set then the notification
Checking the NVDIMM Controller Temperature Trip in Alarm Trips, if set then the
notification is dimm-controller-temperature.
Checking the Health Status, if changed then the notification is dimm-health-state.
Checking the Last Shutdown Status, if changed then the notification is
Checking the UUID of DIMM, if changed then the notification is dimm-detected.
Is there a possibility that a notification contains multiple dimm-events?
Should I need to turn off the event alarm after the notification logged?
Thank you very much.