Freigeben über

What is config churn?

  • Artikel

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    January 01, 2003
    @Jr -

    Mostly just bugs in MP's.... unfortunately. That said - in SCOM 2012, Config Churn is not nearly as much of a problem as it was in SCOM 2007 R2, due to the database driven distributed config. Not saying we shouldn't strive to do better with best practices on management packs, but at least the impact isn't crippling. For instance, if there was NO impact on SCOM, who would care about such things? :-)

    • Anonymous
      September 26, 2016
      DearGood article. My config file on ms got double in size suddenly. On normal MS the size was 37 MB now it is 68 MB and dedicated management servers the size was 138 mb now it is 840 MB almost 6x increase in size. We recently had oms deployed. Can config file size increased in such folds because of OMS
      • Anonymous
        September 26, 2016
        @Azfal - Config file size is not a huge concern... the only real negative of a big file, is if you have churn, you are increasing the time to calculate config, and increasing IOPS significantly on the volume that holds the config file. In SCOM 2012 and later - you can measure how reliable config generation is with the queries from: https://blogs.technet.microsoft.com/kevinholman/2014/06/26/the-case-of-the-dell-detailed-mp-beware-of-large-environments/SELECT * FROM cs.workitemWHERE WorkItemName like '%delta%'ORDER BY WorkItemRowId DESCSELECT * FROM cs.workitemWHERE WorkItemName like '%snap%'ORDER BY WorkItemRowId DESCI'd want to know how long each takes, if this changed since adding OMS, and how often they fail. The log only keeps two days in there by design.Does OMS cause a huge config file? I dont know - have not seen that..... every interesting and somewhat concerning if it does. :-)
        • Anonymous
          October 17, 2016
          The comment has been removed

  • Anonymous
    April 27, 2011
    These queries works only when we have DW database, is there any query to check noisy discoveries with Operationmanager DB ?

  • Anonymous
    December 16, 2013
    Pingback from #WorstPractice ??? Enabling config churn by discovering properties that are significantly dynamic | Oleg Kapustin's sandbox

  • Anonymous
    December 28, 2013
    Here’s a new Knowledge Base article we published today on SCOM 2007. This one talks about configuration

  • Anonymous
    December 28, 2013
    Pingback from How to detect and troubleshoot frequent configuration changes in Operations Manager 2007 - Safranka M??ty??s szakmai blogja - TechNetKlub

  • Anonymous
    December 28, 2013
    Here’s a new Knowledge Base article we published today on SCOM 2007. This one talks about configuration

  • Anonymous
    February 21, 2014
    The comment has been removed

  • Anonymous
    December 24, 2014
    Kevin, what is the 'churn effect' if I repeatedly import an MP that doesn't contain any discoveries or group changes? specifically, what if I wanted to edit the raw XML of my notifications.internal MP and re-import the updated version every night (all via powershell)?

  • Anonymous
    September 30, 2016
    My question is about Connectors, Kevin. If a customer has an inbound connector that pushes data changes frequently to SCOM (maybe using the sdk), we will end up in same churn, without even the config file getting large in this case. What to do then? For eg. VMM has a connector that pushes DO changes. So if a customer has huge management server with lots of clusters there will be frequent DO resulting in same issue.

  • Anonymous
    September 30, 2016
    My question is about Connectors, Kevin. If a customer has an inbound connector that pushes data changes frequently to SCOM (maybe using the sdk), we will end up in same churn, without even the config file getting large in this case. What to do then? For eg. VMM has a connector that pushes DO changes. So if a customer has huge management server with lots of clusters there will be frequent DO resulting in same issue. Could you help.

    • Anonymous
      October 03, 2016
      Connectors can certainly create class instances, and can update class properties. Therefore, if they are updating properties of classes on a very frequent basis, this can cause config churn.SCOM 2012 handles config churn much better than SCOM 2007R2 did, which is when this article was written. However, it still creates large IOPS on the environment, and burdens it unnecessarily. I have no experience with the VMM MP's and churn.