"Alarm filter criteria is too broad" error in alarms dashboard (4301865)

The following message might appear in the message window while you are using the Alarms dashboard:

Alarm filter criteria is too broad.
Please change your filter settings to reduce the number of alarms that will be returned.

If this message appears, adjust your filter settings so that Foglight displays alarms that were fired against a smaller set of topology objects.

RESOLUTION 1

Create a registry variable named 'maxTopologyResultsInAlarmQuery' if it does not already exist.

1. Select Create Registry Variable in Administration | Rules & Notifications.
2. Define the registry variable maxTopologyResultsInAlarmQuery and set it as an Integer; Save
3. Edit the registry variable and set the Global Default value of 50000;
4. Save the changes

This registry should exist beginning with the 5.5.8 version of the FMS and higher.

RESOLUTION 2

To configure a more focused alarm filter:

1. In the bottom pane of the Alarms dashboard, click the Alarm Filter [Set | Unset] link.
2. Adjust the filter to display alarms associated with fewer hosts, alarm sources (instances), and/or agents by entering text in the fields Host Name, Instance, Agent Name, and Agent Type for Foglight to filter on. Make changes to the filter settings that reflect your monitoring needs. For example:
   • If DB* is the current Agent Name filter but you are only interested in alarms associated with one of the agents monitoring your database instances (named DB_agent_1), type the agent's name in the Agent Name field.
   • If DB* is the current Instance filter but you're only interested in alarms associated a single topology object (named DB_SQL_Statement), type the object's name in the Instance field.
3. Click Update.

Note: The message continues to appear in the message window until you clear it manually. If it reappears, repeat the steps above but configure an alarm filter that is even more focused.