Proposed title of this feature request

• Elasticsearch index name should be customised to include static and dynamic data from the structured logs to follow customer indices names on external Elasticsearch instances.
• Especific Customer requirement index name pattern:  project.<namespace>.<date>
  • "project" and dots are static text content.
  • namespace like in kubernetes.namespace_name
  • date only considering day, month and year data from the log entry.

What is the nature and description of the request?

• Customer using an external Elasticsearch instance.
• Customer organizes very large amount of log indices following such standard not only limited to OpenShift clusters.
• Current customer is operating a custom fluentd configuration with operator status on Unmanaged stated for more than one year.
• Customer is migrating to the new stack (Vector).
• Latest CLO 5.9 Tenant configuration is limited to structuredTypeKey and structuredTypeName fallback.

Why does the customer need this? (List the business requirements)

• To follow their own standard for a large fleet of clusters.
  • 20 clusters
  • 1340 nodes
  • 23312 cores
  • 77155 G memory

List any affected packages or components.

• CLO , ClusterLogForwarder API.