Threshold and Availability for REST API Transaction

Add Threshold and Availability for REST API Transaction

1. Click Admin > Configuration Profiles > Threshold and Availability.
2. Click Add Threshold and Availability in Threshold and Availability screen.
3. Specify the following details for adding threshold and downtime rules for Web Transaction:
   • Monitor Type: Select Web Transaction from the drop down list.
   • Display Name: Provide a label for identification purpose.
   • Number of locations to report monitor as down: Choose from the drop down to receive alert notification when the website is down from specified number of locations.
4. Specify the following details for Threshold Configuration:
   • Notify in case of read timeout: Move the toggle button to Yes to receive alerts when you're not receiving the entire HTTP response within 30 seconds
   • Response time threshold for primary monitoring location: Enter a value in milliseconds to get notified when the response time from primary location crosses the specified value.
   • Response time threshold for secondary locations: Enter a value in milliseconds to get notified when the response time from secondary location crosses the specified value.
     
     Note

     Advanced Threshold Settings (Strategy):
     Poll count serves as the default strategy to validate the threshold breach. You can validate threshold breach by applying multiple conditions (>, <, >=, <=, =) on your specified threshold strategy. The monitor’s status changes to ”Trouble or Critical”  when the condition applied to any of the below threshold strategies hold true:

     • Threshold condition validated during the poll count (number of polls): Monitor’s status changes to trouble or critical, when the condition applied to the threshold value is continuously validated for the specified “Poll count”.
     • Average value during poll count (number of polls): Monitor’s status changes to trouble or critical, when the average of the attribute values, for the number of polls configured, continuously justifies the condition applied on the threshold value.
     • Condition validated during time duration (in minutes): When the specified condition applied on the threshold value is continuously validated, for all the polls, during the time duration configured, monitor’s status changes to trouble or critical.
     • Average value during time duration (in minutes): Monitor’s status changes to trouble or critical, when the average of the attribute values, for the time duration configured, continuously justifies the condition applied on the threshold value.

     
     Multiple poll check strategy will not be applied by default. During the conditions where no strategy could be applied, the threshold breach will be validated for a single poll alone.

     
     
     Note

     To make sure the condition applied on the strategy “Strategy-3: Time duration or Strategy-4: Average value during time duration” for threshold breach detection works as intended, you must ensure that you specify a time duration which is at least twice the applied check frequency for that monitor.

     
     
     
5. Click Save.
6. The threshold and availability profile created for your API endpoints application will be automatically listed in Threshold and Availability screen along with the others already created.
   
   Note

   A default threshold and availability profile for API endpoints will be automatically listed in Threshold and Availability screen when the users for the first time click Admin> Inventory > Monitors > Add Monitor > REST API Transaction.

Edit Threshold and Availability for REST API Transaction

1. Click the profile which you want to edit.
2. Edit the parameters which needs to be changed in Add Threshold and Availability screen.
3. Click Save.

Delete Threshold and Availability for REST API Transaction

1. Click the profile in the Threshold and Availability screen which needs to be deleted.
2. This will navigate to Add Threshold and Availability screen.
3. Click Delete.