Discussion Feed

Mario.Morelli · ‎08-17-2020

Hi What I suggest is the following. Not sure which off the shelf product you are instrumenting, but we have had some Java applications, which due to the way their startup files worked did not like having more than one JVM param added together on the same line, one after the other. So you can append them like below using JAVA_OPTS or similar in your application. The main problem is the syntax You need to use single quotes inside of the double quotes as below, where there is a space in the app/tier/node name I don't have the rest of how you are adding your code, if you re using JAVA_OPTS etc. In JAVA_OPTS you would basically append the variables one at a time JAVA_OPTS="$JAVA_OPTS -javaagent:/opt/Folder/AnotherFolder/javaagent.jar" JAVA_OPTS="$JAVA_OPTS -Dappdynamics.agent.tierName='VALUE WITH SPACES'" Once you startup the application, do a ps aux | grep command to see the application startup parameters, which will shows you where it's cutting of your arguments, and assist in fixing your problem.

Mario.Morelli · ‎08-16-2020

Hi There I don't think SignalR is supported OOB. However please enable the find entry points node setting on the relevant nodes, to log the potential entry Classes/Methods. Drive load through the application for 15-30 minutes, then view the Business Transaction Log, which should output some candidates for creation of POCO entry points.

Mario.Morelli · ‎08-13-2020

Hi There We have done 100's of Linux servers using spaces in Application Name, Tier & Node Name in the JVM startup parameters. So it does work. Can you provide your Startup arguments how you are adding them in? Ciao

Mario.Morelli · ‎08-10-2020

That's great Glad to have helped:) Ciao

Mario.Morelli · ‎08-10-2020

Hi Sai No code changes required within the Ocelot App The first step is to update the agent to latest version, as normally it should pick up the Transactions Out of the Box. Failing this ,you create a Business Transaction Detection Rule , using the following You are basically just telling the AppDynamics Agent, that this is the starting point of this transaction, please capture from here. It should bring back a BT for each "proxy endpoint" that is hit on the Ocelot Load Balancer Please restart the Machine Coordinator, and then the App after making these changes Agent Type - .Net Entry Point Type - Class/Method Then add the configuration as below

Mario.Morelli · ‎08-10-2020

Hi There Which Agent version are you using? Please use 20.3 upwards, and latest version if you can. It should work OOB, however if it doesn't, try the below POCO Class - Ocelot.LoadBalancer.Middleware.LoadBalancingMiddleware Method- Invoke Split BT on - Method param Param index - 0 Getter Chain - this.HttpContext.Request.Path.Value Ciao

Mario.Morelli · ‎08-05-2020

By system I mean the application. As the agent will do the work when capturing the snapshots and it runs with the application. This puts overhead on the system.

Mario.Morelli · ‎08-05-2020

Hi This can happen due to a variety of reasons Out of the Box, AppDynamics will have limits set to ensure it does not do excessive snapshots, as this adds overhead to the application. Most of the time you will not have a 1 to 1 ratio between Errors and snapshots, especially when the error rate is very high. You will have to check what limits you have set, under Slow/Error Thresholds for the application, and there are options to increase the snapshot collection to be more aggressive, however it will add additional overhead to the system. You need to finely balance the overhead AppDynamics puts on the application to how many snapshots it collects when errors occur or slow transactions happen. In summary AppDynamics will monitor and report on every error, but not take a snapshot for every error(on low error rates it will mostly take a snapshot for every error). You can then use the Exceptions & Error screens to zone in on the errors being seen. You can also use the Dashboarding side to report on types of errors etc. Hope this clears things up

Mario.Morelli · ‎08-05-2020

Hi Guys All you have to do is to set the following 2 parameters in your startup arguments From the Controller's perspective it will think the 2 Database Agents are running from 2 different servers. -Ddbagent.name =<db_ agent_name > -Dappdynamics.agent.uniqueHostId=<uniquehostid> The documentation states this https://docs.appdynamics.com/display/PRO45/Database+Agent+Configuration+Properties

Mario.Morelli · ‎08-05-2020

Hi You need to click on "Errors" not the count That will open the errors window You can also directly click on "Transaction snapshots" and just filter for Errors Ciao

Date Registered	‎07-03-2019 02:39 AM
Date Last Visited	‎09-27-2020 12:44 AM
Total Messages Posted	69
Total Kudos Received	45

Discussion Feed

Re: Multiple application configuration with single...

Re: Anyone able to monitor .NET SignalR transactio...

Re: Multiple application configuration with single...

Re: AppDynamics for Gateway API kind microservices

Re: AppDynamics for Gateway API kind microservices

Re: AppDynamics for Gateway API kind microservices

Re: Errors dashboard shows 4k errors but not able ...

Re: Errors dashboard shows 4k errors but not able ...

Re: Update Agent Name while installing Multiple Da...

Re: Errors dashboard shows 4k errors but not able ...