APMDEBUG :: Messages reported at INFO level

[Lee Barton]

​Hi
Any idea how I can suppress these please?
I am monitoring IBM BPM with Version 10.7.x , and am noticing in the logs a LOT of APMDEBUG:: messages at INFO level that I don't remember seeing before :

12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: modulename is XXXXXX
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: modulename is XXXXXX
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: componentname is XXXXXXEmpInfo_Med
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: componentname put in data XXXXXXEmpInfo_Med
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: primitiveName is XXXXXInfoRespAfterMap
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] XXXXXXInfoRespAfterMap
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: primitiveType is XXXXXXInfoRespAfterMap
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] XXXXXXInfoRespAfterMap
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: primitiveName is invoke : XXXXXXInfo
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] invoke : XXXXXXInfo
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: primitiveType is XXXXXXInfo_invoke_InputResponse
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] XXXXXXInfo_invoke_InputResponse
12/29/19 01:30:18 AM EST [INFO] [IntroscopeAgent.WebSphereProcessServer_WESB] APMDEBUG :: componentname is XXXXXXEmpInfo_Med

Is there a way to surpress these as the Agent log file is massive with these being the majority of them by far.

[David Lewis]

Hello Lee,
It looks like you have a debug jar there, if you might have had a support case in the past to determine an issue, we do write extra code in. It isn't immediately obvious what files are debug, we would ultimately have to review your agent folder to look for candidates. The related file should be called something like WPSAgentExt.jar  in the agent's core/ext folder

If that is happening from default code, it should be something for us to change. Having said that, I'm fairly sure we stopped supplying/supporting the WPS/WESB extension since APM 10.3

As a workaround you can set logging for that module to WARN which is the next highest severity as listed in log4j documentation

https://www.tutorialspoint.com/log4j/log4j_logging_levels.htm

So you could add this into the agent profile. This ought to take effect immediately (well as soon as a config reload can happen) but it might need a restart to stop.

log4j.logger.IntroscopeAgent.WebSphereProcessServer_WESB=WARN,console,logfile

Many thanks,
David Lewis





------------------------------
https://www.tutorialspoint.com/log4j/log4j_logging_levels.htm
------------------------------

[Geethu John]

Hi @Lee Barton,

Were you able to successfully monitor IBM BPM? I see other discussions where it was told "IBM BPM requires WAS 8.5.5.5 which is supported by APM 9.6-10.3. However, there is no specific configuration or extension to support BPM". ​ In 10.3 comptibility guide, it is written support has been removed for BPM.

Did the java agent provide useful info in monitoring BPM

Geethu