Bug 1465706 - Allow users to disable aggregate logging per project
Allow users to disable aggregate logging per project
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.4.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Paul Weil
Xiaoli Tian
: OpsBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-27 20:24 EDT by bmorriso
Modified: 2017-10-17 10:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bmorriso 2017-06-27 20:24:01 EDT
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:

Note You need to log in before you can comment on or make changes to this bug.