Bug 683595

Summary: Documentation update: How to change logging level at run time
Product: Red Hat Enterprise MRG Reporter: Ted Ross <tross>
Component: Messaging_Programming_ReferenceAssignee: Joshua Wulf <jwulf>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: low    
Version: 1.3CC: iboverma, jneedle, jskeoch, jwulf, lbrindle, lcarlon, pmoravec, sburgess
Target Milestone: 2.2Flags: jwulf: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-20 03:13:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 660526    
Bug Blocks: 657398, 660531    

Description Ted Ross 2011-03-09 19:42:14 UTC
The new feature "Provide mechanism to alter brokers logging level at runtime" requires documentation of how the feature is accessed and used.

Comment 3 Lana Brindley 2011-10-13 02:51:15 UTC
Setting NEEDINFO from reporter, please feel free to pass on to someone more appropriate.

This will be addressed after 2.1.

LKB

Comment 4 Joshua Wulf 2012-03-30 02:51:05 UTC
This is done programmatically by the look of https://bugzilla.redhat.com/show_bug.cgi?id=657398

Can someone give me a code example that modifies the logging level to increase it, and one to decrease it, and I can write the story:

Something is up, you want to examine what's happening, but you don't want to restart. So you can dynamically turn the logging level up to 11, troubleshoot, and then turn it back down.

Turn the logging level up to 11:

  example code goes here

Turn the logging level back down:

  example code goes here

Comment 6 Pavel Moravec 2012-04-26 07:35:44 UTC
(In reply to comment #4)
> This is done programmatically by the look of
> https://bugzilla.redhat.com/show_bug.cgi?id=657398
> 
> Can someone give me a code example that modifies the logging level to increase
> it, and one to decrease it, and I can write the story:
> 

Does https://access.redhat.com/knowledge/solutions/67020 help? (I can provide content to those not having access to KCS).

Comment 7 Joshua Wulf 2012-04-26 09:58:51 UTC
Yes, that's perfect. Thanks!

Comment 9 Pavel Moravec 2012-05-02 13:57:41 UTC
(In reply to comment #8)
> http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.2/html-single/Messaging_Programming_Reference/index.html#Change_the_logging_level_at_runtime

The command to execute the translated code has typos:

./set\_log\_level "trace+"

should be replaced by:

./set_log_level "trace+"

(The typos come from my KCS article that I just corrected - the syntax in KCS tool is/was sometimes tricky / easy to create a typo).

Comment 12 Cheryn Tan 2012-09-20 02:53:58 UTC
Released for MRG 2.2