AnsweredAssumed Answered

Moved to 9.5 from 9.1.1.1 and missing metrics now

Question asked by aobst on Aug 21, 2013
Latest reply on Aug 21, 2013 by aobst

Like • Show 0 Likes0
Comment • 10

Greetings all!

Recently started moving our environment (EMs and Agents) to 9.5 and I am finding that we are no longer getting half the metrics that we were before. Previously I would see metrics for backends, frontends, etc (very common items, nothing unique or custom) but since installing the 9.5 agent into the JVMs we are now missing the majority of those. Has anyone else encountered this problem and if you have, how did you resolve it?

If attached a graphic showing what Im talking about. The top grouping is after 9.5 and the bottom grouping is 9.1.1.1

Thanks!

Aaron

aobst Aug 21, 2013 3:06 PM

Correct Answer

I just realized also that I hadnt updated the profiles fully when we moved to 9.5 ... I left a number of pieces pointing to 9.1.1.1 still. Thats what I get for being rushed.

nWeb.profile:introscope.agent.extensions.directory=/opt/web/wily/9.1.1.1/wily/core/ext
nWeb.profile:introscope.agent.common.directory=/opt/web/wily/9.1.1.1/wily/common
nWeb.profile:introscope.changeDetector.rootDir=/opt/web/wily/9.1.1.1/wily/change_detector
nWebTest.profile:# CA Introscope(R) Version 9.1 Release 9.1.0.0
nWebTest.profile:introscope.agent.extensions.directory=/opt/web/wily/9.1.1.1/wily/core/ext
nWebTest.profile:introscope.agent.common.directory=/opt/web/wily/9.1.1.1/wily/common
nWebTest.profile:introscope.changeDetector.rootDir=/opt/web/wily/9.1.1.1/wily/change_detector

Aaron

See the reply in context

Attachments

Metrics.jpg67.6 KB

No one else had this question

Outcomes

walter_kacynski Aug 21, 2013 2:13 PM

It appears that AutoProbe is not working did you check the AutoProbe log file to make sure that there are no errors?

Actions

venvi05 Aug 21, 2013 2:16 PM

Hi Aaron
Seems like the new agent shows up with %1, indicating its a duplicate instance of the agent.
Can you try this stop the application, Once the agent grays out unmount the %1 instance of the agent and restart the application.
Run some transactions from your application and see if the missing metrics comes back

Vijay
CA Support

Actions

aobst @ venvi05 on Aug 21, 2013 2:19 PM

Vijay,

Sorry thats an older graphic, I should have mentioned that I cleared up the duplicate instance name. I just forgot to grab a newer screen shot. Checking out Auto probe logs to see if they give up any information.

Aaron

Actions

aobst Aug 21, 2013 2:29 PM

Only thing Im catching in the AutoProbe log as a possible issue, not one Ive come across before.

Unable to instrument. Invalid settings provided: 3 Can't proceed because there are conflicting tracer class mappings for BlamedMethodTimer, BlamedNormalCompletionSimpleIncrementor, BlamedPerIntervalCounterDifferentInstances, MethodTimerDifferentMethods, BlamedThrownExceptionPerIntervalCounter, BlamedThrownExceptionPerIntervalCounterDifferentMethods, NormalCompletionMethodTraceIncrementor, BlamedMethodTraceIncrementor, BlamedNormalCompletionMethodTraceIncrementor, BlamedMethodTraceDecrementor, BlamedPerIntervalCounterDifferentMethods, NormalCompletionPerIntervalCounter, BlamedSimpleIncrementor, MethodTraceIncrementor, BlamedNormalCompletionMethodTraceDecrementor, ThrownExceptionPerIntervalCounterDifferentInstances, PerIntervalCounter, NormalCompletionPerIntervalCounterDifferentInstances, SimpleIncrementor, BlamedThrownExceptionSimpleDecrementor, SimpleDecrementor, BlamedNormalCompletionSimpleDecrementor, NormalCompletionMethodTraceDecrementor, BlamedNormalCompletionPerIntervalCounter, BlamedMethodTimerDifferentInstances, BlamedThrownExceptionSimpleIncrementor, ThrownExceptionMethodTraceIncrementor, ThrownExceptionMethodTraceDecrementor, NormalCompletionSimpleIncrementor, BlamedThrownExceptionMethodTraceDecrementor, BlamedNormalCompletionPerIntervalCounterDifferentMethods, BlamedSimpleDecrementor, MethodTraceDecrementor, NormalCompletionPerIntervalCounterDifferentMethods, BlamedMethodTimerDifferentMethods, NormalCompletionSimpleDecrementor, BlamedPerIntervalCounter, ThrownExceptionPerIntervalCounter, BlamedThrownExceptionPerIntervalCounterDifferentInstances, MethodTimer, BlamedThrownExceptionMethodTraceIncrementor, ThrownExceptionSimpleIncrementor, BlamedNormalCompletionPerIntervalCounterDifferentInstances, PerIntervalCounterDifferentInstances, ThrownExceptionPerIntervalCounterDifferentMethods, PerIntervalCounterDifferentMethods, ThrownExceptionSimpleDecrementor, MethodTimerDifferentInstances.

Aaron

Actions

venvi05 @ aobst on Aug 21, 2013 2:35 PM

Hi Aaron,
Can you pls attach the complete Autoprobe logs if possible

Regards
Vijay

Actions

aobst Aug 21, 2013 2:37 PM

Here you go.

Attachments

nWeb_AutoProbe.nwebtestcluster_nwebtest.log.txt355.4 KB

Actions

venvi05 @ aobst on Aug 21, 2013 3:03 PM

Hi Aaron,
Reviewing the AP logs, seems like some tracers from pre 9.5 (9.1.1.1) is getting mixed up with the 9.5 agents

Few lines from the AP logs
>>>>
Introscope AutoProbe Log: /opt/projects/nwebtest/logs/nWeb_AutoProbe.20130821-092515.log
Release 9.1.1.1 (Build 581768)(Diagnos Version 2)
.
.

.Starting file dump for /com/wily/introscope/probebuilder/pbd/required.pbd

########################################################################
# Introscope Required Instrumentation Directives
#
# CA Wily Introscope(R) Version 9.1 Release 9.1.1.1
# Copyright (c) 2012 CA. All Rights Reserved.

.>>>

Can you quickly review your pbd set up from the /core/config , see if there is any mix up from the older agents and remove the conflicting entries. Restart the agent?

Regards
Vijay
CA support

Actions

aobst @ venvi05 on Aug 21, 2013 3:06 PM

Actions

venvi05 @ aobst on Aug 21, 2013 3:10 PM

Thanks Aaron, let us know if correcting the config issue clears up the problem

Actions

aobst @ venvi05 on Aug 21, 2013 3:17 PM

venvi05 wrote:
Thanks Aaron, let us know if correcting the config issue clears up the problem

Yeap that resolved it. Appreciate the second set of eyes.

Aaron

Actions

10 Replies

walter_kacynski Aug 21, 2013 2:13 PM
Mark Correct
Correct Answer
It appears that AutoProbe is not working did you check the AutoProbe log file to make sure that there are no errors?
Like • Show 1 Like1
Actions
venvi05 Aug 21, 2013 2:16 PM
Mark Correct
Correct Answer
Hi Aaron
Seems like the new agent shows up with %1, indicating its a duplicate instance of the agent.
Can you try this stop the application, Once the agent grays out unmount the %1 instance of the agent and restart the application.
Run some transactions from your application and see if the missing metrics comes back

Vijay
CA Support
Like • Show 1 Like1
Actions
- aobst @ venvi05 on Aug 21, 2013 2:19 PM
  Mark Correct
  Correct Answer
  Vijay,
  
  Sorry thats an older graphic, I should have mentioned that I cleared up the duplicate instance name. I just forgot to grab a newer screen shot. Checking out Auto probe logs to see if they give up any information.
  
  Aaron
  Like • Show 0 Likes0
  Actions
aobst Aug 21, 2013 2:29 PM
Mark Correct
Correct Answer
Only thing Im catching in the AutoProbe log as a possible issue, not one Ive come across before.

Unable to instrument. Invalid settings provided: 3 Can't proceed because there are conflicting tracer class mappings for BlamedMethodTimer, BlamedNormalCompletionSimpleIncrementor, BlamedPerIntervalCounterDifferentInstances, MethodTimerDifferentMethods, BlamedThrownExceptionPerIntervalCounter, BlamedThrownExceptionPerIntervalCounterDifferentMethods, NormalCompletionMethodTraceIncrementor, BlamedMethodTraceIncrementor, BlamedNormalCompletionMethodTraceIncrementor, BlamedMethodTraceDecrementor, BlamedPerIntervalCounterDifferentMethods, NormalCompletionPerIntervalCounter, BlamedSimpleIncrementor, MethodTraceIncrementor, BlamedNormalCompletionMethodTraceDecrementor, ThrownExceptionPerIntervalCounterDifferentInstances, PerIntervalCounter, NormalCompletionPerIntervalCounterDifferentInstances, SimpleIncrementor, BlamedThrownExceptionSimpleDecrementor, SimpleDecrementor, BlamedNormalCompletionSimpleDecrementor, NormalCompletionMethodTraceDecrementor, BlamedNormalCompletionPerIntervalCounter, BlamedMethodTimerDifferentInstances, BlamedThrownExceptionSimpleIncrementor, ThrownExceptionMethodTraceIncrementor, ThrownExceptionMethodTraceDecrementor, NormalCompletionSimpleIncrementor, BlamedThrownExceptionMethodTraceDecrementor, BlamedNormalCompletionPerIntervalCounterDifferentMethods, BlamedSimpleDecrementor, MethodTraceDecrementor, NormalCompletionPerIntervalCounterDifferentMethods, BlamedMethodTimerDifferentMethods, NormalCompletionSimpleDecrementor, BlamedPerIntervalCounter, ThrownExceptionPerIntervalCounter, BlamedThrownExceptionPerIntervalCounterDifferentInstances, MethodTimer, BlamedThrownExceptionMethodTraceIncrementor, ThrownExceptionSimpleIncrementor, BlamedNormalCompletionPerIntervalCounterDifferentInstances, PerIntervalCounterDifferentInstances, ThrownExceptionPerIntervalCounterDifferentMethods, PerIntervalCounterDifferentMethods, ThrownExceptionSimpleDecrementor, MethodTimerDifferentInstances.

