You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2021/09/13 19:55:00 UTC

[jira] [Commented] (RANGER-3411) Improvements for Elasticsearch Audit Log Provider

    [ https://issues.apache.org/jira/browse/RANGER-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414561#comment-17414561 ] 

Ramesh Mani commented on RANGER-3411:
-------------------------------------

[~acharneski] Thanks for your valuable contribution to Apache Ranger project.

Please put a review request in [https://reviews.apache.org/dashboard/] for this patch. 

 

> Improvements for Elasticsearch Audit Log Provider
> -------------------------------------------------
>
>                 Key: RANGER-3411
>                 URL: https://issues.apache.org/jira/browse/RANGER-3411
>             Project: Ranger
>          Issue Type: Improvement
>          Components: audit
>            Reporter: Andrew Charneski
>            Priority: Major
>         Attachments: 0001-RANGER-3411-Elasticsearch-Fixes.patch
>
>
> Several improvements are needed to make the Elasticsearch audit log provider viable:
> # Configuration and setup scripts need to support settings for the port, scheme, and index
> # Audit log search logic can remove the "fetch" call after the "searchResources" call to Elasticsearch
> # xasecure.audit.elasticsearch.is.enabled should be supported to enable this provider
> # AuditProviderFactory.java needs logic changes to allow enabling the provider



--
This message was sent by Atlassian Jira
(v8.3.4#803005)