Our Adapter dashboard having the feature to monitor the UCSM resource's faults in the ALERT widget (As we have resource relationship in the CUSTOM DASHBOARD).
We are trying to compare the faults and its details with UCSM GUI and ALERT widget. Found that 'Update time' in "Alert Widget" is not matching with 'Last Transition' time in UCSM GUI. See below snapshot -
fig : UCSM GUI for fault code - F0856, showing the 'Last Transition' as "24-Jun-2014'.
Fig : Alert Widget for Fault Code F0856, showing Update time as "9-June 2014" which is same as Start time.
We had tried to debug the code, check the ADAPTER.log regarding the last update time, found correctly updated for the external event object.
Below is the code snipet showing how we are fetching the 'Last Transition' time from faultInst maganged object and updating the external event
Date updated = formatter.parse(faultInst.getLastTransition());
2014-08-28 23:35:22,753 DEBUG [Collector worker thread 10] (138) com.cisco.ucs.vcops.processor.DataProcessor.processAndPostEvent - fething the start time :2014-06-09T17:28:38.692 and last transition time to event : 2014-06-24T16:48:59.279
Any help highly appreciated.
SO the issue is that you're pulling in change events from UCSM, however the alerts/change events in vC Ops aren't updating? I'd say probably because they're blind events with no real correlation to one another. They aren't really conditions, but likely flat notifications unassociated with one another (but they are associated with a resource).
Here's a quesiron.. do the change events you import ever "close" in status or do they always stay "active"?
The fault events which are active in UCSM are fetched and updated/imported to vCOps application.
Since all other attribute of events are showing properly in ALERT widget of vCOps so the 'updated time' should be display correctly as we are updating through the code of ADAPTER implementation.
If we presume that pulling the change event as object and importing each attribute value to ALERT widget, then all attribute value should be displayed correctly.
This may be the case if attribute binding is different in internal implementation.