Meaning of "Couldn't obtain underlying metric from heatmat metric" errors.

Document ID : KB000011974
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

 This knowledge document provides a brief explanation about the following error message:

 [ERROR] [pool-12-thread-4] [Manager] AgentThresholdDeliveryService: Couldn't obtain underlying metric from heatmat metric: Variance|Differential Analysis|Default Differential Control|Frontends|Apps|comunicador|URLs|Default:Average Response Time (ms) Variance Intensity

Question:

 What does the below error message mean? It is filling up my log.

[ERROR] [pool-12-thread-4] [Manager] AgentThresholdDeliveryService: Couldn't obtain underlying metric from heatmat metric: Variance|Differential Analysis|Default Differential Control|Frontends|Apps|comunicador|URLs|Default:Average Response Time (ms) Variance Intensity

Environment:
APM 10.x releases before 10.5.1.
Answer:

 When trying to initiate the auto trigger based on a variance intensity metric, we will get the original metric from the variance intensity metric since one has to exist.  If for any that the metric is not available, then the error comes up.

 It seems there is possibility that metric is covered inside the log. In this example a FrontEnd, can be shut-off though.  So if it is shutoff while tracking it, these messages can pop up until it expires which is by default 15 minutes.

 Ideally, this message should not be there in the logs and may be tracked in supportability. This message has no performance impact and is only seen in DEBUG/VERBOSE logging in APM 10.5.1 or later.