When "Foglight Memory Usage Check" / "Catalyst Memory Usage Check" alarm appears on the Federator Foglight Management Server (FMS), how to determine where it originated from? Hovering over the alarm's 'Origin' field shows that it originated from 'Local Server'.
1. On all FMS' (Federator and Federated), create a new Foglight Registry variable called "CatalystHost" as String type. Edit the variable and set the Global Default of it to the name of the particular FMS that you are on.
2. On all FMS' (Federator and Federated), modify the "Foglight Memory Usage Check" rule (note: in newer versions of Foglight, this rule is called "Catalyst Memory Usage Check".
a. In the rule severity, create a Severity Level Variable as Expression type, and call it 'var3' - enter the following in the Expression/Message box:
b. Modify the alarm message using @var3. It might look something like this:
Rule @foglight_rule_name fired with @foglight_severity_level_name severity. The Management Server's memory usage is critically high at @var2 MB. This alarm originated on @var3.
(The example above added the string "This alarm originated on @var3." to the default out of the box alarm message)
Setting each of the FMS' Memory Usage Check rules to include their FMS name in the Alarm message will allow the actual originating child FMS' name to be propagated with the alarm as it reaches the Federator's alarm console.
Enhancement request number FGL-12472 has been submitted to Development for consideration in a future release of Foglight.