[
https://issues.apache.org/jira/browse/HBASE-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-4082.
-----------------------------------
Resolution: Duplicate
Duplicates HBASE-2014. Please comment there Lars.
> Add API call audit trail
> ------------------------
>
> Key: HBASE-4082
> URL: https://issues.apache.org/jira/browse/HBASE-4082
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver
> Reporter: Lars George
> Priority: Minor
>
> It would be very helpful to correlate the log contents with API calls that
> have been made. This includes calls to split, compact, as well as
> bulkLoadHFile and so on. This could be stored in a separate log file if
> wanted, and be disabled by default (unless more want it on than off).
> I could think of an AuditLogger class that is used to write them into a
> shared log context. It should log all primitive parameters as well as a
> reasonable amount of those that binary or larger.
> Sure this could be implemented with an Audit coprocessor, but that isn't here
> yet, and also seems a bit overcomplicating things. BUt I am open for ideas.
> We have it often that we get logs that show some sort of malfunction, but we
> cannot tell what happened beforehand. Some events can be inferred if you have
> intrinsic knowledge of the log messages that precede the event. But that is
> hardcore and not really user-friendly. Being able to switch on the call
> logging would help.
> Also, this is probably not useful for high volume calls, like multi() etc. So
> a selective filtering is needed to fine tune what is logged.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
