# Application Rules

**URL:** <https://community.dynatrace.com/t/application-rules/13716>\
**Category:** Open Q&A\
**Tags:** settings\
**Created:** [July 13, 2018, 1:18pm UTC](https://community.dynatrace.com/t/application-rules/13716 "2018-07-13T13:18:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![barryla](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@barryla](https://community.dynatrace.com/u/barryla)\
**Post date:** [July 13, 2018, 1:18pm UTC](https://community.dynatrace.com/t/application-rules/13716/1 "2018-07-13T13:18:25Z")

</div>

Hi, currently in Dynatrace, creating an application is a tedious process of selecting 1 rule at a time.

Can the application rule definition be made easier by allowing to select multiple conditions. At the moment, I have the following problem

We have 3 applications running on the same application server, the name of the applications are [Application — AI for All.](http://application.com/abc), [Application — AI for All.](http://application.com/def) and [Application — AI for All.](http://application.com/ghi).

This is in the live system, we then have the following applications in our test environment, [t-application.com/abc](http://t-application.com/abc), [t-application.com/def](http://t-application.com/def) and [t-application.com/ghi](http://t-application.com/ghi).

How would I be able to differentiate the 3 applications in the live system from those in the test system?

I would like to create 6 different applications namely:

| ABC\_Live | [Application — AI for All.](http://application.com/abc) |
| --- | --- |
| DEF\_Live | [Application — AI for All.](http://application.com/def) |
| GHI\_Live | [Application — AI for All.](http://application.com/ghi) |
| ABC\_Test | [t-application.com/abc](http://t-application.com/abc) |
| DEF\_Test | [t-application.com/def](http://t-application.com/def) |
| GHI\_Test | [t-application.com/ghi](http://t-application.com/ghi) |

Thanking you in advance

---

<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:** [July 13, 2018, 1:37pm UTC](https://community.dynatrace.com/t/application-rules/13716/2 "2018-07-13T13:37:20Z")

</div>

You just have to setup the application rules as precise as possible. Rules can be set on URL or hostname. So basically, unless both production and test environment for application is accessed using the **exactly same URL,** it’s just a matter of correct rule setup.

---

<div class="post-metadata">

**Author:** ![kalle\_lahtinen](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kalle\_lahtinen](https://community.dynatrace.com/u/kalle_lahtinen)\
**Post date:** [January 10, 2019, 10:06pm UTC](https://community.dynatrace.com/t/application-rules/13716/3 "2019-01-10T22:06:35Z")

</div>

Yep, in my case the URLs are exactly the same, only the domain differs. So because the rule options are so rigid, I have two options to go with:

1. Not being able to distinguish between app1 and app2

2. Not being able to distinguish between production and test

\*\*\*

Edit: actually, I should’ve checked the demo environment first, always good for examples. So it seems you can actually define URL-based rules also in a way that contains the domains - e.g. “All URLs starting with [http://ec2-54-91-154-186.compute-1.amazonaws.com/image\_gallery](http://ec2-54-91-154-186.compute-1.amazonaws.com/image%5C_gallery)”

I’ll go and test that now, looks like it should work in my case 🙂