How to install Agent Apm for DotNet Apps?

hello sir
i have some questions that i couldnt find the answer i hope you help to solve it.

in our company we have more that 200 dotnet application with different versions
some of the are dotnet framework
some others are dotnet core with different versions
even we have the latest version of the dotnet

by the way we never thinks about having a apm service to trace and profiling of these apps
now managers need it (i know its so bad after long time undrestand you need monitoring for your services)
i guess you can get it how much is hard to tell you develop teams to config it they are busy they cant accept it, it take more than normal time
i undrestand there is a way we dont need to change the codebase (some people call it zerocode) and with a agent that install next to your app can monitor your app and easily connect to the APM Server

so where is my problem?
i dont know how to install it?
the way i should use to install
is it just a dll i should copy it to the application directory
if its possible make me understood

TNX

Hi @amin_nazari Welcome to the community.

Did you look at the documentation?

Here are the supported versions, it is likely not all your versions are supported but perhaps there is significant coverage.

There are several ways to get instrumentation running... auto instrumentation is the "zero code" approach

Perhaps come back with some specific question and we can help...

1 Like

Thanks @stephenb
i checked and i couldnt underestand but i will check it again because i found somethings else while i researched last night.

i have some question is it support dotnet 7 8 9?
i didnt any thinge refer to it that would not support or support it.
and other things is am i should config kibana to connect to the apm server and receive data from agents?

Best Wishes

Yes with the Elastic Legacy Agent

This means >>>> .NET Core 2.0 or newer <<<, and .NET Framework 4.6.2* or newer.

To be clear there are 2 overall approaches

  1. Elastic APM Agents which I referred to above, and yes those agent
    APM Agen -> APM Server -> Elasticsearch - Kibana

  2. There are also the Brand New Elastic Distribution of Open Telemetry... they are brand new.

You can look at that here

Reference Architecture

APP -> EDOT SDK -> EDOT Collector -> Elastic -> Kibana

.NET Zero Code

Since it is Based on the OTEL SDK - Support Here

Yes it is all a bit confusing right now... lots of options... I think you need to roll up your sleeves and pick one and get started.

1 Like

I appreciate you @stephenb
you give me a lot of idea.

i guess one question left :grimacing: (I hope)
managing the servers is on my shoulder
base on my less knowledge about these server i think i will face with some problems
for previous option i should have 3 servers (elastic apm, Elasticsearch, kibana)
am i should config server to accept apm request or not if i start it and connect it to the Elasticsearch is enough?

and the new brand that you introduced i need to setup new servers?

if its possible give me a view of the server side as well.

TNX @stephenb

Yes, APM does require some extra management.

What version of Elastic Stack are you using?

Yes. There are 2 architectures on this page using Fleet + APM Server or Legacy APM Binary.

I suggest reading these docs thoroughly