https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-detects-services-naming-them-quot-Unexpected-service/m-p/97637#M6081 <P>Looks like custom .NET processes that Dynatrace isn't picking up on the name. You can either change them manually OR setup a service naming rule based on the metadata that you see on those identified.</P><BR /> Mon, 15 Oct 2018 15:08:42 GMT tnoonan 2018-10-15T15:08:42Z https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-detects-services-naming-them-quot-Unexpected-service/m-p/97636#M6080 <P>Hi,</P><P>Recently, I came across this when looking at the list of Transaction &amp; Services for a .Net application:</P><P>Unexpected service</P><P>&lt;process name.exe&gt;</P><P>Lots of them. The following is an screenshot:</P><P><IMG src="https://community.dynatrace.com/legacyfs/online/18609-unexpected-servies.png" /></P><P>Anybody knows why this happens? Is it possible to do some configuration to avoid this? It is necessary to create custom services?</P><P>The customer environment is very simple: one application server (IIS and .Net), and one database server. </P><P>Kind Regards,</P><P>Antonio V.</P><BR /> Mon, 15 Oct 2018 11:26:45 GMT https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-detects-services-naming-them-quot-Unexpected-service/m-p/97636#M6080 antonio_villarr 2018-10-15T11:26:45Z https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-detects-services-naming-them-quot-Unexpected-service/m-p/97637#M6081 <P>Looks like custom .NET processes that Dynatrace isn't picking up on the name. You can either change them manually OR setup a service naming rule based on the metadata that you see on those identified.</P><BR /> Mon, 15 Oct 2018 15:08:42 GMT https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-detects-services-naming-them-quot-Unexpected-service/m-p/97637#M6081 tnoonan 2018-10-15T15:08:42Z