Ranger Audit Options - Is DB Audit still supported in HDP 2.3+?

[#1]

Our customer is planning to take advantage of the new Apache Solr auditing capability in HDP 2.3.

They would also like to keep their exisitng MySQL DB auditing in place. In HDP 2.3+ is the DB Auditing still supported (deprecated)? Or will we be dropping support for this going forward?

Thank you!

References:

http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_Ranger_Install_Guide/content/ranger_datab... http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_Ranger_Install_Guide/content/ch_install_s...

[#2 · Accepted solution]

DB Auditing support will be dropped in future versions.

It is recommended to use Solr auditing.

[#3]

Yes @Wes Floyd

[#4]

In 2.3 it has been deprecated and not recommended for production deployments.

[#5]

This should say -- for production deployments Ranger should be configured to use Solr to index the Audit data. This is the best practice for production deployments. This will be the default configuration starting with HDP 2.5 and the use of a relational data store for Ranger audit (already announced as deprecated) will not be a supported option

[#6]

To add in, as a best practice, we recommend customers using HDP 2.3.x or HDP 2.4.x to configure their audits to both Solr and HDFS. HDFS destination is for long term audit storage, while Solr could be used for short term audit query from the Ranger UI. It is recommended to use a ttl (time to live) setting in Solr to ensure documents are deleted automatically after a certain period.