You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Hao Chen (JIRA)" <ji...@apache.org> on 2016/11/11 06:16:59 UTC

[jira] [Resolved] (EAGLE-5) Minimal general-purpose monitoring engine

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

Hao Chen resolved EAGLE-5.
--------------------------
    Resolution: Fixed

> Minimal general-purpose monitoring engine 
> ------------------------------------------
>
>                 Key: EAGLE-5
>                 URL: https://issues.apache.org/jira/browse/EAGLE-5
>             Project: Eagle
>          Issue Type: New Feature
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>
> As the first step, we should allow traditional monitoring 'users' to
> 1. Create kafka topic say
> 2. Configure stream on UI
> 3. Start generic KafkaStreamMonitor topology pointing to the kafka and stream "storm jar KafkaStreamMonitor --topic $kafka_topic_name --stream $configured_stream_name "
> 4. Then user could start to define policy with eagle policy manager UI
> As the second step, we should allow 'developers' to define stream schema, transformation and alert pipeline in very easily way, schema metadata could be defined from inline / file / database (UI), as to inline/file way, the framework will finally sync the stream schema into database (UI), so that make sure the single source of truth.
> As the third step, we may create a never-existed experience as what you described. We could allow user to define end-to-end monitoring stream pipeline with UI:
> 1. DAG Builder
> 1) Set Data Source
> 2) Set Stream Schema
> 3) Define Transformation with simple method or advanced programming scripts like groovy
> 4) Connect to Alert Engine
> 2. DAG Manager
> 1) Automatically build DAG
> 2) Automatically schedule DAG



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