Hello Community,
we are facing an issue with Azure Appservices with same name and different technology type coming as duplicate services even when attributes to detect service are same.
Hello Dynatrace Community,
I am currently investigating a duplicate service detection behavior for some Windows App Services / IIS based applications.
For the same application, Dynatrace is creating two separate Web request service entities with the same visible service name. When I open the service properties, the main service detection attributes appear to be the same for both services.
Example service name:
WEBAPP-ABC
For both service entities, the following attributes are the same:
Process group:
IIS app pool WEBAPP-ABC
Context root:
/
Web application ID:
WEBAPP-ABC
Web server name:
WEBAPP-ABC
Service type:
Web request service
However, the services are still created as two separate monitored entities because the Agent technology type is different:
Service 1:
Agent technology type = IIS
Service 2:
Agent technology type = .NET
The technologies field for both services includes similar technologies such as:
.NET
ASP.NET
CLR
IIS App Pool
WCF
but the Agent technology type differs between the two service entities.
Another observation is that when I open both service entities, the .NET service appears to have received only a single request, and after that no further requests are shown. Most of the regular traffic seems to continue on the IIS service entity.
So it looks like Dynatrace briefly created or detected a separate .NET web request service for the same IIS app pool, even though the main detection contributors are the same. This makes it difficult to understand whether this is expected behavior, a temporary detection artifact, or something caused by service detection configuration.
Any help to resolve this would be appreciated
