none
BizTalk Counters and SCOM RRS feed

  • Question

  • Hello all,

    If SCOM with BizTalk monitoring PACK is being used, do we still need to look into the individual counters or should we primarily rely on the SCOM rules and monitors?

    Thanks.

    Thursday, July 2, 2015 9:46 AM

Answers

  • Advantages of using both SCOM and BizTalk360 is explained very well in the white paper published by Kent Weare @ BizTalk Monitoring Solutions (SCOM vs BizTalk360) white paper by Kent Weare.

    I would like to highlight few limitations of SCOM for which you have to seek help of other tools if ever required.

    1)  There are no specific counters for Message publishing throttling state or Message delivery throttling states. These are the counters that are described in the very useful MSDN document. So in order to clearly detect a Throttling state you need SCOM and Performance Monitoring (PerfMon).

    2) There is no direct integration with Message Box Viewer. Through custom scripting desired results are probably achievable but this will be custom work in order to achieve this requirement.

    3) When an orchestration gets suspended for some reason, you will receive an alert. However when other orchestrations of the same type are getting suspended, and the previous instance has not been terminated/resumed yet, no new alert(s) will be fired.

    4) Reducing the number of alerts generated involves fine-tuning SCOM for BizTalk by manually selecting parameters to monitor, and then setting thresholds of behaviours. Here again, you’re going to need SCOM experts dedicated to this sizable task. And after all the hours of planning and decision-making, thresholds set by the SCOM team are ultimately static and potentially out-of-date as soon as a change is introduced into the BizTalk environment.

    SCOM is not a tool that is specific to BizTalk. It is an enterprise monitoring solution that allows you to monitor Microsoft and Non-Microsoft assets. I would recommend you BizTalk 360, the product itself was built to address some gaps that exist within the BizTalk Monitoring and Management space. 

    Rachit


    Please mark as answer or vote as helpful if my reply does


    Thursday, July 2, 2015 12:41 PM
    Moderator
  • Hi ,

    If you are working with BizTalk 2013 then you can  use BizTalk Server 2013 Monitoring  Management Pack along with SCOM.

    BizTalk Server 2013 Management Pack offers monitoring capabilities for BizTalk artifacts and BizTalk-related platform components. It allows administrators to monitor health state of various BizTalk artifacts such as Send Ports, Orchestrations etc. and platform artifacts such as Host Instances (BizTalk service). Further, this mp includes performance views, diagnostic capability and alerts.

    Feature Summary
    BizTalk Server 2013 MP includes the following enhancements:
      • Updated discovery to handle a large amount of BizTalk Server artifacts
      • Increased suppression on rules to show only the important messages
      • Fixed the issue with the discovery of the installed BizTalk Server version
      Supported Operating System

      Windows Server 2008 R2 SP1, Windows Server 2012

        • Required Software:
        • System Center Operations Manager 2007 R2 Or System Center Operations Manager 2012
        • Microsoft BizTalk Server 2013

    MSDN Reference Article : BizTalk Server 2013 Monitoring Management Pack 

    SCOM Does the core job of monitoring SQL Server instances very well (Health Monitoring) – but it is not going to make maintenance plans for you.

    Thanks

    Abhishek



    • Marked as answer by Angie Xu Tuesday, July 14, 2015 5:39 AM
    Friday, July 3, 2015 6:13 AM

All replies

  • Advantages of using both SCOM and BizTalk360 is explained very well in the white paper published by Kent Weare @ BizTalk Monitoring Solutions (SCOM vs BizTalk360) white paper by Kent Weare.

    I would like to highlight few limitations of SCOM for which you have to seek help of other tools if ever required.

    1)  There are no specific counters for Message publishing throttling state or Message delivery throttling states. These are the counters that are described in the very useful MSDN document. So in order to clearly detect a Throttling state you need SCOM and Performance Monitoring (PerfMon).

    2) There is no direct integration with Message Box Viewer. Through custom scripting desired results are probably achievable but this will be custom work in order to achieve this requirement.

    3) When an orchestration gets suspended for some reason, you will receive an alert. However when other orchestrations of the same type are getting suspended, and the previous instance has not been terminated/resumed yet, no new alert(s) will be fired.

    4) Reducing the number of alerts generated involves fine-tuning SCOM for BizTalk by manually selecting parameters to monitor, and then setting thresholds of behaviours. Here again, you’re going to need SCOM experts dedicated to this sizable task. And after all the hours of planning and decision-making, thresholds set by the SCOM team are ultimately static and potentially out-of-date as soon as a change is introduced into the BizTalk environment.

    SCOM is not a tool that is specific to BizTalk. It is an enterprise monitoring solution that allows you to monitor Microsoft and Non-Microsoft assets. I would recommend you BizTalk 360, the product itself was built to address some gaps that exist within the BizTalk Monitoring and Management space. 

    Rachit


    Please mark as answer or vote as helpful if my reply does


    Thursday, July 2, 2015 12:41 PM
    Moderator
  • Hi ,

    If you are working with BizTalk 2013 then you can  use BizTalk Server 2013 Monitoring  Management Pack along with SCOM.

    BizTalk Server 2013 Management Pack offers monitoring capabilities for BizTalk artifacts and BizTalk-related platform components. It allows administrators to monitor health state of various BizTalk artifacts such as Send Ports, Orchestrations etc. and platform artifacts such as Host Instances (BizTalk service). Further, this mp includes performance views, diagnostic capability and alerts.

    Feature Summary
    BizTalk Server 2013 MP includes the following enhancements:
      • Updated discovery to handle a large amount of BizTalk Server artifacts
      • Increased suppression on rules to show only the important messages
      • Fixed the issue with the discovery of the installed BizTalk Server version
      Supported Operating System

      Windows Server 2008 R2 SP1, Windows Server 2012

        • Required Software:
        • System Center Operations Manager 2007 R2 Or System Center Operations Manager 2012
        • Microsoft BizTalk Server 2013

    MSDN Reference Article : BizTalk Server 2013 Monitoring Management Pack 

    SCOM Does the core job of monitoring SQL Server instances very well (Health Monitoring) – but it is not going to make maintenance plans for you.

    Thanks

    Abhishek



    • Marked as answer by Angie Xu Tuesday, July 14, 2015 5:39 AM
    Friday, July 3, 2015 6:13 AM
  • AIMS will provide you with the most counters including perf counters for all orchs and ports. It can provide all these details without BAM or tracking enabled and has the lowest footprint available.

    If you have 1-2 BizTalk servers in a group you can use our free version, you can sign up here http://www.aimsinnovation.com/aims-free

    For more details see www.aimsinnovation.com

    Thanks,

    Marius

    Wednesday, April 12, 2017 2:37 PM
  • If you have 1-2 BizTalk servers in a group you can use our free version, you can sign up here http://www.aimsinnovation.com/aims-free

    Hi Marius, maybe slow down a bit. These are about to cross the Advertising/Spam line. Thanks!
    Wednesday, April 12, 2017 3:06 PM
    Moderator
  • Sure will slow down....but since people have issues that AIMS cover and for free, and seems like there are just two monitoring tools mentioned in this forum, why not help by introducing more options that can solve a problem in a better way?

    360 and SCOM are not the only two options, even if marked as answer. Guess people should know their options?


    Wednesday, April 12, 2017 8:41 PM