You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jonathan Robie (JIRA)" <qp...@incubator.apache.org> on 2009/10/14 17:04:31 UTC

[jira] Created: (QPID-2139) Usability of log messages

Usability of log messages
-------------------------

                 Key: QPID-2139
                 URL: https://issues.apache.org/jira/browse/QPID-2139
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Broker
            Reporter: Jonathan Robie
             Fix For: 0.6


Our broker log messages are currently ad-hoc, difficult to grep or read, with a bad signal/noise ratio. They could be improved as follows:

- Define log-level usage guidelines, document, and enforce
- Define user-relevant categories for logging, document, and enforce
- Design messages to be easily greppable
- Avoid logging redundant information. Log entry into a state / exit from a state, instead of redundant entries saying what state you are in.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Updated: (QPID-2139) Usability of log messages

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-2139:
-----------------------------------

    Fix Version/s:     (was: 0.6)
                   0.7

Moving items unlikely to be in 0.6 out to 0.7 (since not in progress)

> Usability of log messages
> -------------------------
>
>                 Key: QPID-2139
>                 URL: https://issues.apache.org/jira/browse/QPID-2139
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>            Reporter: Jonathan Robie
>             Fix For: 0.7
>
>
> Our broker log messages are currently ad-hoc, difficult to grep or read, with a bad signal/noise ratio. They could be improved as follows:
> - Define log-level usage guidelines, document, and enforce
> - Define user-relevant categories for logging, document, and enforce
> - Design messages to be easily greppable
> - Avoid logging redundant information. Log entry into a state / exit from a state, instead of redundant entries saying what state you are in.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org