Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 382980
Smarts SAM: Timestamps for correlated alarms are different for LastNotifiedAt NOTIFY and LastClearedAt CLEAR
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Smarts SAM timestamps for correlated alarms are different for LastNotifiedAt NOTIFY and LastClearedAt CLEAR Smarts SAM LastNotifiedAt takes timestamp for NOTIFY from beginning of correlation cycle Smarts SAM LastClearedAt takes timestamp for CLEAR from end of correlation cycle
Cause
The Smarts SAM LastNotifiedAt and LastClearedAt attributes are set differently by design. LastNotifiedAt uses a timestamp it gets from the underlying IP. LastClearedAt is not derived from the underlying IP, but is derived at the time Smarts SAM processes the CLEAR. The following sections of this Cause statement explain this functionality.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:AM-PM starts a correlation cycle at 2:00:00 pm.The correlation process lasts 25 seconds and the correlation then ends at 2:00:25, producing a PROBLEM (isproblem=true) in AM-PM.The problem then appears in SAM, but its "Last Notify" timestamp is 2:00:00LastClearedAt 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:PROBLEM situation changes so that the problems symptoms are no longer present.AM-PM starts a correlation cycle at 3:00:00 pmFor this example, the correlation takes 20 seconds, so that the time is at 3:00:20.In Smarts SAM, the Notification "Last Clear" timestamp will be 3:00:20.
Resolution
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
Related Information
This behavior only applies to DURABLE event type. For MOMENTARY event type, the LastNotifyAt time will change on NOTIFY.
