Services are not getting detected on standalone .NET exe processes.

You have deployed new /already have few standalone  .NET exe processes that are shown in Dynatrace UI , but wondering why services are not getting auto-detected for them. What should be done about it ?

Here, you are running into the default behaviour for .NET where only w3wp (IIS) processes are instrumented automatically. In other words , Dynatrace doesn’t automatically perform deep monitoring on all .NET processes as there are many arbitrary processes that rely on these processes.

More details on this can be found at Process deep monitoring — Dynatrace Docs

So, first sugggestion would be to configure custom service detection rule , which will help to list the expected service.This can be esaily set up using the details mentioned in this link Define custom services — Dynatrace Docs

If Custom Service creation rules are not making any improvements, I would recommend to try utilising the Dynatrace .NET one agent SDK GitHub - Dynatrace/OneAgent-SDK-for-dotnet: Enables custom tracing of .NET applications in Dynatrace · GitHub
OneAgent SDK — Dynatrace Docs

If still desired services are not getting reflected , please do reach out to Dynatrace Technical support with relevant details

Thanks !

9 Likes

Thanks for sharing this, It would be nice if the system did reference which rule was being triggered for denial of deep monitoring, otherwise you have to kind of comb through them all.