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

Implement delete by query as part of index management

    XMLWordPrintable

Details

    • 3
    • False
    • False
    • NEW
    • OBSDA-123 - cluster logging - delete ES logs by PVC usage threshold
    • VERIFIED
    • Undefined
    • Logging (LogExp) - Sprint 210, Logging (LogExp) - Sprint 206, Logging (LogExp) - Sprint 207, Logging (LogExp) - Sprint 208, Logging (LogExp) - Sprint 209, Logging (LogExp) - Sprint 211

    Description

      As a follow up from https://issues.redhat.com/browse/LOG-1326, we want to implement delete by query as part of index management script.

      Acceptance Criteria:

      • Ensure that the API changes are not breaking the current flow.
      • Ensure that the user is able to specify the namespaces and minAge for performing delete by query.
      • Ensure that the index management script is able to perform delete by query correctly.
      • Ensure that CLO is able to consume the API changes for delete by query.
      • Write possible test cases to check that delete by query is working correctly.

      Dev Notes:

      Attachments

        Issue Links

          account is impacted by

          Task - Represents a small unit of work that is not end-user facing. LOG-1757 Implemnet merge indices as part of Index Management

          • 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
          causes

          Bug - A problem that impairs or prevents the functions of the product. LOG-2210 Delete by query doesn't delete all the projects' logs defined in retentionPolicy

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

          Bug - A problem that impairs or prevents the functions of the product. LOG-2216 Delete by query doesn't delete all the projects' logs defined in retentionPolicy

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

          Bug - A problem that impairs or prevents the functions of the product. LOG-2120 EO becomes CrashLoopBackOff when deploy ES with more than 3 nodes

          • Undefined - Priority not specified.
          • Closed
          is related to

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-324 Data cleanup and retention for logging

          • 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
          links to

          GitHub openshift/elasticsearch-operator#797: Add delete by query to index management

          Activity

            People

              btaani@redhat.com Bayan Taani
              sasagarw@redhat.com Sashank Agarwal (Inactive)
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: