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

**URL:** <https://community.dynatrace.com/t/services-are-not-getting-detected-on-standalone-net-exe-processes/41503>\
**Category:** Troubleshooting\
**Tags:** dotnet\
**Created:** [September 4, 2023, 1:54pm UTC](https://community.dynatrace.com/t/services-are-not-getting-detected-on-standalone-net-exe-processes/41503 "2023-09-04T13:54:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vineet\_Sinha](https://avatars.discourse-cdn.com/v4/letter/v/3be4f8/32.png) [@Vineet\_Sinha](https://community.dynatrace.com/u/Vineet_Sinha)\
**Post date:** [September 4, 2023, 1:54pm UTC](https://community.dynatrace.com/t/services-are-not-getting-detected-on-standalone-net-exe-processes/41503/1 "2023-09-04T13:54:18Z")

</div>

You have deployed new /already have few&nbsp;standalone&nbsp; .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&nbsp;for .NET where&nbsp;only w3wp (IIS) processes are instrumented automatically.&nbsp;In other words , Dynatrace doesn’t automatically perform deep monitoring on&nbsp;all .NET&nbsp;processes as there are many arbitrary processes that rely on these processes.

More details on this can be found at&nbsp;[Process deep monitoring — Dynatrace Docs](https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/pg-monitoring)

So, first sugggestion would be to&nbsp;_configure custom service detection rule ,_&nbsp;which will help to list the expected service.This can be esaily set up using the details mentioned in this link&nbsp;[Define custom services — Dynatrace Docs](https://www.dynatrace.com/support/help/platform-modules/applications-and-microservices/services/service-detection-and-naming/service-types/custom-services)

If Custom Service creation rules are not making any improvements, I would recommend to try utilising the Dynatrace .NET one agent SDK&nbsp;[GitHub - Dynatrace/OneAgent-SDK-for-dotnet: Enables custom tracing of .NET applications in Dynatrace · GitHub](https://github.com/Dynatrace/OneAgent-SDK-for-dotnet)  
[OneAgent SDK — Dynatrace Docs](https://www.dynatrace.com/support/help/extend-dynatrace/extend-tracing/oneagent-sdk)

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

Thanks !

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [September 7, 2023, 12:35pm UTC](https://community.dynatrace.com/t/services-are-not-getting-detected-on-standalone-net-exe-processes/41503/2 "2023-09-07T12:35:19Z")

</div>

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.
