[
https://issues.apache.org/jira/browse/HBASE-14396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738762#comment-14738762
]
Ashish Singhi commented on HBASE-14396:
---------------------------------------
I think this is logged as part of params which is part of context.
{code}
public String toString() {
String familiesString = toFamiliesString(families, family, qualifier);
String[] params = new String[] {
namespace != null ? "namespace=" + namespace : null,
tableName != null ? "table=" +
tableName.getNameWithNamespaceInclAsString() : null,
familiesString.length() > 0 ? "family=" + familiesString : null
};
return Joiner.on(",").skipNulls().join(params);
}
{code}
Am I missing anything ?
> audit log should record the operation object
> ---------------------------------------------
>
> Key: HBASE-14396
> URL: https://issues.apache.org/jira/browse/HBASE-14396
> Project: HBase
> Issue Type: Bug
> Reporter: sunhaitao
>
> Currently the hbase audit log only records the user and scope,we can't know
> which table the user is operating on unless the scope is table.
> It would be better to know what's going on if we record the exact table and
> column family we are operating on besides the scope.
> String logMessage =
> "Access " + (result.isAllowed() ? "allowed" : "denied") + " for user "
> + (result.getUser() != null ? result.getUser().getShortName() :
> "UNKNOWN")
> + "; reason: " + result.getReason() + "; remote address: "
> + (remoteAddr != null ? remoteAddr : "") + "; request: " +
> result.getRequest()
> + "; context: " + result.toContextString();
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
