Recently, I came across this when looking at the list of Transaction & Services for a .Net application:
Lots of them. The following is an screenshot:
Anybody knows why this happens? Is it possible to do some configuration to avoid this? It is necessary to create custom services?
The customer environment is very simple: one application server (IIS and .Net), and one database server.
Solved! Go to Solution.
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.