Hi,
I have problem setting up AppDynamics to monitor my biz transactions (in a Java standalone app). They simply don't appear in the results. I've tried to use Transaction Discovery under Configure menu, and it did find them with the config I choose (4 Spring beans for start). Then when I applied that config, there were no results under Business Transactions menu. I thought that I should restart my JVM, did that, and since then they don't even appear in the Discovery section.
BR,
Dejan
Hi Dejan,
Can you please help us provide the following details to assist you further:
- zipped version of logs folder under <agent_install_dir>/logs path before applying the node property suggested in below step
- enable node property "find-entry-points" flag to true and save the changes and restart JVM after 2-4 minutes and generate load after retart and send use the latest zipped version of logs under <agent_install_dir>/logs
Find screenshot below to update node property from UI:
- We will go through latest BusinessTrasnacitons.logs and see the possible entry points listed based on the node property output
Refer doc to define pojo rules from UI:
https://docs.appdynamics.com/display/PRO39/POJO+Entry+Points
As this is not ootb supported server we would need to define manua custom pojo rules as stated in docs once we go through the node property output with new load on the JVM to suggest possible entry.
Keep us posted the requested information to assist you further.
Regards,
Arun
Hi Arun,
Unfortunatelly we can't do that. This is our production server and we can't just start and stop it occasionaly to debug your application.
BR,
Dejan
Hi Dejan,
We thought this is test instance, we request you to provide the agent logs after setting find-entry-points flag to true and load generated to debug further. We confirm you do not required restart for the node property flag suggested to work. please keep us posted the logs to assist you further.
Regards,
Arun
Hi Arun,
We changed the param to true, and there haven't been any new entries in the BusinessTrasnacitons logs (in ~1h). Here are the other 2 logs (they had some output):
https://dl.dropboxusercontent.com/u/18839632/agent.log
https://dl.dropboxusercontent.com/u/18839632/ByteCodeTransformer.log
What is strange is that after setting this param to true, transaction discovery under configuration menu started working again (with the discovery config copied from the tier). I could see my 4 Spring transactions with expected load. However, the real monitoring, under Business Transactions, still shows no data (although it's using the same discovery config).
Btw, we're using only monitoring of Spring Beans, 4 exact matches by class & method name for now. So we don't need POJO entry setup (this one never worked at all so we tried spring and it worked from time to time).
BR,
Dejan
Hi Dejan,
By default we see spring auto discovery checkbox is disabled and to get spring beans as BTs you would need to restart, but before that we would like you to check whether the spring entry point and auto discovery checkbox is enabled or not under application "ttrade" in controller UI under Configure -> Insturmentation -, transaction detection screen
Also we see all logs under <agent_install_dir>/logs path and <agent_install_dir>/conf we could see you have provided only BCT.log and agent.log from which we could confirm that spring entry points are intercepted but cannot confirm whether auto discovery is enabled or not in UI.
Regards,
Arun
Hi Arun,
I confirm that Spring discovery is enabled in UI: http://screencast.com/t/t38LydaDsm (although not for all spring beans (the second check box is off)). If it weren't enabled, then the Configuration -> Transaction discovery shouldn't find anything either with this config (and it finds the custom bean invocations that we've defined (now that I've changed that field in agent settings to true): http://screencast.com/t/6lMhEOlsu .
No other logs except for the 2 I sent have any data written today at all.
BR,
Dejan
Hi Dejan,
Can you please disable find-entry-points flag set to false and save the changes and make sure you disable servlet, struts and other entry points (not auto discovery chebox the other one) and see how it goes with new load if issue still persists please send the logs requested earlier , as providing logs snippet which does not have details above jvm and agent version will not help us to debug further.
Keep us posted how it goes.
Regards,
Arun
Hi Arun,
All the other entry points (struts, pojo, servlet, etc.) are disabled. We're trying it with spring only, and only those 5 custom beans.
I've set the find-entry-points flag back to false, and no difference again - discovery works, but real monitoring doesn't.
Here are all the logs that I have atm: https://dl.dropboxusercontent.com/u/18839632/all_logs.zip
BR,
Dejan
Hi Dejan,
We have access to your saas ui and the settings looks fine, but would like to confirm whether the load is made currently on any of the followng apis for which you have defined four spring bean rules:
Applying method interceptor entry.spring.Identifier at com/beyondo/tt/feed/FeedMessageProcessor.processTimeMessage ((J)V) id:46
Applying method interceptor entry.spring.Identifier at com/beyondo/tt/services/impl/ClientRequestService.submitOrder ((ILjava/lang/String;)V) id:311
If yes, can you do agent reset/restart and check the behavior post the changes with new load.
If issue persists please enable checkbox "Enable servlet filter detection" and servlet entry point and auto discovery with spring rules still enabeld and see if that makes difference.
Please be sure that you would need to restart jvm if spring entry point checkbox is disabled before jvm restart .
Keep us posted how it goges.
Regards,
Arun
Hi Arun,
I confirm that we have a constant load (of 60 calls per minute, all the time) for processTi
ClientRequestService.
I did all the changes in setup you suggested, and we even restarted the JVM as part of our scheduled maintenance last Sunday, but nothing worked.
Any new ideas?
BR,
Dejan
Hi Dejan,
Can you create information points on the affected APIs and see if they get statistis as we see information points should work out of context of BT this confirms whether load is made to further debug please send the latest agent logs directory if issue persits? Also we still see spring auto discovery is disabled can you enabled this checkbox as well in addition below change on new tier
Also it looks weird that we see "All other traffic - <tier>" BT on UI under BT grid , Can you delete tier from UI if you are not bothered on old data Or restart agent with different tier and node-name and see the behavior for rules defined on new tier?
Regards,
Arun
Hi Arun,
Information points didn't work out either, no calls, no data available.
BR,
Dejan
Hi Dejan,
Can you quickly disable Servlet entry checkbox and servlet auto discovery checkbox and servlet fitler checkbox and see how it goes ? We suggested the above changes as we in your other saas controller spring BT monitor for rules defined for similar with serlvet entry checkbox disabled and only spring entry is enabled. please disable all other entry points and see how it goes with new tier and node name as we also suspect some how other traffic BT exists though no BT limit reached ?
Regards,
Arun