Aaron
Like • Show 0 Likes0
Actions
- venvi05 @ aobst on Aug 21, 2013 2:35 PM
  Mark Correct
  Correct Answer
  Hi Aaron,
  Can you pls attach the complete Autoprobe logs if possible
  
  Regards
  Vijay
  Like • Show 1 Like1
  Actions
aobst Aug 21, 2013 2:37 PM
Mark Correct
Correct Answer
Here you go.
Attachments
- nWeb_AutoProbe.nwebtestcluster_nwebtest.log.txt355.4 KB
Like • Show 0 Likes0
Actions
- venvi05 @ aobst on Aug 21, 2013 3:03 PM
  Mark Correct
  Correct Answer
  Hi Aaron,
  Reviewing the AP logs, seems like some tracers from pre 9.5 (9.1.1.1) is getting mixed up with the 9.5 agents
  
  Few lines from the AP logs
  >>>>
  Introscope AutoProbe Log: /opt/projects/nwebtest/logs/nWeb_AutoProbe.20130821-092515.log
  Release 9.1.1.1 (Build 581768)(Diagnos Version 2)
  .
  .
  
  .Starting file dump for /com/wily/introscope/probebuilder/pbd/required.pbd
  ########################################################################
  # Introscope Required Instrumentation Directives
  #
  # CA Wily Introscope(R) Version 9.1 Release 9.1.1.1
  # Copyright (c) 2012 CA. All Rights Reserved.
  .>>>
  
  Can you quickly review your pbd set up from the /core/config , see if there is any mix up from the older agents and remove the conflicting entries. Restart the agent?
  
  Regards
  Vijay
  CA support
  Like • Show 2 Likes2
  Actions
  - aobst @ venvi05 on Aug 21, 2013 3:06 PM
    Unmark Correct
    Correct Answer
    I just realized also that I hadnt updated the profiles fully when we moved to 9.5 ... I left a number of pieces pointing to 9.1.1.1 still. Thats what I get for being rushed.
    
    nWeb.profile:introscope.agent.extensions.directory=/opt/web/wily/9.1.1.1/wily/core/ext
    nWeb.profile:introscope.agent.common.directory=/opt/web/wily/9.1.1.1/wily/common
    nWeb.profile:introscope.changeDetector.rootDir=/opt/web/wily/9.1.1.1/wily/change_detector
    nWebTest.profile:# CA Introscope(R) Version 9.1 Release 9.1.0.0
    nWebTest.profile:introscope.agent.extensions.directory=/opt/web/wily/9.1.1.1/wily/core/ext
    nWebTest.profile:introscope.agent.common.directory=/opt/web/wily/9.1.1.1/wily/common
    nWebTest.profile:introscope.changeDetector.rootDir=/opt/web/wily/9.1.1.1/wily/change_detector
    
    Aaron
    Like • Show 1 Like1
    Actions
    - venvi05 @ aobst on Aug 21, 2013 3:10 PM
      Mark Correct
      Correct Answer
      Thanks Aaron, let us know if correcting the config issue clears up the problem
      Like • Show 0 Likes0
      Actions
      - aobst @ venvi05 on Aug 21, 2013 3:17 PM
        Mark Correct
        Correct Answer
        venvi05 wrote:
        Thanks Aaron, let us know if correcting the config issue clears up the problem
        Yeap that resolved it. Appreciate the second set of eyes.
        
        Aaron
        Like • Show 2 Likes2
        Actions

Moved to 9.5 from 9.1.1.1 and missing metrics now

Attachments

Outcomes

Attachments

Related Content

Recommended Content