-
Title
Alarm templates not loading when using reference values in registry variables -
Description
The alarm templates do not load completely when there are thresholds registry variables that use reference values; the alarms list stops at the rule that contains the variable.
The following error is present in the Management Server logs after the alarm templates fail to load:
YYYY-MM-DD hh:mm:ss.SSS ERROR [http-exec-7] org.glassfish.jersey.server.ServerRuntime$Responder - An I/O error has occurred while writing a response message entity to the container output stream. org.glassfish.jersey.server.internal.process.MappableException: com.fasterxml.jackson.databind.JsonMappingException: (was java.lang.NullPointerException) (through reference chain: com.quest.forge.rest.alarm.template.v1.model.RuleConfigListResult["ruleConfigs"]->java.util.ArrayList[13]->com.quest.forge.rest.alarm.template.v1.model.MultiSeverityRuleConfig["criticalConfig"]->com.quest.forge.rest.alarm.template.v1.model.SeverityConfig["registryValues"]->java.util.ArrayList[0]->com.quest.forge.rest.alarm.template.v1.model.RegistryValue["value"]->com.quest.nitro.service.registry.RegistryReferenceValue["factor"])
-
Resolution
WORKAROUND
Configure a static registry variable value instead of a registry reference.
Example:
STATUS
This issue was logged as FOG-4637 and has been fixed in the 6.3.0 and higher releases of the Foglight Management Server. -
Defect ID
FOG-4637