[CONF] Apache Qpid: Logging Format Design (comment added)

[confluence]

Comment Added : qpid : Re: Logging Format Design Logging Format Design commented on by Martin Ritchie (Jul 01, 2009). Comment: Agree that having a regex is undesirable. If I understand your objections correctly they around the inconsistency with queue display and selecting conection details. To answer your points I think if we always follow the queue format qu(<name>) then it will be easy to extract. So the subscription event would be come: 2009-06-29 13:35:10,1234 +0100 [ con:1(u...@127.0.0.1/)/ch:2/sub:1:qu(myqueue) ] Subscription Event Occcured The benefit of this is a single simple grep for the qu(myqueue) will find all log statements that were for that queue. The other change is to the connection details: con:1(u...@127.0.0.1/) I think this is more understandable form a user's point of view and still machine parsable. I think this encorporates the main points of your suggestion. I'm not convinced by the sequence of '<host>:<remote-port>:<channel>:<virtualhost>:' as this is not easily understood by a human operator.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences

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