Threshold and Availability for Exchange Server Monitor

Once the Exchange 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 for
  • Mailbox
  • Client Access
  • Unified Messaging
  • Hub Transport and Edge Transport
• Advanced settings (Strategy)
• Edit a threshold profile
• Delete a threshold profile

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 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 Exchange Server from the drop-down.
   • Display Name: Provide a label for identification purposes. 
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.
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.
   
   
   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. The threshold and availability profile created for the Exchange server monitor will be automatically listed in the Threshold and Availability screen along with the others already created.

List of Metrics Supported

• General Thresholds:
  • IO DB Writes: Get alert severity status as Trouble or Critical when the IO database writes meets the condition set for the specified count.
  • IO DB Reads: Get alert severity status as Trouble or Critical when the IO database reads meets the condition set for the specified count.
  • RPC Response time to Unified Messaging: Get alerted with status as Trouble or Critical when response time from Mailbox to Unified Messaging meets the condition specified for the set value. 
  • RPC Response time to Hub Transport: Get alerted as Trouble or Critical when the response time from Mailbox to Hub Transport meets the condition specified for the set value. 
  • Information store RPC Response time: Get notified as Trouble or Critical when the information store RPC response time meets the condition specified for the set value.
  • Information Store Mailbox average delivery time: Get notified as Trouble or Critical when the information store mailbox average delivery time meets the condition specified for the set value. Also get severity status as Trouble or Critical according to your configuration.
• ClientAccess Thresholds:
  • OWA response time: Get alert severity status as Trouble or Critical when OWA response time meets the condition specified for the set value.
  • Active sync response time: Get alerted as Trouble or Critical when the response time meets the condition specified for the configured value. 
  • OWA requests: Get alert severity status as Trouble or Critical when OWA request meets the condition specified for the set value.
  • Active sync OWA requests: Get notified as Trouble or Critical when Active sync requests meets the condition specified for the configured value.
  • OWA Messages sent: Get notified as Trouble or Critical when OWA sent messages meets the condition specified for the set value. 
  • Active sync busy threads: Receive alert status as Trouble or Critical when active sync busy threads meets the condition specified for the configured value.
• Unified Messaging Thresholds:
  • Current Calls: Receive severity status as Trouble or Critical when current calls meets the condition specified for the set value.
  • Mailbox access failure: Get notified as Trouble or Critical when the mailbox access failure count meets the condition specified for the configured set. 
  • Hub Transport access failure: Get notified as Trouble or Critical when the hub transport access failure count meets the condition specified for the set value.
  • Directory access failure: Receive severity status as Trouble or Critical when directory access failure value meets the condition specified for the set value.
  • User response latency: Get alerted as Trouble or Critical when user response latency count meets the condition specified for the set value.
  • Call duration: Get alert severity status as either down or trouble when call duration meets the condition specified for the specified count.
  • Subscriber authentication failure: Get alert severity status as Trouble or Critical when subscriber authentication failure count meets the condition specified. 
• HubTransport and EdgeTransport Thresholds:
  • Hub SMTP Inbound/Outbound: Get alert severity status as Trouble or Critical when the Hub SMTP Inbound/Outbound count meets the condition set for the specified count
  • Hub messages sent/received: Get alert severity status as Trouble or Critical when Hub messages sent/received meets the condition specified for the set value.
  • Edge SMTP Inbound/Outbound: Get notified as Trouble or Critical when Edge SMTP inbound/outbound count meets the condition specified for the set value.
  • Edge messages sent/received: Receive alert status as Trouble or Critical when Edge messages sent/received meets the condition specified for the configured value. 
  • Message routing failed/succeeded: Get alert status as Trouble or Critical when the total number of messages failed to be/successfully routed meets the condition specified.

Edit 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 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.

Related Articles

• Add an Exchange server
• Performance metrics for Exchange server monitoring
• Add a Windows monitor
• Get started with our IT Automation tool
• Server monitoring architecture
• Configuration Profiles
• Other OS platforms supported