Bug 797092 – Support log category exclusion

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 797092 - Support log category exclusion

Summary:	Support log category exclusion

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	2.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	3.0
Target Release:	---
Assigned To:	Chuck Rolke
QA Contact:	Petra Svobodová
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, Triaged

Depends On:
Blocks:	957975
	Show dependency tree / graph

Reported:	2012-02-24 04:08 EST by ranjith ruban
Modified:	2014-09-24 11:04 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	qpid-cpp-0.22-4.el6, qpid-cpp-0.22-4.el5
Doc Type:	Enhancement
Doc Text:	Logs are sometimes flooded by thousands of log messages that may not be considered important during issue investigation. It is now possible to specify a broker option that turns off log messages using precise filters. During problem investigation, users can control log file content to better understand a specific issue, rather than manually filtering out extraneous log events. The feature is supported in the C++ Broker, by specifying --log-disable.
Story Points:	---
Clone Of:
Clones:	957975 (view as bug list)
Environment:
Last Closed:	2014-09-24 11:04:05 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Apache JIRA	QPID-4651	None	None	None	Never
Red Hat Product Errata	RHEA-2014:1296	normal	SHIPPED_LIVE	Red Hat Enterprise MRG Messaging 3.0 Release	2014-09-24 15:00:06 EDT

Groups: None (edit)

Comment 1 Justin Ross 2012-12-07 09:51:55 EST

Chuck, is this now possible with 0.18?

Comment 3 Chuck Rolke 2012-12-07 10:33:20 EST

It is possible indirectly. Instead of "filtering out" QMF messages the user can "filter on" everything but QMF messages. That is accomplished by a series of "--log-enable debug+:<class>" log filters that name all the classes except Management.

Comment 4 Justin Ross 2012-12-07 10:49:03 EST

Okay, let's treat this one as an RFE for opting out of (versus the existing "opt in to") a set of classes.

(In reply to comment #3)
> It is possible indirectly. Instead of "filtering out" QMF messages the user
> can "filter on" everything but QMF messages. That is accomplished by a
> series of "--log-enable debug+:<class>" log filters that name all the
> classes except Management.

Comment 6 Chuck Rolke 2013-04-29 14:55:41 EDT

This is available upstream on trunk at r1476409.
http://svn.apache.org/viewvc?view=revision&revision=r1476409

Comment 11 Petra Svobodová 2014-02-06 05:13:45 EST

Filter out log messages are possible through disabling one or more log levels or sending entities in broker logging, performed by "--log-disable <rule>:<pattern>" option. 

Verified on qpid-cpp-0.22-33 on Rhel6.5-i686 and Rhel6.5-x86_64.

--> VERIFIED

Comment 13 errata-xmlrpc 2014-09-24 11:04:05 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1296.html

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