Description of problem: Currently, its possible to keep aggregate logging from collecting logs for a particular project by editing the fluentd configmap with something like: <match pattern> @type null </match> However, this requires the user has access to the logging project. It would be useful if users could disable aggregate logging on a per-project basis, perhaps using a label. There have been instances where a customer's application is producing a very high volume of logs that quickly fills the elastic search pod's persistent volume. If users had the ability to "mute" logging for projects they don't want to collect, it would make it easier for them to control how much space their logs consume. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Closing in favor of https://jira.coreos.com/browse/LOG-254. This is a topic to be investigated during the logging 2019 hackfest