Blacked out Tomcat agent is throwing "Tomcat Host State" alarm (4246262)

When blacking out the collections of an Tomcat agent, the rule "Tomcat Host State" is still firing after shutting down the Tomcat server. As the agent collection is blacked out, no alarm should be triggered.

Product defect

WORKAROUND:

There are two workarounds - one is quick and easy, the other one is a bit more complex:

Workaround 1:

Create a second black out which blacks out the alarms for the same agent.

Workaround 2:

Change the calculation of the derived metric which is used by rule "Tomcat Host State".

1. Go to "Administration | Data | Manage Derived Metrics"
2. Search for "availability" metric with scope "TomcatHost"
3. Click on it to open the details
4. Now click on the the calculation "TomcatHost" under "Derived Metric Calculations", so that you can edit the script
5. Find two occurrences of "scope.agent" and replace it with "scope.monitoringAgent"
   First occurence:
   CAT.debug("TomcatHost.availability: null due to agent blackout, agentNameID: " + scope.agent.agentNameID);
   Should be:
   CAT.debug("TomcatHost.availability: null due to agent blackout, agentNameID: " + scope.monitoringAgent.agentNameID);
    
   Second occurence:
   agentID = scope.agent?.agentID;
   Should be:
   agentID = scope.monitoringAgent?.agentID; 
6. Save the calculation and then save the metric (Note: both saves are required)

STATUS:

A change request has been created. CR number: JEE-8677

It will be fixed in a future release.