Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-1141

Option for monitoring Vector's per-component memory usage

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • Logging 6.0, Logging 6.1, Logging 6.2, Logging 6.3, Logging 6.4
    • PM Logging
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 0

      Proposed title of this feature request

      Option for monitoring Vector's per-component memory usage

      What is the nature and description of the request?

      It's requested an option in the ClusterLogForwarder API for being able to analyze the Vector's per component memory usage in "managementState: Managed".

      Why does the customer need this? (List the business requirements)

      In cases where observed Vector using high Vector memory usage, it's needed to understand in what Vector's component the memory is used and the memory allocated is deallocated or not released.

      List any affected packages or components.
      Cluster Logging Operator
      Vector

              jamparke@redhat.com Jamie Parker
              rhn-support-ocasalsa Oscar Casal Sanchez
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: