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

Implement Custom Tenant Configuration for supported outputs

    XMLWordPrintable

Details

    • Custom Tenant Configuration
    • 8
    • False
    • None
    • False
    • Green
    • NEW
    • Administer, API, Release Notes
    • To Do
    • OBSDA-392 - Allow specifying custom index pattern in Cluster Log Forwarder
    • OBSDA-392Allow specifying custom index pattern in Cluster Log Forwarder
    • NEW
    • 100
    • 100% 100%
    • This enhancement introduces the capability for custom tenant configuration across all supported outputs, facilitating the organization of log records in a logical manner. However, it does not permit custom tenant configuration for Logging managed storage.
    • Enhancement

    Description

      Goals

      • Allow admins to spec the tenant for an output (e.g. Elasticsearch, Splunk, Loki, cloudwatch)

      Non-Goals

      • Allowing admins to spec the tenant for Logging managed storage (e.g. Elasticsearch, LokiStac

      Motivation

      The existing design restricts some customers ability to organize their log records in a way that is logical to them. This change would allow configuration to meet their requirements.

      Alternatives

      Acceptance Criteria

      • Verify the API allows the tenet to be set by the admin (e.g. Elasticsearch or splunk index)
      • Verify the admin is able to spec the tenant from a record's pod labels or namespace
      • Verify tenant specs for 'default' storage are rejected by the operator

      Risk and Assumptions

      Documentation Considerations

      • API changes
      • Explicit fields from which the tenant can be crafted
      • Tenant spec is disallowed for 'default' storage

      Open Questions

      Additional Notes

      Attachments

        Issue Links

          is documented by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OBSDOCS-825 [DOC] CLF Custom Tenant Configuration

          • 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.
          • To Do
          links to

          Web Link RHBA-2024:1591 Logging for Red Hat OpenShift - 5.9.0

          Activity

            People

              rh-ee-calee Calvin Lee
              jcantril@redhat.com Jeffrey Cantrill
              Qiaoling Tang Qiaoling Tang
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: