# Define custom error using request attribute

**URL:** <https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129>\
**Category:** Alerting\
**Tags:** request-attributes, problems-classic\
**Created:** [June 25, 2019, 8:01pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129 "2019-06-25T20:01:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alea\_fowler](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/alea_fowler/32/29188_2.png) [@alea\_fowler](https://community.dynatrace.com/u/alea_fowler)\
**Post date:** [June 25, 2019, 8:01pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129/1 "2019-06-25T20:01:52Z")

</div>

Why don’t I have the option of defining a rule using “greater than” when I am editing a particular service to add a custom error using a request attribute? According to [this documentation](https://www.dynatrace.com/support/help/how-to-use-dynatrace/services-and-transactions/configuration/configure-service-error-detection/?_ga=2.156097659.1750352934.1561488256-1045251982.1559055750) I should be able to choose “greater than” as an option.

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [June 25, 2019, 8:05pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129/2 "2019-06-25T20:05:40Z")

</div>

Is your request attribute configured as numeric (integer for example)? If not this may be reason

Sebastian

---

<div class="post-metadata">

**Author:** ![alea\_fowler](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/alea_fowler/32/29188_2.png) [@alea\_fowler](https://community.dynatrace.com/u/alea_fowler)\
**Post date:** [June 25, 2019, 8:16pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129/3 "2019-06-25T20:16:25Z")

</div>

[@Sebastian K.](https://answers.dynatrace.com/users/15061/view.html) Yes. 😞 I was hoping to create a custom error when the amount of requests reached a certain threshold.

---

<div class="post-metadata">

**Author:** ![Joe\_Hoffman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/joe_hoffman/32/30752_2.png) [@Joe\_Hoffman](https://community.dynatrace.com/u/Joe_Hoffman)\
**Post date:** [June 25, 2019, 9:25pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129/4 "2019-06-25T21:25:33Z")

</div>

I don’t have any problems seeing “Greater than” option when defining a custom Error on a service.

To reproduce:

Select the service, → Edit

Select Error Detection

Select Add Custom Error Rule

If I select a source thats defined to be a string, I don’t get the "Greater Than’ option. But if the source is defined to be Integer, the “Greater than” shows up.

But I"m not sure this is what you want. It sounds like you want to trigger on the quantity of transactions, not the value of a given transactions request parameter. Or does the Request Attribute contain the trigger value?

 ![21077-screen-shot-2019-06-25-at-21833-pm.png](https://global.discourse-cdn.com/dynatrace/original/3X/8/2/821ceeb7cf1959e451c0e63b0d0459dec582922a.png)

---

<div class="post-metadata">

**Author:** ![alea\_fowler](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/alea_fowler/32/29188_2.png) [@alea\_fowler](https://community.dynatrace.com/u/alea_fowler)\
**Post date:** [June 27, 2019, 7:42pm UTC](https://community.dynatrace.com/t/define-custom-error-using-request-attribute/21129/5 "2019-06-27T19:42:17Z")

</div>

[@Joseph M. H.](https://answers.dynatrace.com/users/3021/view.html) yeah I was hopping to create a trigger if the quantity of transactions is greater than x (amount).

What I’m looking at is identifying Bot traffic - which I’ve done via request attribute. Now I’m trying to figure out the trend so I can establish a baseline to create a custom error event.