audit

Type Members

1. case class Audit(level: String, msg: String, details: String, link: Option[String] = None, node: Option[String] = None, when: DateTime = DateTime.now, _id: ObjectId = new ObjectId) extends REntity[Audit] with Product with Serializable

   

   generic audit event - stored in db table, log or ELK etc.

   generic audit event - stored in db table, log or ELK etc.

   Some of these may end up as emails or alerts.

   With the Mongo implementation, there are two tables: Audit for events to be reviewed and AuditCleared for reviewed events. You need your own purging of the AuditCleared table.

   The Play Controller for these is controllers.AdminAudit

   these are also used for cluster notifications

   TODO should have a configurable workflow for each of these - what's the pattern?

   Annotations

   @RTable()

2. trait AuditService extends Auditor with Logging

   

   fairly generic website audit service.

   fairly generic website audit service.

   many operations are audited - this is strait in the log files, as well as the logdb() audit facility. Audited events are supposed to end up somewhere special or even notify someone etc

   in my RK, I simply log them in a database, for review - you could do the same or ignore them

   there's a Audit default implementation here somehwer

3. trait Auditor extends AnyRef

   

   mixin this to get the local logdb methods- OR use the static Audit.xxx

   mixin this to get the local logdb methods- OR use the static Audit.xxx

   many operations are audited - this is strait in the log files, as well as the logdb() audit facility. Audited events are supposed to end up somewhere special or even notify someone etc

   in my RK, I simply log them in a database, for review - you could do the same or ignore them or syslogd tham etc

   there's an Audit default implementation here somehwere

4. class MdbAuditService extends AuditService with Logging

   

   diesel's default Audit implementation - stores them events in a Mongo table.

   diesel's default Audit implementation - stores them events in a Mongo table. Use this as an example to write your own auditing service.

   Upon review, move them to the cleared/history table and purge them sometimes

5. class NoAuditService extends AuditService

   

   sample stub audit service - no database backup