Duplicate alarms were generated for the same instance without previous alarm being cleared (97740)

Duplicate alerts where generated for the same instance without the previous alarm being cleared by a user or the rule itself. If the rule condition changes, the rule clears the alarm and it would be regenerated, if condition matches again.

If the 10k internal processing limit for alarms is reached, you might be hitting a problem where not all alarms are considered when the conditions are checked.

Please follow the steps below to increase the limit temporary:

1. Open the JMX console of the FMS: <FMS-Server>:<port>/jmx-console
2. Log in with user foglight
3. Search for "service=Alarm" and click on it, to open it
4. Find the attribute "MaxAlarms" and change it from 10000 to 20000
5. Now scroll to the bottom of the table and click on "Apply Changes"

DO NOT restart the FMS afterwards. The change it not written in the FMS DB, it is only persistent in the FMS cache.

To make the change persistent, modify the server.config file like described below:

1. Log in the Foglight Manager Server
2. Go to "FMS_install_dir/config/"
3. Make a backup copy of the file "server.config"
4. Go to the line where the server vm option are set
5. Add the line:
   server.vm.option0="-Dfoglight.alarm.query.max_alarms=20000"
6. Save the file
7. Restart the Foglight Management server