Bug 1465706 - Allow users to disable aggregate logging per project
Summary: Allow users to disable aggregate logging per project
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 00:24 UTC by bmorriso
Modified: 2018-12-11 15:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-11 15:03:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description bmorriso 2017-06-28 00:24:01 UTC
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:

Comment 3 Jeff Cantrill 2018-12-11 15:03:23 UTC
Closing in favor of https://jira.coreos.com/browse/LOG-254.  This is a topic to be investigated during the logging 2019 hackfest


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