I’ve talked about our new logging, which I’ve only discussed in theory before. I’m now using the R11 pre-release on my laptop, and I’m blown away by the details (I guess I like strange stuff). I just hope Isode customers will like it as much as I do.
The GUIs give a lot of control on audit logging. The capability for multiple streams also applies for audit logging, so if you need multiple audit logs with different (potentially overlapping) information you can have this.
Some organizations need a lot of audit logging, and others prefer to keep it to a minimum (to save disk space and optimize performance). The GUIs allow you to choose which audit events you want (either select the events you need, or start with all events and deselect ones you don’t want).
We developed for M-Switch, an extensible an esily parseable attribute/value format of event logging. This is important, as there are often lots of parameters that you may wish to log with an event. The aviation industry requires very very detailed logging, of pretty much everything associated with each message. We’re now using this format for the audit logs in all of our products.
You can control which records you want recorded. If you need message trace information, this can be audit logged. Again, this flexibility will enable audit logging to be appropriately tuned to operational requirements.