You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Edward Zhang (JIRA)" <ji...@apache.org> on 2016/09/18 23:42:20 UTC

[jira] [Resolved] (EAGLE-26) Generic solution for Eagle topology merge

     [ https://issues.apache.org/jira/browse/EAGLE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward Zhang resolved EAGLE-26.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.5

This is accomplished with new alert engine released at Eagle 0.5

> Generic solution for Eagle topology merge
> -----------------------------------------
>
>                 Key: EAGLE-26
>                 URL: https://issues.apache.org/jira/browse/EAGLE-26
>             Project: Eagle
>          Issue Type: New Feature
>            Reporter: Edward Zhang
>            Assignee: Edward Zhang
>             Fix For: 0.5
>
>
> One Eagle topology can have multiple data sources, but in practice, some policies need to join streams from multiple different topologies on the fly. For example user security logging stream and user audit logging stream are 2 different physical topologies, if we want a policy like "user tries logon xxx times and then access sensitive information", then we have develop a new topology to join the 2 data sources. That is not good. We should provide a way of easily merge the streams from the 2 existing topologies in runtime instead of in development time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)