metric values in summary metrics
Article ID: 192272
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
CA Application Performance Management (APM / Wily / Introscope)
INTROSCOPE
DX Application Performance Management
Issue/Introduction
There is something wrong in the summary metrics behind "Frontends|Messaging Services (onMessage)|Queues|{queue}". We believe that the queue metrics are not adding correctly the calls from their respective Called Backends.
In the good example we can see that in the path "Frontends|Messaging Services (onMessage)|Queues|{queue}" it appears that there was a response and if we fetch it in the respective Called Backends ("Frontends|Messaging Services (onMessage)|Queues|{queue}|CalledBackends|{service}") we can find it.
In the bad example we can see a call under Called Backends but if we look up Responses Per Interval of the queue metric (that summaries all the called backends) we can´t find it, we loose sight of it in Introscope.
In the good example we can see that in the path "Frontends|Messaging Services (onMessage)|Queues|{queue}" it appears that there was a response and if we fetch it in the respective Called Backends ("Frontends|Messaging Services (onMessage)|Queues|{queue}|CalledBackends|{service}") we can find it.
In the bad example we can see a call under Called Backends but if we look up Responses Per Interval of the queue metric (that summaries all the called backends) we can´t find it, we loose sight of it in Introscope.
Environment
Release : 10.7.0
Component : APM Agents
Resolution
We noticed that there is a metric clamp on the agent. It seems like that might be what is causing this problem.
Please check the information related to metric clamp in agent logs and agent profile, and adjust it accordingly.
Please check the information related to metric clamp in agent logs and agent profile, and adjust it accordingly.
Feedback
Yes
No
Powered by
