You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (Created) (JIRA)" <ji...@apache.org> on 2012/03/20 12:29:37 UTC
[jira] [Created] (AMQ-3779) Allow logging broker plugin to use a
log per destination
Allow logging broker plugin to use a log per destination
--------------------------------------------------------
Key: AMQ-3779
URL: https://issues.apache.org/jira/browse/AMQ-3779
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.5.1
Reporter: Gary Tully
Priority: Minor
Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned.
A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.<destination name> for producer send events
--
Query on composites?
For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3779) Allow logging broker plugin to use a
log per destination
Posted by "Gary Tully (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-3779:
----------------------------
Description:
Re:
http://activemq.2283324.n4.nabble.com/How-to-log-all-incoming-msgs-of-Queue-quot-hello-quot-into-a-separate-logfile-td4487917.html
Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned.
A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.<destination name> for producer send events
--
Query on composites?
For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination.
was:
Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned.
A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.<destination name> for producer send events
--
Query on composites?
For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination.
> Allow logging broker plugin to use a log per destination
> --------------------------------------------------------
>
> Key: AMQ-3779
> URL: https://issues.apache.org/jira/browse/AMQ-3779
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Priority: Minor
> Labels: logging, plugin
>
> Re:
> http://activemq.2283324.n4.nabble.com/How-to-log-all-incoming-msgs-of-Queue-quot-hello-quot-into-a-separate-logfile-td4487917.html
> Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned.
> A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.<destination name> for producer send events
> --
> Query on composites?
> For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira