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

Investigate potential solutions for BZ 2097620

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Undefined
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • NEW
    • NEW
    • Sprint 221, Sprint 224, MON Sprint 225, MON Sprint 226, MON Sprint 227, MON Sprint 228, MON Sprint 229, MON Sprint 231, MON Sprint 232
    • 0

    Description

      One customer reported excessive CPU usage for node_exporter in BZ 2097620 [1]. They use SR-IOV network interfaces which may explain that node_exporter spends lots of CPU cycles in collecting network interface metrics.

      AC

      • Suggestions to remediate the issue.

      [1] https://bugzilla.redhat.com/show_bug.cgi?id=2097620

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1649 Node Exporter Need Updates on collector.netclass.ignored-devices

          • 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
          relates 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-2814 Customizations for node-exporter collectors (Phase 2)

          • 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

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1321 node_exporter collects metrics for "virtual" network interfaces

          • 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

          Activity

            People

              hasun@redhat.com Haoyu Sun
              spasquie@redhat.com Simon Pasquier
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: