Discussion Feed

Harrison.Clark

Any updates on this? We want to take our monitoring and ops to the next level with automated remediation, but it seems remediation scripts are still not supported in .NET environments?

Ashish.Singh

Hi Tamir, If we understand, you have two server name one is like " server01" and another is like "server01-java-MA". The Controller UI might show the server name with "-java-MA" appended to the host ID. This is expected behavior; the "-java-MA" suffix indicates that the host has a Standalone Machine Agent running in .NET Compatibility Mode. For more details, please refer to the below document. https://docs.appdynamics.com/display/PRO45/.NET+Compatibility+Mode Let us know if it helps. Thanks, Ashish.

Andrew.Draut

That does answer my question. I had hoped to use the BT on the Main method as a fallback for unconfigured specific BTs for a .Net console application that acts as a job/process runner. It would be nice for this scenario to work, though as it would save a lot of time configuring BTs and allow instrumenting the entire process as there is a bunch of setup code that runs before each job/process that is not currently captured because we have to configure the BT for something farther down the call chain.

Ashish.Singh

Hi Michael, Could you please review the below document, and let us know if it helps. "When you enable object instance tracking for a node, AppDynamics analyzes the heap to identify classes with the most instances on the heap. AppDynamics tracks the top 20 .NET framework classes and the top 20 application classes based upon the number of instances. Use object instance tracking to identify memory usage trends in classes with large numbers of instances." For more details please review the below document. https://docs.appdynamics.com/display/PRO45/Object+Instance+Tracking+for+.NET Thanks, Ashish.

Blaine.Johnson · ‎01-14-2020

Thanks Ashish!

Ashish.Singh · ‎01-13-2020

Hi P auric, As per the logic and implementation, .Net Core microservices agents are the App Agent only and it does not provide the machine-related metrics to the controller for that application node also there is no separate .NET Core machine agent available. To report the machine related data metrics to the controller for that specific host machine, you can install the standalone java machine agent separately to report the machine level data metrics. So, It will consume only 1 machine agent license extra. During the recent observation on the windows machine, with the latest available version ( for ex. 4.5.18 ) of .NET Core microservice agent instrumentation in case you have also the latest .NET .msi based Agent installed on the same host machine, we notice that .NET msi based machine agent reports the machine level metrics on the application node as well. Could you please try in any lower or testing environment to check this behavior. Let us know if it helps or you have any further questions. Thanks, Ashish.

Ashish.Singh · ‎01-12-2020

Hi Ahmed, We notice that you have already raised a ticket with us with number #217116 and our team is already working on this. We will further do followups to this issue on the ticket which you have raised with us. Thanks, Ashish.

Ashish.Singh · ‎01-12-2020

Hi Doug, As per our precious AppDynamics documents, it seems for the Config Management requirement was " .NET Agent 4.1 or later installed on machines where you plan to deploy configuration." So, it looks like this Config Management for .NET feature was present from .Net Agent version 4.1.X. For reference, you can refer to the below document [ It is 4.1.x version related document ] https://docs.appdynamics.com/display/PRO41/Manage+Configuration+for+.NET Please let us know if it helps, or you have any further questions. Thanks, Ashish.

pauric.coyle · ‎01-10-2020

Perfect that makes sense. Correct me if I am wrong but if we have the old .NET machine agent installed on our server this is not compatible with the new .Net core micro services agents that will be installed on the applications or will a new .NET core machine agent need to be installed on the server also ?

Ashish.Singh · ‎01-09-2020

Hi Narasimha, If application is a .NET 4.5 framework based MVC API running on the windows VM, then we do not have any NuGet package specific for the solution, To instrument this kind of application, you would need to use the .NET msi based agent installer. If you have applications, those are based on .NET Core 2.0 or above and running on windows VM, then to instrument these applications you can use the .NET Core microservice agent for windows NuGet package. Let us know if it helps or you have any further questions. Thanks, Ashish.

Date Registered	‎07-07-2016 09:45 AM
Date Last Visited	Friday
Total Messages Posted	75
Total Kudos Received	31

Discussion Feed

Re: Remediation Script on Windows Node

Re: Machine Agent Grayed

Re: Split .Net Business Transaction on Method Arra...

Re: Memory tracking .net windows application

Re: Limits on tiers

Re: Is the current .NET machine agent compatible ...

Re: .net app agent isn't reporting BTs data

Re: Centralized config management

Re: Difference between .Net Microservices agent an...

Re: AppD on Premise without .NET Agent, but only t...