[
https://issues.apache.org/jira/browse/EAGLE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082438#comment-15082438
]
ASF GitHub Bot commented on EAGLE-79:
-------------------------------------
Github user haoch commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/52#discussion_r48814463
--- Diff: eagle-core/eagle-policy/eagle-policy-base/pom.xml ---
@@ -0,0 +1,62 @@
+<?xml version="1.0"?>
--- End diff --
Never mind, I mistake something. :-)
> Provide analytic DSL support
> -----------------------------
>
> Key: EAGLE-79
> URL: https://issues.apache.org/jira/browse/EAGLE-79
> Project: Eagle
> Issue Type: New Feature
> Affects Versions: 0.3.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> Eagle input comes with stream data (like security audit log), eagle provide
> alerting computation based on CEP DSL.
> Similar to this process, eagle should be able to provide same DSL support to
> expose the real-time monitoring feature, and furthermore could be integrated
> with some storage backend to provide dashboard/presentation to user.
> This would require
> 1. eagle programming API to support a new semantic of query(or aggregation),
> using the similar alert DSL.
> 2. a clear definition of time series storage interface (so that different
> storage engine could be adopted), currently we might start from the eagle
> built-in hbase implementation
> 3. Metric API/Dashboard.
> Currently, it require a lot of user customization and CEP engine capability
> could not be reused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
