Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-640

Add node-role.kubernetes.io and topology.kubernetes.io/zone to OpenShift - Node related alerts

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • Add node-role.kubernetes.io and topology.kubernetes.io/zone to OpenShift - Node related alerts
    • False
    • False
    • To Do
    • OCPSTRAT-354 - Sig-Node upstream
    • OCPSTRAT-354Sig-Node upstream
    • 100
    • 100% 100%
    • Undefined

      1. Proposed title of this feature request
      Add node-role.kubernetes.io and topology.kubernetes.io/zone to OpenShift - Node related alerts

      2. What is the nature and description of the request?
      OpenShift - Node specific alert currently just contain the Node name but no information about the Node role or Availability Zone. To improve monitoring and help understand what component might be affected, it's required to add node-role.kubernetes.io and topology.kubernetes.io/zone to the OpenShift - Node specific alerts. That way, it's easy to see if the problem is specific to workerinfra or master nodes respectively to a Availability Zone.

      3. Why does the customer need this? (List the business requirements here)
      In Cloud environments, with automatic scaling of OpenShift - Node, it's rather difficult to understand if an alert if firing how critical it is. While every alert needs to be taken serious, it's hard to understand what alert to tackle first if for example filesystem full alert is firing. Certainly not good if affecting a worker but even worse if it's affected a master. Thus if these information are included in the Alert, it would be much easier to understand what issue to tackle first and also better understand if something in a specific region/zone is broken or not.

      4. List any affected packages or components.
      OpenShift - Monitoring

        1.
        Docs Tracker Sub-task Closed Undefined Unassigned
        2.
        QE Tracker Sub-task Closed Undefined Unassigned
        3.
        TE Tracker Sub-task Closed Undefined Derrick Ornelas

            rphillip@redhat.com Ryan Phillips
            gausingh@redhat.com Gaurav Singh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: