# Limitation on number of Request Attributes in an Environment and allowed number of conditions in a RA?

**URL:** <https://community.dynatrace.com/t/limitation-on-number-of-request-attributes-in-an-environment-and-allowed-number-of-conditions-in-a-ra/20548>\
**Category:** Open Q&A\
**Tags:** request-attributes\
**Created:** [October 12, 2020, 9:35pm UTC](https://community.dynatrace.com/t/limitation-on-number-of-request-attributes-in-an-environment-and-allowed-number-of-conditions-in-a-ra/20548 "2020-10-12T21:35:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\
**Post date:** [October 12, 2020, 9:35pm UTC](https://community.dynatrace.com/t/limitation-on-number-of-request-attributes-in-an-environment-and-allowed-number-of-conditions-in-a-ra/20548/1 "2020-10-12T21:35:22Z")

</div>

Hi, please let me know if there is a limitation for following in Dynatrace Managed trial/small environment

1. Limitation of the number of Request attributes allowed? Is there an overhead if I have more than 100 Request attributes?
2. Maximum number of Data source conditions that we can apply in a Request attribute? I am planning to have 30+ data source conditions in each request attribute.

Appreciate your help! Thanks, Suresh.

---

<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:** [October 13, 2020, 6:30am UTC](https://community.dynatrace.com/t/limitation-on-number-of-request-attributes-in-an-environment-and-allowed-number-of-conditions-in-a-ra/20548/2 "2020-10-13T06:30:12Z")

</div>

I think it depends on the request attribute type and methods of capture.

Overall I don’t think there is a limit right now on the number of request attributes in an environment.

I would recommend:

- not setting “return all distinct values” unless necessary
- limiting the scope of request attributes only for process groups where it is necessary (typically by tags, technologies or by other filters)
- not using request attributes based on code instrumentation (JAVA/NET/…) if the value can be returned by another capture type (URL, HTTP request header, … )
- defining proper naming for your request attributes, so you don’t get lost within those definitions after some time
- if there are some general kinds of request attributes (for example capturing Soap Action) that span different processes, keep it Global.
- it’s ok to have multiple conditions, they are evaluated and the first rule matches. Keep that in mind when defining the order. But 30+ conditions seems to be too much. Most likely you can rewrite that in a more efficient way.

---

<div class="post-metadata">

**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\
**Post date:** [October 13, 2020, 9:59pm UTC](https://community.dynatrace.com/t/limitation-on-number-of-request-attributes-in-an-environment-and-allowed-number-of-conditions-in-a-ra/20548/3 "2020-10-13T21:59:28Z")

</div>

Thanks [@Julius L.](https://answers.dynatrace.com/users/16467/view.html) Similar to Key requests, I have to tag around 30 different web requests with ‘Type1’ so that I can filter them while charting/doing MDA. Similar to that have to Tag the second set of 30 unique requests as ‘Type2’. My understanding is, this is doable in 2 ways. please suggest if there is an efficient way than this

#1 - Define a RA ‘Type1’ and write 30 data source conditions (condition#1 - contains /abc/test, condition#2 - contains /def/lab, …so on)

#2 - Create a Tag ‘Type1’ and create a rule with 30 conditions