Smarts SAM: What causes the LastChangedAt value to get updated in Smarts SAM for Durable notifications?; Is there any command or log file which logs the timestamps?
search cancel

Smarts SAM: What causes the LastChangedAt value to get updated in Smarts SAM for Durable notifications?; Is there any command or log file which logs the timestamps?

book

Article ID: 303775

calendar_today

Updated On:

Products

VMware

Environment

VMware Smart Assurance - SMARTS

Resolution

What causes the LastChangedAt value to get updated in Smarts SAM for Durable notifications?
Is there any command or log file which logs timestamps when the LastChangedAt field of a notification gets updated?




Any Smarts code calling the ICS_Notification::changed() function will cause the value for the LastChangedAt field of a notification to get updated. This could be a Smarts SAM notification processing routine when it receives a Notify/clear/changed event from an underlying server, or an application/adapter call to the ICS_Notification::changed() function.

There is no command or log file which logs timestamps when the LastChangedAt field of a notification gets updated. This is because the ICS_Notification::changed() function call does not log anything to the audit log.