LastNotifiedAt processing sequence
Using the time from the beginning of correlation as LastNotify could be considered misleading, but it is not seen as incorrect behavior because the notification generated after the correlation is based on the events active at the beginning of the cycle. For example, consider the following Last Notify sequence:
LastClearedAt processing sequence
LastClearedAt sets as the current time when SAM processes it. The main reason for this design is if Smarts SAM implemented original CLEAR timestamps, it may cause some unexpected behaviors such as auto-acknowledgement executing faster since the interval starts from the time of LastClearedAt. Moreover, auto-clear action would still assign the current time. The "Last Clear" processing sequence (continuing the preceding Last Notify sequence example) is as follows:
Smarts is working as currently designed. EMC Smarts Engineering has advised that changing this functionality would require an enhancement request that would need to be reviewed and approved. If you require this functionality, you can submit an enhancement request on Powerlink at the following location:
Home > Support > Request Support > Request a Product Enhancement