Duplicate web request services created for same IIS App Pool when Agent technology type differs between IIS and .NET

[Saqib_Fayaz]

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

[sujit_k_singh]

Hi @Saqib_Fayaz 

This is a known behavior with IIS-hosted .NET applications and is not necessarily a configuration issue.

While the visible service detection attributes (Web application ID, Context root, Web server name, Process group, etc.) may be identical, Dynatrace also considers the agent technology type when identifying services.

In your screenshots, the only notable difference is that one service is reported with Agent technology type = IIS and the other with Agent technology type = .NET. Despite sharing the same IIS application pool and detection attributes, Dynatrace can create separate service entities when traffic is observed from different technology perspectives.

The fact that the .NET service only contains a single request while ongoing traffic continues to the IIS service suggests that the .NET entity may be a short-lived detection artifact rather than an actively used duplicate service.

I would review the service creation time, any application deployments or app pool recycles around that period, and whether the .NET service continues to receive traffic. If it remains inactive and receives no new requests, it is likely just a stale service entity rather than an indication that traffic is being split between two active services.

Has anyone from Dynatrace Support confirmed whether differing Agent technology types (IIS vs .NET) alone can result in separate web request service entities for the same IIS-hosted application?

Thanks,

Sujit