hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jerry He <jerry...@gmail.com>
Subject Re: Filtering in HBase Audit Logs
Date Thu, 01 Mar 2018 04:19:36 GMT
Some people probably can share more lights. I recall no hbase built-in
construct to limit or filter the Audit logs, and I agree it can be very
verbose depending on the access operations.

We can propose two approaches to access and fix the issues.

1  Some low hanging cleanup and simplification of the logging messages, to
cleanup duplicate/redundant information that is being outputted.
I am sure there some cleanup/consolidation that can be done.

2. Define a framework to define the construct to saperate and limit the
scope and levels of audit logging, which can be set and turn on and off.

We can open JIRAs to tackle the raised approaches.



On Wed, Feb 28, 2018 at 7:58 PM Subash Kunjupillai <subash.k@ericsson.com>

> Hi,
> Just to give a background, recently I enabled Audit logs in HBase and I
> could see all operations done in HBase is being logged in
> SecurityAuth.audit. And our application is running as hbase user and all
> put
> and get done by this user is also being audited. Due to this audit logs are
> flooding since our data loading frequency is very high.
> Can someone please let me know is there any possibility to filter what
> information to be logged? something like restrict it to specific user or
> specific operations like delete, disable, truncate.
> Regards,
> Subash Kunjupillai
> --
> Sent from:
> http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message