[
https://issues.apache.org/jira/browse/RANGER-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-5262:
-------------------------------------
Issue Type: New Feature (was: Improvement)
> Ranger audit service
> --------------------
>
> Key: RANGER-5262
> URL: https://issues.apache.org/jira/browse/RANGER-5262
> Project: Ranger
> Issue Type: New Feature
> Components: audit
> Reporter: Madhan Neethiraj
> Priority: Major
>
> Access audits generated while authorizing access requests is a critical
> functionality provided by Ranger plugins. Ranger plugins supports sending
> access audits to several destinations, including:
> # Solr
> # Elasticsearch
> # HDFS
> # AWS S3
> # ADLS-Gen2
> # AWS Cloudwatch
> # Kafka
> Ranger plugins are configured with details of destinations the audits are to
> be sent, including credentials to connect with each destination; destination
> specific libraries must be packaged with the plugins as well. This can
> introduce complexities, like mismatch in version of dependent libraries, in
> setting up plugins.
> Ranger audit service that handles details of sending audit logs to various
> destinations will significantly simplify Ranger plugin configuration and
> eliminate inclusion of libraries for audit destinations, there by making the
> plugins lighter.
> The plugins will only need to send audit logs to Ranger audit service, via
> HTTP APIs. Ranger audit service will have configurations and libraries to
> send audit logs to desired destinations. This approach will also eliminate
> the need to restart the plugins to change destination configurations (like
> credentials) or add/remove of the destinations
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
