Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1165

Top 10 log producing containers chart

    XMLWordPrintable

Details

    • 2
    • False
    • False
    • NEW
    • NEW
    • Undefined
    • Logging (Core) - Sprint 198, Logging (Core) - Sprint 199

    Description

      Story

      As an administrator to cluster logging,
      I want a chart that displays the top 10 containers producing the most logs
      so that I can understand who are the most chatty.

      Acceptance Criteria

      • Add a new chart to the existing "Openshift Logging" dashboard that shows the top 10 containers producing logs.
      • The chart displays the podname and namespace associated with each metric

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. LOG-1271 Logs Produced Line Chart does not display podname and namespace labels

          • 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 cloned by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-1269 Top 10 logs collected containers chart

          • 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. LOG-1166 Collection log loss chart

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is documented by

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-2913 Top 10 containers chart and log loss - what to do?

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. LOG-1353 No datapoints found on top 10 containers dashboard

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

          Web Link Existing Dashboard

          GitHub openshift/cluster-logging-operator#954: Adding container chart LOG-1165-Dashboard

          GitHub openshift/cluster-logging-operator#1009: Reverting dashboard changes from earlier PR(JIRA ticket LOG-1320)

          Activity

            People

              aguptaredhat Ajay Gupta (Inactive)
              jcantril@redhat.com Jeffrey Cantrill
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: