Is there a way to re-initialize the server agent without restarting the application server?

[James_Lofton]

seeing appDynamics work on a development environment, where there is constant changes, it appears that the agent loses the ability to monitor those transactions and just starts out putting just service calls at the same exe. time, instead of giving the actual stack trace and execution times. Is there a way to re-initialize the server agent without restarting the application server completely, to re-run its jar file in the start-up script?

[Arun_Dasetty]

Hi Trey,

Thanks for writing in. We understood that you are referring to Lite Viewer, let us know if you are referring to appdynamics controller UI. If this is not what you referring to, Can you please provide the following details:

>>> it appears that the agent loses the ability to monitor those transactions and just starts out putting just service calls at the same exe. time, instead of giving the actual stack trace and execution times.?

Answer: Can you eloborate the issue with screenshots from UI as expect that the BT list should show aggregated exec time for overall calls and transactions snapshot should provide the code stack trace with complete exec time of particular BT request snapshot.?

>>> Is there a way to re-initialize the server agent without restarting the application server completely, to re-run its jar file in the start-up script?

Answer: You can re-iniitalize the AD agent to set the agent limit counters to back to initial values, without restarting server with agent configured (refer attached screenshot). by performaing agent reset, if there is any disconnect please eloborate the scenario in more details to better assist you further.

Let us know if you are looking for "Reset app agent" which does reset the app agent BT limit and other counters(refer attached screenshot)

And if you are referring to Pro controller UI , you can do reset from node dashboard -> agents -> click "reset" button

Thanks,

Arun

[James_Lofton]

Hey Anun,

 I tried using your method to reset the agent and it didn't seem to help. I am still getting most of my traces that look like this and am missing the important ones that I am looking for. If I restart the viewer I the agent won't seem to display any of the traces from my application. 

[Arun_Dasetty]

Hi Trey,

Thanks for posting back. We understood that you are not seeing certain packages/APIs as part of call graph for snapshot discovered, let us know if any disconnect in our understanding.

If the above said is right, Can you please try the following options:

- Start diagnostics session on BT (select "start session" from contect menu on BT in BT list screen) as referred in attached screenshot

- navigate to the new snapshot discovered for the new load applied on the BT for which session started

- click "packages have been excluded" link at the botton in call graph link and check if any packages you are listed in exclude list that you are interested in and click the link "confiugre exclude package list in call graph" to add packages to include list

By default AppDynamics agents excludes certain packages like javax.*, java.*, org.* from call graph which are usually not web application packages so that customer could focus on web app code stacktrace

- add package you want to see in "configure -> add pakcages to always show in call graph section -> save changes

- now check whether the package you are expecting shows fine for the new load and snapshot discovered in call graph.

If you still see the issue, provide the api/package name that you are expecting in call graph but not showing in call graph with screenshot of BT and latest call graph (complete screenshot including address URL section of browser)?

Thanks,

Arun