CPU alarms violating a set threshold is not generating an alarm for a certain device, events missing.
CPU Events are not seen in Performance Management Performance Center web UI.
Memory Events are not seen in Performance Management Performance Center web UI.
Component Item Events are not seen in Performance Management Performance Center web UI.
This is seen for some Component Items but not all of them, some work fine.
DX NetOps Performance Management releases r20.2.2 and earlier
In the default configuration Component Items, those like CPU and Memory, aren't synchronized as individual items to Performance Center inventory. In that form Events for those items are raised against the device that manages them.
In the r20.2.1 and r20.2.2 releases of DX NetOps Performance Management these items were incorrectly marked as syncable. This takes place during Discovery update cycles when changes are found for the affected component items. When they need changes made, it is then that the incorrect syncable flag is set on the items. This is why we'll see the issue for some component items but not others on the same device or between different devices.
Because that is only part of the process to enable sync of these items to Performance Center Inventory, they remain unknown to the Event Manager.
The result of this is an inability for Event Manager to determine what Performance Center item it's been synced to raise the Event against. The Component item isn't found in Performance Center inventory as a properly synced item by Event Manager and it believe it is a properly synced item that should be found.
The end symptom is the Event and the items Data Aggregator Item ID is put in the Event Manager em MySql database unresolved_event_items table.
With it present in this table it will never be displayed in Performance Center.
This is resolved via DE474142 in the DX NetOps Performance Management release r20.2.3.
To properly resolve this upgrade to the r20.2.3 or a newer release.
When resolving this there are two choices. Upgrade now and fix it, or work around it and upgrade later, fixing it after the upgrade at that time. The two choices are:
To validate this is the problem being faced: