Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-705

Limit the number of logs kept in Elastic index

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      This feature ensures that we can plan for a reasonable level of resources for the logging infrastructure

      Show
      This feature ensures that we can plan for a reasonable level of resources for the logging infrastructure
    • Hide

      The log count should not grow indefinitely, but be capped at a configured amount.

      Show
      The log count should not grow indefinitely, but be capped at a configured amount.
    • 1
    • 1
    • 2
    • Team_KAROO
    • Sprint 5
    • 6.6

    • PI24 - UNCOVERED

    • Team_KAROO goal_O3

    Description

      To keep the resources consumed by the logging infrastructure (fluentd, logstash, elastic, kibana) as low as possible, we need to limit the number of logs that are kept.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-25 Implement standardised approach to logging for the OMC and DP MVPs

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          Capability - SAFe program capability SS-26 Continue implementation of standardised approach to logging for the OMC and DP MVPs

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          is triggered by

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-15 Harmonize approach to logging.

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Done
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                p.swart Swart, Paul [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete34.0
                  Total34.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel