Help Docs

Threshold and Availability for IIS Server

Once the IIS server monitor is successfully added to your Site24x7 account, add a threshold and availability profile to help the alarms engine decide if a specific resource has to be declared critical or down. Configure downtime rules to reduce false alerts.

While setting up a threshold profile, you can also map automation(s) to desired attribute(s). Once the threshold is breached, the corrective automation will be executed and the issue can be fixed without manual intervention. You can map upto five corrective automations per attribute.

Add a Threshold Profile

  1. Log in to Site24x7.
  2. Go to Admin > Configuration Profiles > Threshold and Availability > Add Threshold Profile. You can also navigate via Server > Server Monitor > Servers > click on the server monitor > hover on the hamburger icon beside the display name > Edit > Configuration Profiles > pencil icon beside Threshold and Availability.
  3. Specify the following details:
    • Monitor Type: Select Microsoft IIS Server from the drop-down.
    • Display Name: Specify an appropriate name for the threshold and availability profile.
  4. Threshold Type: You can choose between Static and AI-based thresholds. Refer the below section for the entire list of metrics for which thresholds can be set.
    • Static Thresholds: From the drop-down menu, choose the desired metrics for which thresholds need to be configured. Enter a value specific to the unit, and set the threshold conditions (<, <=, =, >, or >=) and the monitor state (to be notified as) for each metric. You'll receive alerts when these threshold conditions are violated.
    • AI-based Thresholds: The AI-based threshold will track the abnormal spikes using anomaly detection and will offer a dynamic threshold which will be updated accordingly. If you're choosing AI-based threshold, choose associated anomaly severity and the status accordingly. This is supported for the metric Network Traffic.
  5. 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.

  6. Save the profile. This will be automatically listed in the Threshold and Availability screen along with the others already created.

List of Metrics Supported

  • Notify when Site is Down: Get notified as Down, Trouble, or Critical when the site is down. By default, it is set as Yes.
  • Notify when Application Pool is Down: Get notified as Down, Trouble, or Critical when the application pool is down. By default, it is set as Yes.
  • Network Traffic: Get alerted as Trouble or Critical when the total rate of bytes transferred exceed the configured value.
  • Current Requests: Get alerted as Trouble or Crtitical when the number of current requests exceed the configured value. 

Edit a Threshold and Availability Profile

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

Delete a Threshold and Availability Profile

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


Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!