JMX matrices and audit logs serve completely different purposes.
Yup, I know, but I was thinking about exporting those metrics to systems like Graphite or Nagios that can keep a record of ops exposed (given the right adapters), aggregate the data and show them in fancy dashboards. But you right: they are complementary. I would even go further to suggest that we could have JMX commands to enable/disable the audit log.
Audit logs does not log all the operations, they log only the operations which change the state of the system.
Even so, this can be a LOT of operations (state changes). THIS, in fact is my only point regarding this issue, but I am all favour about the prospect of adding an audit log. Even on previous comment about it (sorry, if I was unclear about that).
When the audit log is disabled, the performance impact is negligible. But when audit log is enabled offcourse there will be slight performace degradation
Sure. Let's do this and measure his performance degradation under a high load of write ops, so that users can be aware of its impact.
TL;DR: I am +1 about adding an audit log, we certainly need this.