Auditing
John Mazzitelli
mazz at redhat.com
Tue Jun 19 12:36:32 UTC 2012
This is something Jay talked about (and others) a while ago. What we should have done in the beginning was create a generic "Audit Trail" subsystem - and have all the other subsystems log messages there. That way, we don't have N different, isolated "history" trails and N different ways to purge and query them. Unfortunately, we didn't do that - so we have things like (what you see) the operation history audit, we also have rsource config history, plugin config history, etc.
It would be alot of work (though probably doable - maybe not easy to upgrade from old schema to new however) - we could rip out all these isolated history tables and design and build an "Audit" subsystem that all other subsystems can share.
----- Original Message -----
> Hi,
>
> I just came across the javadoc of this method:
> org.rhq.enterprise.server.operation.OperationManagerLocal#deleteOperationHistory
>
> " Purges the history from the database. Doing this loses all audit
> trails of the invoked operation. "
>
> I wonder how much we would want an audit subsystem, where e.g. the
> some information of the
> history + who scheduled it originally and who removed the record is
> just appended to a table.
> The same is of course true for other subsystems.
>
> --
> Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
> Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
> Handelsregister: Amtsgericht München HRB 153243
> Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham,
> Charles Cachera
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
>
More information about the rhq-devel
mailing list