DX Application Performance Management

Expand all | Collapse all

Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

  • 1.  Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Posted 11-19-2015 03:38 AM
      |   view attached

    Hello Team,

     

    Many of the tibco BW Agents are showing only 'EM Host/Port'  metrics.

     

    SS is attached for more information so Please help.

     

    Thanks Vaibhav



  • 2.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Broadcom Employee
    Posted 11-19-2015 10:13 AM


  • 3.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Broadcom Employee
    Posted 11-20-2015 12:08 AM

    Hi Vaibhav,

    If you find that clamping is not occurring it could be an agent configuration problem i.e. Agent.jar getting loaded but not the agent profiile.

    I have seen similar with other AppServer agents and in that the case no agent logs are created.

    So if these were previously working agents something must have changed with the agent config. for TIBCO BW.

    Hope it helps.

    Lynn



  • 4.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Posted 11-22-2015 01:10 PM

    Can you please check if your BW services are started from the files (.tra) from the one where you have made the changes ?

    In BW, we also need to take care that how my services are deployed - container based or individual tra's for each service. ?

     

    If not, could you please check the logs for the same ?

     

    Regards,

    Vaibhav



  • 5.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Posted 11-23-2015 04:44 AM

    Hello All,

     

    Agent.jar is getting loaded fine as all of BWAgent is accessing same Mount Point and I am facing this issue for some of the agents only.Nothing is changed for TIBCO BW.

    My TIBCO BW is started from .tra file only which I want...

     

    PFA Agent logs:-

     

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.stalls.thresholdseconds=30

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.synthetic.node.name=Synthetic Users

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.synthetic.user.name=Synthetic_Trace_By_Vuser

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.threaddump.MaxStackElements=12000

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.threaddump.deadlockpoller.enable=false

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.threaddump.deadlockpollerinterval=15000

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.threaddump.enable=true

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.ttClamp=50

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.urlgroup.group.default.format=Default

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.urlgroup.group.default.pathprefix=*

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.agent.urlgroup.keys=default

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.autoprobe.deepinheritance.enabled=true

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.autoprobe.directivesFile=default-typical.pbl,hotdeploy,spm.pbl,webspheremq.pbl,tibcobw-typical.pbl

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.autoprobe.enable=true

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.autoprobe.logfile=../../logs/AutoProbe.log

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.bootstrapClassesManager.enabled=true

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.bootstrapClassesManager.waitAtStartup=5

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.agentID=

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.enable=false

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.isengardStartupWaitTimeInSec=15

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.profile=ChangeDetector-config.xml

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.rootDir=/opt/tibco2/ca/BwMonitor/wily/change_detector

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] introscope.changeDetector.waitTimeBetweenReconnectInSec=10

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment

    11/23/15 05:22:36 PM SGT [INFO] [IntroscopeAgent.Properties] java.awt.printerjob=sun.print.PSPrinterJob

     

    Please suggest



  • 6.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Broadcom Employee
    Posted 11-23-2015 04:25 PM

    Hi Vaibhav,

    In that case it sounds like this could be more like the clamping scenario suggested by Yanna in her earlier advice with the KB. Have you checked the EM logs for the Collector(s) for the relevant message per that KB?

    Thanks

    Lynn



  • 7.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Posted 11-24-2015 05:13 AM

    Hi Lynn,

     

    I have update from CA Support on this issue and they said they found clamps

    in logs as follows:-

     

    MOM log:-

     

    11/19/15 07:57:45.431 PM SGT 

    [Clamp : introscope.enterprisemanager.agent.metrics.limit,

    Value : 250,000]

     

    11/19/15 07:57:45.774 PM SGT 

    [Clamp :

    introscope.enterprisemanager.disconnected.historical.agent.limit, Value :

    400]

     

    11/19/15 07:57:45.774 PM SGT 

    [Clamp : introscope.enterprisemanager.events.limit, Value :

    1,250]

     

    11/19/15 07:57:45.957 PM SGT 

    [Clamp : introscope.enterprisemanager.agent.trace.limit,

    Value : 1,000]

     

    11/19/15 07:57:45.957 PM SGT 

    [Clamp : introscope.enterprisemanager.agent.error.limit,

    Value : 10]

     

    and the collector have one clamp message

     

    apm-threasholds file

    introscope.enterprisemanager.collector.cdv.max

     

    As per above configuration, What can be the maximum value we can configure

    to avoid clamp.

     

    Please suggest.

     

    Thanks & Regards

    Vaibhav Jindal

    006587278701

    Senior Consultant for APM

    On Nov 24, 2015 05:26, "Lynn_Williams" <



  • 8.  Re: Many of the tibco BW Agents are showing only 'EM Host/Port' metrics

    Broadcom Employee
    Posted 11-24-2015 04:19 PM

    Which value is clamped?

     

    We prefer to scale by adding a collector instead of raising the clamps. Although we do not recommend it you can raise the limits in small increments as long as your EM is healthy.

     

    Make sure to continuously monitor your EM health after changing the limits!

     

    Ciao,

    Guenter