-
Title
Many messages for missing registry variable “End_User_Hit_Interaction_Hit_Min_Error_Threshold” filling up FMS logs -
Description
There are many messages referencing missing registry variable filling up the FMS log like below.
2016-07-12 12:40:27.963 ERROR [http-exec-15127] com.quest.wcf.core.module.function.FunctionManager - Error executing script id=system:apm_application_root_common.getRegVarScopedObjectValueHelper name="'Get RegVar Scoped Object Value - Internal Helper' from the System module APM/Application Root/Common" message: com.quest.nitro.service.sl.interfaces.scripting.ScriptingException: com.quest.nitro.service.sl.interfaces.scripting.ScriptAbortException: com.quest.nitro.service.sl.interfaces.registry.RegistryNotFoundException: Registry variable End_User_Hit_Interaction_Hit_Min_Error_Threshold not found ...
FMS: V5.7.5.3 on LinuxEndUser cartridge: 5.9.10; Application−Operations: 5.9.8.2 -
Cause
It was found out that quite a lot registry variables in EndUser cartridge were missing for some reasons. -
Resolution
Uninstalling and installing EndUser cartridge did not fix the problem. The workaround is to import related policy file into FMS to restore those missing registry variables.
"apm-rules-threshold.xml" in EndUser cartridge includes those missing registry variables and please copy it into your FMS. And then please go to your Foglight bin directory to run the following command to import this policy file.fglcmd -usr foglight -pwd foglight -cmd util:configimport -f apm-rules-threshold.xmlYou need to modify your credential and the file path after -f. Please find details in the doc below.https://support.quest.com/technical-documents/foglight/5.7.5/command-line-reference-guide/managing-agents-cartridges-and-metrics/exporting-or-importing-a-monitoring-policy