What are you experiencing? What are you expecting to happen?
log_es_400_reason parameter added would be very helpful. Sometimes clients request support because they don't have logs in ElasticSearch. We have to debug Logging Operator and client applications which is not that easy. Putting Logging Operator in Unmanaged state and modifying the ConfigMap is inconvenient. log_es_400_reason is really helpful.

Define the value or impact to you or the business
Easier debugging of clients' applications, easier life for cluster admins

CU direct comment:
To understand our request better - we are using FluentD for internal logging in OCPv4 but logs are forwarded then to our central ElasticSearch system, that's why changing ES to Loki doesn't affect our team. We are using default configuration of RHOL (with custom ClusterLogForwarder, of course). As far as I see OCP in version 4.12.31 is still using RHOL with FluentD, so I would be grateful for creating RFE. If it's not possible or it's very hard to perform that change, I would like to know.