# Duplicate application names

**URL:** <https://community.dynatrace.com/t/duplicate-application-names/37923>\
**Category:** Open Q&A\
**Tags:** application-rules\
**Created:** [January 9, 2023, 10:29am UTC](https://community.dynatrace.com/t/duplicate-application-names/37923 "2023-01-09T10:29:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [January 9, 2023, 10:29am UTC](https://community.dynatrace.com/t/duplicate-application-names/37923/1 "2023-01-09T10:29:27Z")

</div>

Duplicate Application names, I thought it was not possible, but creating an application with existing name seems to be possible. But is undesired in my point of view, there may be a purpose, but I do not see it. Besides monitoring the underlying domains separately&nbsp;yet still using the same name.  
You can have the application list with multiple of the same name, but from outside you can not tell which is which.  
Maybe we’ve to starting thinking of application grouping?

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [January 9, 2023, 12:56pm UTC](https://community.dynatrace.com/t/duplicate-application-names/37923/2 "2023-01-09T12:56:36Z")

</div>

You can rename the application anytime, but the identifier (APPLICATION-123456789ABCDEF) is important. Initially, the identifier is derived from the application name, but then it stays fixed for the lifetime of the application. Yes, this may be confusing, but for example, this is valid also for other entities such as hosts, process groups or services.

What you can’t have is duplicate action names of the same user action type within an application.

---

<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:** [January 9, 2023, 1:08pm UTC](https://community.dynatrace.com/t/duplicate-application-names/37923/3 "2023-01-09T13:08:17Z")

</div>

to add to&nbsp;[@Julius\_Loman](https://community.dynatrace.com/user/3364),&nbsp;you also cannot have duplicate rules on two different applications.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [January 9, 2023, 1:12pm UTC](https://community.dynatrace.com/t/duplicate-application-names/37923/4 "2023-01-09T13:12:13Z")

</div>

Yes, that’s correct. Having duplicate rules, however, does not make any sense.

---

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [January 9, 2023, 1:44pm UTC](https://community.dynatrace.com/t/duplicate-application-names/37923/5 "2023-01-09T13:44:24Z")

</div>

I know they can be renamed, and the name is merely a label to the entity, identified indeed as you indicate.  
But since there’s no warning in the UI, the application can be easily be recreated by mistake. So make a notification ‘already exists are you sure’ would be an RFE candidate I guess 🙂

I understand it works as designed. But having a application list that contains the same name multiple times, does not necessarily make things clearer:

EasyTravel&nbsp;&nbsp;Poor&nbsp; 0.03 /min&nbsp; Visually complete: 2.9 s&nbsp; -&nbsp;&nbsp;0.00 /min&nbsp; 0.16 /min  
EasyTravel&nbsp; Good&nbsp; 0.12 /min&nbsp; Visually complete: 2.5 s&nbsp; -&nbsp; 0.25 /min&nbsp; 0.56 /min  
EasyTravel&nbsp; Good&nbsp;&nbsp;0.20 /min&nbsp;&nbsp;Visually complete: 1.7 s&nbsp; -&nbsp; 0.02 /min&nbsp; 1.05 /min  
EasyTravel&nbsp; No user actions during past 21min&nbsp; &nbsp;Poor&nbsp; &nbsp;0.12 /min&nbsp; Visually complete: 1.2 s&nbsp; -&nbsp; 0.03 /min&nbsp; &nbsp;0.89 /min

So proper configuration and naming policies need to be defined and followed.
