Compartilhar via

OpsMgr – Authoring performance collection rules for cluster disks – the *right* way.

  • Artigo

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    January 01, 2003
    But look at all the cool stuff you just learned?  :-)

  • Anonymous
    January 01, 2003
    @Trond - GREAT question - I don't know - but I will look into this.

  • Anonymous
    January 01, 2003
    @RHC - Have you enabled our mount point discovery? We will discover and monitor mount points via that method.  However - I do know that our typical perfmon targets don't work - and this shows up in events on the SCOM agent because the workflow is trying to map the discover ID to something in perfmon - and these don't match.  Perfmon shows these as "HardDiskVolume1", etc.... so I'd argue that we need to change the mount point discovery to allow logical disk counters in perfmon to map correctly to these, or find some other way to monitor free space and collect perf data for mount points.  This sounds like a good bug to raise in support and request a hotfix for the MP.  Raising a bug and escalating for a fix is the BEST way to see changes made to any MP.  Without that request being made by the customer, it wont be seen as an impacting issue.

    • Anonymous
      March 23, 2017
      Hi Kevin.I have written a MP to overcome the limitations regarding mountpoints. I would really appreciate your feedback. Especially I would like to get your feedback regarding cookdown. I tried to implement the rules that cookdown should take place.MP can be downloaded here: https://gallery.technet.microsoft.com/SCOM-Management-Pack-for-0afa5515Best regardsAndreas

  • Anonymous
    January 01, 2003
    I have raised it as a recommendation.  :-) When I say "known issue" I mean it is known by me.

  • Anonymous
    January 01, 2003
    Good One.

  • Anonymous
    September 30, 2012
    Can you try and get this into the next release of the official OS MP so we don't have to do our own custom workarounds for a known issue?

  • Anonymous
    October 02, 2012
    The comment has been removed

  • Anonymous
    November 03, 2012
    Hi Kevin Again a greate post from you! – thank you! I followed you article and start collecting a lot of performance data from the cluster disk, but I have one problem – How to I collect performance data from mount points we are using in a cluster? We have a lot of big SQL clusters where each cluster resource/SQL instance is buildup of a “anchor disk” with a driver letter and then a lot of mount points on this disk – In this situation I only get performance data from the “anchor disk” that have a drive letter and not from all the mount points – do you have an ide how to solve this?

  • Anonymous
    November 13, 2012
    Hi Kevin Yes we have enabled moint point discovery. I will raise it for MS support - thank you a lot for you answer.

  • Anonymous
    September 12, 2013
    Hello, Does a list of all counters already available exist? Should I add all counters in the custom MP attached?

  • Avg. Disk sec/Read
  • Avg. Disk sec/Write
  • I/O Database Reads/Sec
  • I/O Database Reads Average Latency
  • I/O Database Writes/Sec
  • I/O Database Writes Latency for SQL databases (SQL MP), I saw these counters in the Exchange MP... Thanks, Dom
  • Anonymous
    August 25, 2015
    Hello Kevin -
    Does this require time to discover cluster disk which I made the rule enabled? If so, how many hours? Thanks!
  • Anonymous
    August 25, 2015
    @nhlad - this has nothing to do with cluster disk discovery. This has to do with performance collection.

    Your cluster disks should already be discovered instances. If they aren't - you need to make sure you have the right MP's installed and troubleshoot.