Help Docs

Threshold and Availability for BizTalk Server

Once the BizTalk 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 BizTalk Server from the drop-down.
    • Display Name: Provide a name 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 BizTalk server monitor will be automatically listed in the Threshold and Availability screen.

List of Metrics Supported

  • Used Physical Memory: Get alerted as Trouble or Critical when the percentage of physical memory used on the machine meets the condition set for the configured value.
  • Database Transactions/sec: Get alerted as Trouble or Critical when the average number of database transaction per second meets the condition set for the configured value.
  • Idle Orchestrations: Get alerted as Trouble or Critical when the number of idle orchestrations meets the condition set for the configured value.
  • Message Box Database Connection Failures: Get alerted as Trouble or Critical when the number of concurrent message box database connection failures meets the condition set for the specified value.
  • Orchestrations Suspended/sec: Get alerted as Trouble or Critical when the number of orchestrations suspended per second meets the condition set for the configured value.
  • Pending Messages: Get alerted as Trouble or Critical when the number of messages pending from the orchestration engine meets the condition set for the configured value.
  • Orchestrations Discarded/secmeets the condition set for the: Get alerted as Trouble or Critical when the number of orchestrations discarded per second meets the condition set for the configured value.
  • Orchestrations Created/sec: Get alerted as Trouble or Critical when the number of orchestrations created per second meets the condition set for the configured value.
  • Running Orchestrations: Get alerted as Trouble or Critical when the number of active orchestrations meets the condition set for the configured value.
  • Active Instance Count: Get alerted as Trouble or Critical when the number of instances that are active in memory meets the condition set for the configured value.
  • Database Sessions Count: Get alerted as Trouble or Critical when the number of concurrent message box database connections being used meets the condition set for the configured value.
  • Database Size: Get alerted as Trouble or Critical when the capacity of the database in which the messages are published meets the condition set for the configured value.
  • Total Messages Delivered: Get alerted as Trouble or Critical when the number of messages delivered to the orchestration engine meets the condition set for the configured value.
  • Pending Receive Batches: Get alerted as Trouble or Critical when the number of pending batches that have not completed processing meets the condition set for the configured value.
  • Pending Transmitted Messages: Get alerted as Trouble or Critical when the number of pending batches from the messaging engine to be sent to the adapters meets the condition set for the configured value.
  • Throttled Receive Batches: Get alerted as Trouble or Critical when the number of pending batches that are blocked due to high service load by the messaging engine meets the condition set for the configured value.
  • Inbound Latency: Get alerted as Trouble or Critical when the average latency recorded from when the messaging engine receives the message from the adapter to the time it is published in the message box meets the condition set for the configured value.
  • Outbound Latency: Get alerted as Trouble or Critical when the average latency recorded from the time the messagin engine receives the message from the message box till it is sent by the adapter meets the condition set for the configured value.
  • File Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the file adapter per second meets the condition set for the configured value.
  • File Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the file adapter per second meets the condition set for the configured value.
  • FTP Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the FTP adapter per second meets the condition set for the configured value.
  • FTP Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the FTP adapter per second meets the condition set for the configured value.
  • HTTP Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the HTTP adapter per second meets the condition set for the configured value.
  • HTTP Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the HTTP adapter per second meets the condition set for the configured value.
  • MSMQ Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the MSMQ adapter per second meets the condition set for the configured value.
  • MSMQ Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the MSMQ adapter per second meets the condition set for the configured value.
  • Active Sessions: Get alerted as Trouble or Critical when the number of open POP3 connections manageable by the adapter at a time meets the condition set for the configured value.
  • POP3 Messages Received/sec: Get alerted as Trouble or Critical when the number of emails taken up by the POP3 adapter from the mail server per second meets the condition set for the configured value.
  • SMTP Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the SMTP adapter per second meets the condition set for the configured value.
  • SOAP Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the SOAP adapter per second meets the condition set for the specified value.
  • SOAP Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the SOAP adapter per second meets the condition set for the configured value.
  • Message Delivery Delay: Get alerted as Trouble or Critical when the delay occured on each message delivery batch (in ms) meets the condition set for the configured value.
  • SQL Messages Received/sec: Get alerted as Trouble or Critical when the number of messages received by the SQL adapter per second meets the condition set for the configured value.
  • SQL Messages Sent/sec: Get alerted as Trouble or Critical when the number of messages sent by the SQL adapter per second meets the condition set for the configured value.
  • Spool Size: Get alerted as Trouble or Critical when the size of the spool present on a particular message box on a particular server meets the condition set for the configured value.
  • Tracking Data Size: Get alerted as Trouble or Critical when the size of the tracking data table on the message box meets the condition set for the configured value.
  • Total Instances: Get alerted as Trouble or Critical when the total number of instances in memory meets the condition set for the configured value.
  • Suspended Messages Length: Get alerted as Trouble or Critical when the total number of messages suspended for the host meets the condition set for the configured value.
  • Host Queue Length: Get alerted as Trouble or Critical when the total number of messages in the host queue meets the condition set for the configured value.
  • Notify if host instance is disabled: Get notified as Trouble or Critical when the host instance is disabled.
  • Notify if receive location is disabled: Get notified as Trouble or Critical when the primary receive location for receiving the message content is disabled.

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

Related Articles

Was this document helpful?

Shortlink has been copied!