-
Epic
-
Resolution: Done-Errata
-
Major
-
None
-
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
-
-
NEW
-
0% To Do, 0% In Progress, 100% Done
-
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
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
- is documented by
-
-
- To Do
-
- links to
-
RHBA-2024:1591
Logging for Red Hat OpenShift - 5.9.0
There are no Sub-Tasks for this issue.