Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-2894

gomaxprocs setting of Node Exporter in CMO

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • openshift-4.14
    • None
    • None
    • None
    • 0
    • MON Sprint 234
    • 0

    Description

      Node Exporter has been upgraded to 1.5.0.
      The default value of argument `--runtime.gomaxprocs` is set to 1, different from the old behavior. Node Exporter used to take advantage of multiple processes to accelerate metrics collection.
      We are going to add a parameter to set the argument `--runtime.gomaxprocs` and make its default value 0. So that CMO retains the old behavior while allowing users to tune the multiprocess settings of Node Exporter.

      The CMO config will have a new section `nodeExporter`, under which there is the parameter `maxProcs`, accepting an integer number as the maximum number of process Node Exporter runs concurrently. Its default value is 0 if omitted.

       config.yaml: |
      
          nodeExporter: 
            maxProcs: 1
      

      Attachments

        Activity

          People

            hasun@redhat.com Haoyu Sun
            hasun@redhat.com Haoyu Sun
            Tai Gao Tai Gao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: