Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM: Timestamps for correlated alarms are different for LastNotifiedAt NOTIFY and LastClearedAt CLEAR (382980)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3187Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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:00

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:

PROBLEM situation changes so that the problems symptoms are no longer present.

AM-PM starts a correlation cycle at 3:00:00 pm

For 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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant