You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/11/03 12:06:00 UTC
[jira] [Commented] (SYNCOPE-1696) Audit Elasticsearch persistence
[ https://issues.apache.org/jira/browse/SYNCOPE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628290#comment-17628290 ]
ASF subversion and git services commented on SYNCOPE-1696:
----------------------------------------------------------
Commit f42ea0bb756a82a39d42617a746f8f213b1f3ff8 in syncope's branch refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=f42ea0bb75 ]
[SYNCOPE-1696] Adding support to manage Audit entries via Elasticsearch (#387)
> Audit Elasticsearch persistence
> -------------------------------
>
> Key: SYNCOPE-1696
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1696
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0.0-M0
> Reporter: Andrea Patricelli
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Labels: elasticsearch
> Fix For: 2.1.13, 3.0.0
>
>
> Give the possibility to switch the audit messages persistence on Elasticsearch, instead of the Syncope database. This will improve search performances and give more powerful search features.
> Besides the main goal there could be also some query improvements to implement, like passing more that on type or category in the AuditQuery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)