topic Re: Define custom error using request attribute in Alerting

Define custom error using request attribute

alea_fowler — Tue, 25 Jun 2019 20:01:52 GMT

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 I should be able to choose "greater than" as an option.

Re: Define custom error using request attribute

skrystosik — Tue, 25 Jun 2019 20:05:40 GMT

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

Sebastian

Re: Define custom error using request attribute

alea_fowler — Tue, 25 Jun 2019 20:16:25 GMT

@Sebastian K. Yes. 😞 I was hoping to create a custom error when the amount of requests reached a certain threshold.

Re: Define custom error using request attribute

Joe_Hoffman — Tue, 25 Jun 2019 21:25:33 GMT

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?

Re: Define custom error using request attribute

alea_fowler — Thu, 27 Jun 2019 19:42:17 GMT

@Joseph M. H. 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.