Setting NEEDINFO from reporter, please feel free to pass on to someone more appropriate.

This will be addressed after 2.1.

LKB

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

(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).

Yes, that's perfect. Thanks!

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

(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).

Fixed and published:
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

Released for MRG 2.2