Hello,

Reading the Monitoring documentation Support considerations for monitoring. It's great to see how it's indicated what is not supported and what's not supported.

In the middle of that, it's said:

"Deploying user-defined workloads to openshift-, and kube- projects. These projects are reserved for Red Hat provided components and they should not be used for user-defined workloads."

Moving this to the Logging context, it would great to have added to another improvement for the documentation saying something similar. Why? Since a lot of customer are deploying in the openshift-logging namespace their own custom Elasticsearch, fluentd, syslog or whatever to forward the logs to them.

The previous is generating a lot of noise when we are supporting them and even, a lot of times, this is the main reason for the issue.

Adding to the previous, it would be great to have "what is not the OpenShift Logging is NOT and what the OpenShift Logging is" in the same way that it's done for the Monitoring.

It was created in the past another issue for adding what's not:

• High scale log collection system
• SIEM Compliant
• Historical/long term log retention storage
• Guaranteed log sink

In the documentation, some of these points are commented, but, all of them are dispersed. It should be at the beginning of the Logging documentation and crealy saying what's supported, what's not supported, what's logging and what's not logging.