none
Performance Monitoring Tools for BizTalk 2010

    Question

  • Dear All,

    What default tools are available for performance monitoring for BizTalk 2010.

    I have 100 apllications / host running in BiztTalk 2010 and I need to find the maximum thorughput for all 100 host. So how do I find the thoroughput for all the 100 host. 

    Regards,

    Bhavin

    Sunday, November 27, 2016 10:28 AM

Answers

  • Hi,

    A good place to start to monitor performance are performance counters. BizTalk provides performance counters to monitor the individual components like hosts, message box, orchestration, adapters, …

    A very interesting set of counters are the Host Throttling Performance Counters. These counters not only provide information about message throughput but also provide indicators when high-water marks are reached. Check out High Message Delivery Rate, High Database Size, High Thread Count or High Process Memory. These counters should always return 0 (zero). In case a high-water mark is reached the counter flips to 1 alerting you that the Host Instance is experiencing throughput problems.

    The two counters Message Delivery Incoming Rate and Message Deliver Outgoing Rate tell you how many messages have been passed to the Orchestration or Messaging System and how many of them have actually been processed. There are two similar counters – Message Publishing Incoming Rate and Message Publishing Outgoing Rate – which indicate how many messages have been put to the MessageBox database and how many have been pulled out. In an ideal world the incoming and outgoing numbers should match. If you see a gap you know that either the Orchestration Engine, the Message Engine or the MessageBox cannot handle the number of incoming messages.

    Refer: Monitoring BizTalk Performance Counters for throttling and MICROSOFT BIZTALK SERVER 2010 HOST THROTTLING PERFORMANCE COUNTERS

    You can use your own windows performance counter monitoring tool, System Center Operations Manager (SCOM) or just go with Windows Performance Monitoring tool that comes with every windows installation.

    Few best practices as rightly highlighted at http://btsguru.blogspot.in/2011/07/post-by-marcel-determining-optimum.html

    Best practices
    Make your plan on how to separate hosts beforehand and how to name them. It is not possible to rename hosts.

    Create separate hosts for different functions.

    · Receiving
    · Sending
    · Processing
    · Tracking

    Add hosts for protocol or application specific requirements.

    · Prioritization
    · Batching vs. messaging
    · Low latency
    · Protocols that require clustering
    · Protocols that require scale-out
    · Separate hosts for applications with known or expects problems
    When problematic applications are in a separate host, crashes will not affect applications in other hosts.
    · Licensing of adapters
    Certain 3rd party adapters are licensed separate from BizTalk Server. Separating per host can be a cost-effective deployment scheme.
     

    Rachit Sikroria (Microsoft Azure MVP)

    Sunday, November 27, 2016 1:59 PM
    Moderator
  • Hi Bhavin,

    BizTalk 2013 ships with BizTalk Health Monitor which can be used for monitoring health of BizTalk, but it can be downloaded separately and install it for BizTalk 2010 -How to install BizTalk Health Monitor v3.2 

    

    See if you need to add more counters then click on plus sign and add counters to it.

    And if not comfortable with BHM then as Rachit suggested, you can use PerfMon  -- How to setup and schedule BizTalk performance Counters in PerfMon

    --------

    Maheshkumar S Tiwari|User Page|Blog|How to get Retry Count of Successful sent attempt - One way Scenario

    • Marked as answer by bhavin07 Monday, November 28, 2016 3:10 AM
    Sunday, November 27, 2016 3:04 PM

All replies

  • Hi,

    A good place to start to monitor performance are performance counters. BizTalk provides performance counters to monitor the individual components like hosts, message box, orchestration, adapters, …

    A very interesting set of counters are the Host Throttling Performance Counters. These counters not only provide information about message throughput but also provide indicators when high-water marks are reached. Check out High Message Delivery Rate, High Database Size, High Thread Count or High Process Memory. These counters should always return 0 (zero). In case a high-water mark is reached the counter flips to 1 alerting you that the Host Instance is experiencing throughput problems.

    The two counters Message Delivery Incoming Rate and Message Deliver Outgoing Rate tell you how many messages have been passed to the Orchestration or Messaging System and how many of them have actually been processed. There are two similar counters – Message Publishing Incoming Rate and Message Publishing Outgoing Rate – which indicate how many messages have been put to the MessageBox database and how many have been pulled out. In an ideal world the incoming and outgoing numbers should match. If you see a gap you know that either the Orchestration Engine, the Message Engine or the MessageBox cannot handle the number of incoming messages.

    Refer: Monitoring BizTalk Performance Counters for throttling and MICROSOFT BIZTALK SERVER 2010 HOST THROTTLING PERFORMANCE COUNTERS

    You can use your own windows performance counter monitoring tool, System Center Operations Manager (SCOM) or just go with Windows Performance Monitoring tool that comes with every windows installation.

    Few best practices as rightly highlighted at http://btsguru.blogspot.in/2011/07/post-by-marcel-determining-optimum.html

    Best practices
    Make your plan on how to separate hosts beforehand and how to name them. It is not possible to rename hosts.

    Create separate hosts for different functions.

    · Receiving
    · Sending
    · Processing
    · Tracking

    Add hosts for protocol or application specific requirements.

    · Prioritization
    · Batching vs. messaging
    · Low latency
    · Protocols that require clustering
    · Protocols that require scale-out
    · Separate hosts for applications with known or expects problems
    When problematic applications are in a separate host, crashes will not affect applications in other hosts.
    · Licensing of adapters
    Certain 3rd party adapters are licensed separate from BizTalk Server. Separating per host can be a cost-effective deployment scheme.
     

    Rachit Sikroria (Microsoft Azure MVP)

    Sunday, November 27, 2016 1:59 PM
    Moderator
  • Hi Bhavin,

    BizTalk 2013 ships with BizTalk Health Monitor which can be used for monitoring health of BizTalk, but it can be downloaded separately and install it for BizTalk 2010 -How to install BizTalk Health Monitor v3.2 

    

    See if you need to add more counters then click on plus sign and add counters to it.

    And if not comfortable with BHM then as Rachit suggested, you can use PerfMon  -- How to setup and schedule BizTalk performance Counters in PerfMon

    --------

    Maheshkumar S Tiwari|User Page|Blog|How to get Retry Count of Successful sent attempt - One way Scenario

    • Marked as answer by bhavin07 Monday, November 28, 2016 3:10 AM
    Sunday, November 27, 2016 3:04 PM
  • Just for recommendation : Having 100 hosts in ur env ?? This is not a good idea as such.. Having a lot of hosts is detrimental for ur farm. Ur host separation is not in the best way if u have 100 apps and 100 hosts. You should definitely look to streamline this.

    Pi_xel_xar

    Blog: My Blog

    BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/

    Monday, November 28, 2016 6:13 AM
    Answerer