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

Customizations for node-exporter collectors (Phase 2)

    XMLWordPrintable

Details

    • Customizations for Node-Exporter collectors (Phase 2)
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • MON-3154CMO user customizations
    • NEW
    • 100
    • 100% 100%
    • 0

    Description

      Epic Description

      This is the second part of Customizations for Node Exporter, following https://issues.redhat.com/browse/MON-2848
      There are the following tasks remaining:

      • On/off switch for these collectors:
        • systemd
        • hwmon
        • mountstats (pending decision which metrics to collect)
        • ksmd
      • General options for node-exporter
        • maxprocs

       

      The "mountstats" collector generates 53 high-cardinality metrics by default, we have to refine the story to choose only the necessary metrics to collect.

       

      Cluster Monitoring Operator uses the configmap "cluster-monitoring-config" in the namespace "openshift-monitoring" as its configuration. These new configurations will be added into the section  "nodeExporter".

      Node Exporter comes with a set of default activated collectors and optional collectors.

      To simplify the configuration, we put a config object for each collector that we allow users to activate or deactivate.

      If a collector is not present, no change is made to its default on/off status. 

      Each collector has a field "enabled" as a on/off switch. If "enabled" is set to "false", other fields can be omitted.

      The default value for the new options are:

      • collectors
        • systemd
          • enabled: bool, default: false
        • hwmon
          • enabled: bool, default: true
        • mountstats
          • enabled: bool, default: false
        • ksmd
          • enabled: bool, default: false
      • maxProcs: int, default: 0

      Here is an example of what these options look like in CMO configmap:

      apiVersion: v1
kind: ConfigMap
metadata: 
  name: cluster-monitoring-config
  namespace: openshift-monitoring
data: 

  config.yaml: |
    maxProcs: 4 
    nodeExporter: 
      collectors: 
        hwmon: 
          enabled: true
        mountstats: 
          enabled: true
        systemd: 
          enabled: true
        ksmd: 
          enabled: true

       

      If the config for nodeExporter is omitted, Node Exporter should run with the same arguments concerning collectors as those in CMO v4.12:

       
--no-collector.wifi
--collector.filesystem.mount-points-exclude=^/(dev|proc|sys|run/k3s/containerd/.+|var/lib/docker/.+|var/lib/kubelet/pods/.+)($|/)
--collector.netclass.ignored-devices=^(veth.*|[a-f0-9]{15}|enP.*|ovn-k8s-mp[0-9]*|br-ex|br-int|br-ext|br[0-9]*|tun[0-9]*)$
--collector.netdev.device-exclude=^(veth.*|[a-f0-9]{15}|enP.*|ovn-k8s-mp[0-9]*|br-ex|br-int|br-ext|br[0-9]*|tun[0-9]*)$
--collector.cpu.info
--collector.textfile.directory=/var/node_exporter/textfile
--no-collector.cpufreq
--no-collector.tcpstat
--no-collector.cpufreq
--no-collector.tcpstat
--collector.netdev
--collector.netclass
--no-collector.buddyinfo
--collector.netdev
--collector.netclass
--no-collector.buddyinfo

       

       

       

      Attachments

        Issue Links

          depends on

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MON-2848 Customizations for node-exporter collectors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MON-2904 On/Off switch of buddyinfo Collector in Node Exporter

          • Undefined - Priority not specified.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MON-2903 On/Off switch of systemd Collector in Node Exporter

          • Undefined - Priority not specified.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MON-2905 On/Off switch of ntp Collector in Node Exporter

          • Undefined - Priority not specified.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MON-2906 On/Off switch of hwmon Collector in Node Exporter

          • Undefined - Priority not specified.
          • Closed
          incorporates

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-293 Adding mountstats collector in Node exporter

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-214 OpenShift node-exporter for systemd

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is depended on by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CNV-27076 Validate that node-exporter ksm metrics are available in OCP

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MON-3235 Enable the processes_linux collector in node_exporter/cluster-monitoring-operator

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Release Pending

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MON-2895 add option to activate netlink backend in netclass collector in Node Exporter settings in CMO

          • Undefined - Priority not specified.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MON-2640 Investigate potential solutions for BZ 2097620

          • Undefined - Priority not specified.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-209 Customizations for node-exporter collectors

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users RFE-2112 Need RHCOS Metrics Exposed for OCP Cluster Monitoring

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Rejected

          Feature Request - Feature requests from customers and/or users RFE-4708 Ability to customize also the diskstats collector of node-exporter

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Under Review

          Feature Request - Feature requests from customers and/or users RFE-3187 [RFE] Enable `cpufreq` module on node-exporter

          • Undefined - Priority not specified.
          • Accepted

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MON-2894 gomaxprocs setting of Node Exporter in CMO

          • Undefined - Priority not specified.
          • Closed
          links to

          GitHub openshift/openshift-docs#64732: OBSDOCS-310: Monitoring-4.14-RN-new-features

          Web Link tasks review

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: