Error from the Alarm Console in Performance Management


Article ID: 195452


Updated On:


CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps


Experiencing an issue syncing alarms from Spectrum. This appears in the Alarm Console when going to 'Performance->Alarms->Alarm Console'.

When the problem is seen we see the following error that states "An unexpected error has occurred. Please check the logs for any error messages."


This has been seen where the integrated Spectrum Data Source hosts a large number of Global Collections (GC).

We first look for Landscape GCs to build these queries. When the Landscape groups are not found, it defaults to GCs to check. This results in a huge request to OneClick that is rejected if more than 150 comparisons in the REST based OR statement passed to it. This is what triggers the failure when the View is run against a large set of Groups or GCs, such as the default 'All Groups' Group in Performance Management.


Performance Management releases r20.2.1 and earlier


This has been resolved via DE468346 in the r20.2.2 release of the DX NetOps Performance Management tool.

It has also been resolved in the r3.7.15 release.

The Fixed Issues documentation shows the following entry.

  • Symptom: When running Alarm Console against Spectrum 10.4.x+ (20.2.x), it might time out or throw an error when not using a custom group. This is because the landscape group synchronized from DX NetOps Spectrum to Performance Center changed and Alarm Console did not take that into account. It uses global collection groups, and if no global collections are defined, it uses all synced DX NetOps Spectrum items. DX NetOps Spectrum also has a limit on 150 comparisons in the webservice used for Alarm Console, so if too many global collections are passed, it fails.
  • Resolution: Updated the logic to check for the old and new DX NetOps Spectrum landscape group IDs. By using landscape group, DX NetOps Spectrum can return all events for the landscape group members quicker than specifying all items in groups. In addition, to resolve the issue with 150 comparisons, up to 150 comparisons are added to the webservice request, and a message is printed to PCService.log when more than 150 comparisons is hit.
  • (20.2.2, DE468346)

If running an impacted release and unable to upgrade, the only workaround possible until upgrade is the use of smaller Groups on these Views to view Alarms.