qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-4079) C++ Broker needs log messages to track object life cycles for auditing
Date Tue, 10 Jul 2012 15:49:34 GMT

    [ https://issues.apache.org/jira/browse/QPID-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410455#comment-13410455

Gordon Sim commented on QPID-4079:

Seems reasonable to me. One comment on having the log statements added to the generated code
though (i.e. for part 2) is that the generator was at one time supposed to be usable for 'agents'
other than the broker. Adding logging statements would add another point of coupling.
> C++ Broker needs log messages to track object life cycles for auditing
> ----------------------------------------------------------------------
>                 Key: QPID-4079
>                 URL: https://issues.apache.org/jira/browse/QPID-4079
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.16
>            Reporter: Chuck Rolke
> The C++ broker logs are unfriendly and incomplete for customers who are hoping to audit
system usage. Missing are log artifacts to expose which user created, used, or destroyed which
> The proposed improvement adds INFO level log statements for the creation, destruction,
and major state changes to connection, session,  and subscription objects, and to exchange,
queue, and binding objects.
> From this set of log messages a user could determine what user from what client system
address created a connection, what sessions were created on that connection, and what subscriptions
were created on those sessions. Similarly the exchange-binding-queue objects would have enough
in their log messages to correlate the interactions between them.
> The log message for the destruction of an object would contain a record of all the management
statistics kept for that object. Then, working through the log records a customer could attribute
broker usage back to specific users.
> This class of log message has been requested by customers using Security Information
and Event Management (SIEM) systems to scrape information from broker event logs.

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


To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message