ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Attempted to create a metric with the invalid metric name

book

Article ID: 187472

calendar_today

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

We recently deployed the new 10.7 CTG extension to WebSphere app server running on z/OS using the NoRedef agent.


Some apps recently reported clamps and on checking the agent logs we find very high number of log messages similar to the following:

[ERROR] [IntroscopeAgent.Agent] Attempted to create a metric with the invalid metric name "Backends|CTG_to_CICS_ECI_IPIC_Trace|tcp://myserver.com:3120|YSS2C00:Responses Per Interval".

[ERROR] [IntroscopeAgent.Agent] Attempted to create a metric with the invalid metric name "Backends|CTG_to_CICS_ECI_IPIC_Trace|tcp://myserver.com:3121|YSS2C00:Average Response Time (ms)".

[ERROR] [IntroscopeAgent.Agent] Attempted to create a metric with the invalid metric name "Backends|CTG_to_CICS_ECI_IPIC_Trace|tcp://myserver.com:3121|YSS2C00:Responses Per Interval".

[WARN] [IntroscopeAgent.Agent] Temporarily throttling the errors sent because more than 10 have occurred in a short time

[ERROR] [IntroscopeAgent.Agent] Attempted to create a metric with the invalid metric name "Backends|CTG_to_CICS_ECI_IPIC_Trace|tcp://myserver.com:3120|YSS2C00:Average Response Time (ms)".

[ERROR] [IntroscopeAgent.Agent] Attempted to create a metric with the invalid metric name "Backends|CTG_to_CICS_ECI_IPIC_Trace|tcp://myserver.com:3120|YSS2C00:Responses Per Interval".

Should the name formatter already have replaced the illegal ":" character in the metric name?
Is this a bug in the CTG extension?
Is the metric naming problem somehow contributing to the clamps?

 

 

Environment

Release : 10.7.0

Component : APM Agents

Resolution

Deploying HF 59 resolved the issue.  Please contact Support for 10.7 HF59