Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-566

[Tech Debt] [Diagnostics] HAProxy Troubleshooting Enhancements

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • [Diagnostics] HAProxy Troubleshooting Enhancements
    • Proactive Architecture
    • False
    • False
    • To Do
    • OCPPLAN-7878 - NetEdge - Maintainability and Debugability & Tech Backlog
    • OCPPLAN-7878NetEdge - Maintainability and Debugability & Tech Backlog
    • Undefined
    • 0
    • 0

      HAProxy has many nuances, and troubleshooting issues with the current logging and must-gather records can be difficult.

      Prioritize the following list and decide which to add to must-gather or other side-car logging for HAProxy:

      1. HAProxy directory contents
      2. number of HAProxy processes (pid count)
      3. CPU, memory, buffer, and other resource requests/limits
      4. netstats
      5. established connections
      6. pertinent Prometheus metrics

       

            Unassigned Unassigned
            cholman@redhat.com Candace Holman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: