Notification becomes an important integration point for EAGLE with external tools.
This part should be extensible and declarative. Extensible: some jars/classes which contain specific notification implementations. Those implementations accepts some specific arguments, for example email notification accepts arguments like sender, receiver etc. Declarative: Some notification should Support dynamic code or scripts for example dynamic java code, script(python, perl) Notification declarations should be also dynamically downloaded and framework should support its lifecycle. Please suggest. Thanks Edward On 12/9/15, 11:13, "Zhang, Edward (GDI Hadoop)" <[email protected]> wrote: >Notification framework is really hard. I have some thoughts for >notification extensibility design, please suggest more. > >1. alert notification is one interface which accepts alert entity, >forwards that to external system, reports status, ... >2. framework should invoke alert notification instance in synchronized or >asynchronized way given that some notification is very heavy >3. framework should do notification in parallel or sequentially >4. framework should ensure alert notification is sent out (at least once) >5. user registers new alert notification type by full qualified class name >while topology starts up. (Not necessarily to be hot deploy) >6. notification is setup while defining policy, so notification is per >policy >6. Separation of concerns of alert generation and alert notification. Raw >alert can be generated into messaging bus to be consumed. But this can be >done later on > >public interface AlertConsumer{ > void onAlert(AlertEntitiy alert); > Status getStatus(); >} > >Because framework and notification could be distributed into different >nodes, we still need more mechanism for the communication between >framework and notification. But today we can just assume everything is on >the same JVM or there is no status report. > >Thanks >Edward > >On 12/9/15, 0:24, "Liangfei.Su" <[email protected]> wrote: > >>Awesome! >> >>If there is anything(analysis/design) that we think worth for recording, >>then https://cwiki.apache.org/confluence/display/EAG/eagle could be used. >> >>Ralph >> >>On Wed, Dec 9, 2015 at 4:11 PM, Senthil Kumar <[email protected]> >>wrote: >> >>> Hi All , I'll look into the following JIRA's.. >>> >>> https://issues.apache.org/jira/browse/EAGLE-82 >>> https://issues.apache.org/jira/browse/EAGLE-81 >>> https://issues.apache.org/jira/browse/EAGLE-47 >>> >>> Will notify this group later on each JIRA's Analysis & Design .. >>> >>> Regards, >>> Senthil >>> >
