[GitHub] incubator-eagle issue #330: EAGLE-450: Alert check meta confliction

[RalphSu]

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/330
  
+1

Merged.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-450) Alert check meta version conflict between runtime modules

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418444#comment-15418444
 ] 

ASF GitHub Bot commented on EAGLE-450:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/330
  
+1

Merged.


> Alert check meta version conflict between runtime modules
> -
>
> Key: EAGLE-450
> URL: https://issues.apache.org/jira/browse/EAGLE-450
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>




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

[GitHub] incubator-eagle issue #336: Alert State check

[RalphSu]

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/336
  
This is wrong pr, should to develop not master.
Closed


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #336: Alert State check

[RalphSu]

Github user RalphSu closed the pull request at:

https://github.com/apache/incubator-eagle/pull/336


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #337: init draft impelmentation of multiple sta...

[RalphSu]

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/337

init draft impelmentation of multiple state check

Init draft to provide alert on state, add a state definition in policy 
metadata.

Move input/output stream into definition
Assume the intermediate stream defined in system stream definition
Chain the siddhi definition, use index to identify the next handler.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle statecheck

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/337.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #337


commit 9599a296522f496da7cb7637ba0fa5e97bb77165
Author: Ralph, Su 
Date:   2016-08-12T07:25:54Z

init draft impelmentation of multiple state check




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle issue #331: EAGLE-455 Add JDBCMetadataQueryService, JDBCData...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/331
  
-1 for the early abstraction, we should still use existing implementation 
and push abstraction after we tested all the applications.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-445) convert eagle-hdfs-auditlog app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418229#comment-15418229
 ] 

ASF GitHub Bot commented on EAGLE-445:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/333

convert eagle-hdfs-auditlog app to use new app framework

https://issues.apache.org/jira/browse/EAGLE-445

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/333.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #333


commit feeece3f2b5af9e2c2fa17af6e8806f50a8a2930
Author: yonzhang 
Date:   2016-08-10T21:17:04Z

eagle assembly for new app framework

commit d78d649ffb007dbf327027b17e0aad7dec3b8022
Author: yonzhang 
Date:   2016-08-11T20:53:45Z

first drop for converting hdfs audit app

commit c8598d47797b4145b9a4954bb105966193e3486d
Author: yonzhang 
Date:   2016-08-11T23:09:48Z

hdfs conversion

commit c29893070035cc1e0607ba243a41898f8038d95a
Author: yonzhang 
Date:   2016-08-11T23:28:06Z

fix web app issue for both hdfs and hbase

commit b26e3714e24219eb6fa908db4937a2fd5841606a
Author: yonzhang 
Date:   2016-08-12T00:17:17Z

hdfs topology end-2-end smooth run

commit 0d29a6e401361626ada593c3f084d3b699e61aa6
Author: yonzhang 
Date:   2016-08-12T01:25:40Z

jdbc/memory dao fix




> convert eagle-hdfs-auditlog app to use new app framework
> 
>
> Key: EAGLE-445
> URL: https://issues.apache.org/jira/browse/EAGLE-445
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hdfs-auditlog should use new app framework to manage its lifecycle



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

[jira] [Created] (EAGLE-461) Convert MR history app with new app framework

[Hao Chen (JIRA)]

Hao Chen created EAGLE-461:
--

 Summary: Convert MR history app with new app framework
 Key: EAGLE-461
 URL: https://issues.apache.org/jira/browse/EAGLE-461
 Project: Eagle
  Issue Type: Sub-task
Reporter: Hao Chen
Assignee: Hao Chen






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

Re: Brighttalk: User Behavior Analytics

[Liangfei.Su]

Thanks for the sharing. Daniel :)

On Fri, Aug 12, 2016 at 7:06 AM, Daniel Zhou 
wrote:

> Hi teammates,
>
> I Just watched a video about "user behavior analytics", which I think is
> pretty cool and fit our user case.
> It gives deep analysis on "machine learning and user behavior analytics",
> hope you might be interested in it.
>
> Here is the link:
> https://www.brighttalk.com/webcast/288/216587/user-
> behavior-analytics-a-game-changer-in-the-fight-against-cyber-attacks
>
> Thanks and regards,
> Da
>

[jira] [Commented] (EAGLE-445) convert eagle-hdfs-auditlog app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418314#comment-15418314
 ] 

ASF GitHub Bot commented on EAGLE-445:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/334


> convert eagle-hdfs-auditlog app to use new app framework
> 
>
> Key: EAGLE-445
> URL: https://issues.apache.org/jira/browse/EAGLE-445
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hdfs-auditlog should use new app framework to manage its lifecycle



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

[jira] [Closed] (EAGLE-450) Alert check meta version conflict between runtime modules

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant closed EAGLE-450.
--
Resolution: Fixed

> Alert check meta version conflict between runtime modules
> -
>
> Key: EAGLE-450
> URL: https://issues.apache.org/jira/browse/EAGLE-450
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>




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

[GitHub] incubator-eagle issue #331: EAGLE-455 Add JDBCMetadataQueryService, JDBCData...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/331
  
@Override
public void register(ModuleRegistry registry) {
registry.register(MemoryMetadataStore.class, new AbstractModule() {
@Override
protected void configure() {

bind(ISecurityMetadataDAO.class).to(InMemMetadataDaoImpl.class);
}
});

registry.register(JDBCMetadataStore.class, new AbstractModule() {
@Override
protected void configure() {

bind(ISecurityMetadataDAO.class).to(JDBCSecurityMetadataDAO.class);
}
});
}

Again this is too cumbersome, too much code for application and application 
developer need understand the framework to use.
Further, what if the application needs know configuration for eagle server. 
I still prefer to have global configuration to each application for flexibility.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #335: EAGLE-458 Migrate eagle-jpm-spark-running...

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/335

EAGLE-458 Migrate eagle-jpm-spark-running using appplication framework

https://issues.apache.org/jira/browse/EAGLE-458

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle EAGLE-458

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/335.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #335


commit 5588d1c25f7fc592a57ff71562aa8e6186917f12
Author: Hao Chen 
Date:   2016-08-12T03:35:50Z

Migrate /eagle-jpm-spark-running using appplication framework




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-458) Convert spark running app using new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418310#comment-15418310
 ] 

ASF GitHub Bot commented on EAGLE-458:
--

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/335

EAGLE-458 Migrate eagle-jpm-spark-running using appplication framework

https://issues.apache.org/jira/browse/EAGLE-458

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle EAGLE-458

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/335.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #335


commit 5588d1c25f7fc592a57ff71562aa8e6186917f12
Author: Hao Chen 
Date:   2016-08-12T03:35:50Z

Migrate /eagle-jpm-spark-running using appplication framework




> Convert spark running app using new app framework
> -
>
> Key: EAGLE-458
> URL: https://issues.apache.org/jira/browse/EAGLE-458
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle issue #331: EAGLE-455 Add JDBCMetadataQueryService, JDBCData...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/331
  
I think the implementation is to provide the foundation for make sure the 
code modules extensible, as how much code developer should write it's to 
continue simplifying the interface or DSL. I was told to think interface 
earlier than implementation.

> - Further, what if the application needs know configuration for eagle 
server

We should follow the defined interface of Application. For Application 
standalone mode, the configuration should be passed through configuration file, 
for Application managed by server, the configuration should be passed through: 
https://github.com/apache/incubator-eagle/blob/develop/eagle-core/eagle-app/eagle-app-base/src/main/java/org/apache/eagle/app/service/ApplicationContext.java#L70

this.config = 
ConfigFactory.parseMap(executionConfig).withFallback(envConfig);

For managed classes, it could easily get server config by `@Inject Config 
config;`



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-445) convert eagle-hdfs-auditlog app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418309#comment-15418309
 ] 

ASF GitHub Bot commented on EAGLE-445:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/334

hdfs,hbase,mapr app conversion

https://issues.apache.org/jira/browse/EAGLE-445

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/334.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #334


commit 8c4c53a28a308908944086f7f5027a495c558b47
Author: yonzhang 
Date:   2016-08-12T03:39:08Z

hdfs,hbase,mapr app conversion




> convert eagle-hdfs-auditlog app to use new app framework
> 
>
> Key: EAGLE-445
> URL: https://issues.apache.org/jira/browse/EAGLE-445
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hdfs-auditlog should use new app framework to manage its lifecycle



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

[jira] [Commented] (EAGLE-445) convert eagle-hdfs-auditlog app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418307#comment-15418307
 ] 

ASF GitHub Bot commented on EAGLE-445:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/333


> convert eagle-hdfs-auditlog app to use new app framework
> 
>
> Key: EAGLE-445
> URL: https://issues.apache.org/jira/browse/EAGLE-445
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hdfs-auditlog should use new app framework to manage its lifecycle



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

[jira] [Closed] (EAGLE-440) Alert mongodb storage refine

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant closed EAGLE-440.
--
Resolution: Fixed

> Alert mongodb storage refine
> 
>
> Key: EAGLE-440
> URL: https://issues.apache.org/jira/browse/EAGLE-440
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Currently, some Alert Mongo Collection is too large. Consider future 
> increase, need to split large collection to some small collections.
> To back compatible, need to keep the interface as the same as before. 



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

[jira] [Commented] (EAGLE-416) Add check style support

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418375#comment-15418375
 ] 

ASF GitHub Bot commented on EAGLE-416:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/303
  
LGTM


> Add check style support
> ---
>
> Key: EAGLE-416
> URL: https://issues.apache.org/jira/browse/EAGLE-416
> Project: Eagle
>  Issue Type: Improvement
>Reporter: JiJun Tang
>Assignee: JiJun Tang
>Priority: Trivial
>  Labels: engineering, pull-request-available
> Fix For: v0.5.0
>
>
> Add check style when build the project. Just print warning in console.



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

[EAGLE BUILD FAILED] incubator-eagle-develop failed on build #26

[Apache Jenkins Server]

The Apache Jenkins build system has built incubator-eagle-develop (build 
#26) Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-develop/26/ to view the 
results. Test Report is at: Test Result

how to configuration alert notify to mail

[javacaoyu]

HI eagle devs:
I create a new policy in step 3 to configuration notification with mail.
I can config the `sender` `subject` `description` in web ui, but can’t config 
`username` `password` `mailhost` `smtp port`
My mail server need this.
please help me tell me where to config it. thanks very much.

[GitHub] incubator-eagle pull request #332: convert eagle-hdfs-auditlog app to use ne...

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/332


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle issue #316: [EAGLE-438] Multiple Inputs for Hadoop JMX Colle...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/316
  
Thanks for the contribution, Peter, it is merged in 
https://github.com/apache/incubator-eagle/commit/502c7e37f842eabc4021c47053dd95bdd1c7efde
Please close this PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419553#comment-15419553
 ] 

ASF GitHub Bot commented on EAGLE-438:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/316
  
Thanks for the contribution, Peter, it is merged in 
https://github.com/apache/incubator-eagle/commit/502c7e37f842eabc4021c47053dd95bdd1c7efde
Please close this PR.


> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[GitHub] incubator-eagle pull request #316: [EAGLE-438] Multiple Inputs for Hadoop JM...

[peterkim95]

Github user peterkim95 closed the pull request at:

https://github.com/apache/incubator-eagle/pull/316


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419555#comment-15419555
 ] 

ASF GitHub Bot commented on EAGLE-438:
--

Github user peterkim95 closed the pull request at:

https://github.com/apache/incubator-eagle/pull/316


> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



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

[GitHub] incubator-eagle issue #337: init draft impelmentation of multiple state chec...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/337
  
Good to see that stateCheck can be aligned with policy evaluation, that 
would be easy for user to define state rules.  LGTM.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle issue #335: EAGLE-458 Migrate eagle-jpm-spark-running using ...

[yonzhang]

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/335
  
LGTM. but to complete application conversion, we need complete 
configuration in metadata.xml like application.conf. Future, we may be able to 
reduce this duplication.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-458) Convert spark running app using new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419591#comment-15419591
 ] 

ASF GitHub Bot commented on EAGLE-458:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/335
  
LGTM. but to complete application conversion, we need complete 
configuration in metadata.xml like application.conf. Future, we may be able to 
reduce this duplication.


> Convert spark running app using new app framework
> -
>
> Key: EAGLE-458
> URL: https://issues.apache.org/jira/browse/EAGLE-458
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Hao Chen
>Assignee: Hao Chen
>




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

[GitHub] incubator-eagle pull request #338: hive query log monitoring application usi...

[yonzhang]

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/338

hive query log monitoring application using new app framework

https://issues.apache.org/jira/browse/EAGLE-446

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/338.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #338


commit 597a815bfa6120d08faec244235af30e1a7a3aca
Author: yonzhang 
Date:   2016-08-12T23:35:55Z

hive monitoring conversion

commit 982670ad8b4e384d1d865beb28743db2690adfbf
Author: yonzhang 
Date:   2016-08-12T23:36:40Z

add bash files




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-446) convert eagle-hive app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419683#comment-15419683
 ] 

ASF GitHub Bot commented on EAGLE-446:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/338

hive query log monitoring application using new app framework

https://issues.apache.org/jira/browse/EAGLE-446

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/338.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #338


commit 597a815bfa6120d08faec244235af30e1a7a3aca
Author: yonzhang 
Date:   2016-08-12T23:35:55Z

hive monitoring conversion

commit 982670ad8b4e384d1d865beb28743db2690adfbf
Author: yonzhang 
Date:   2016-08-12T23:36:40Z

add bash files




> convert eagle-hive app to use new app framework
> ---
>
> Key: EAGLE-446
> URL: https://issues.apache.org/jira/browse/EAGLE-446
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hive should use new application framework



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

Heads up for Eagle 0.5 in develop branch

[Edward Zhang]

Hi Eagle Community,

There are some on-going significant changes in Eagle 0.5 regarding code
structure and features. These changes happen in develop branch, so we see
many PRs recently.

One heads up is those changes may break the existing way of you running an
Eagle application. It needs one week or so to make all applications to run
in a new way consistently.

Those significant changes are as follows:

1. Alert engine is decoupled into a separate component. Before Eagle 0.5,
application uses alert engine as a java library. In Eagle 0.5, Alert engine
becomes a multi-tenant platform where data from different applications can
potentially go into one single (or multiple) storm topology to be evaluated
based on some CEP rules. Also, Alert engine will support correlation of
different streams of events by declaring multiple input streams in one
policy.

This decoupling brings extra benefit e.g. any data in Kafka can go to alert
engine directly for alerting purposing without having to write code if the
data in Kafka is already ready for setting up rule.

2. Application configuration and lifecycle management. Before Eagle 0.5,
application is one storm topology which we use local configuration file to
manage, start, stop in a linux box. But Eagle in production normally
consists of many topologies which process different type of data sources.
Operational cost is very big without Eagle to manage those applications'
configuration and lifecycle.

In Eagle 0.5, application constitutes 2 parts, i.e. managed storm topology
and web resources. Both parts need configurations and those configurations
are managed by Eagle API. By this way, operations can start/stop/status
check storm topology remotely and manage multiple sites(datacenter) in one
organization.

Another benefit of application management is that it is very easy to
onboard a new Eagle monitoring application because processing(topology) and
web(UI/API) are both managed by Eagle platform.

3. More features. Besides existing security features, Eagle community has
integrated more Hadoop monitoring related features into Eagle, including
Hadoop running job, history job, Yarn queue, JMX metrics, Namenode log, GC
log, bad node check etc.

Because of #1 and #2, Eagle platform now becomes more open and friendly to
add any new monitoring features.

Thanks
Edward

[GitHub] incubator-eagle pull request #338: hive query log monitoring application usi...

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/338


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-446) convert eagle-hive app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419822#comment-15419822
 ] 

ASF GitHub Bot commented on EAGLE-446:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/338


> convert eagle-hive app to use new app framework
> ---
>
> Key: EAGLE-446
> URL: https://issues.apache.org/jira/browse/EAGLE-446
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-hive should use new application framework



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

[GitHub] incubator-eagle pull request #339: convert eagle-gc app to use new app frame...

[yonzhang]

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/339

convert eagle-gc app to use new app framework

https://issues.apache.org/jira/browse/EAGLE-444

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/339.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #339


commit 597a815bfa6120d08faec244235af30e1a7a3aca
Author: yonzhang 
Date:   2016-08-12T23:35:55Z

hive monitoring conversion

commit 982670ad8b4e384d1d865beb28743db2690adfbf
Author: yonzhang 
Date:   2016-08-12T23:36:40Z

add bash files

commit 6ef22823cc8e38169fabe766255bb2ec7cd67215
Author: yonzhang 
Date:   2016-08-13T04:43:37Z

convert gc log

commit 820516e88571de037c540d97929c305d48308bd6
Author: yonzhang 
Date:   2016-08-13T06:33:34Z

gclog and metric collection conversion

commit e8ce38da43c5b6af473ad21e16bda0513357eae9
Author: yonzhang 
Date:   2016-08-13T06:37:57Z

merge with upstream develop




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-444) convert eagle-gc app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419829#comment-15419829
 ] 

ASF GitHub Bot commented on EAGLE-444:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/339

convert eagle-gc app to use new app framework

https://issues.apache.org/jira/browse/EAGLE-444

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/339.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #339


commit 597a815bfa6120d08faec244235af30e1a7a3aca
Author: yonzhang 
Date:   2016-08-12T23:35:55Z

hive monitoring conversion

commit 982670ad8b4e384d1d865beb28743db2690adfbf
Author: yonzhang 
Date:   2016-08-12T23:36:40Z

add bash files

commit 6ef22823cc8e38169fabe766255bb2ec7cd67215
Author: yonzhang 
Date:   2016-08-13T04:43:37Z

convert gc log

commit 820516e88571de037c540d97929c305d48308bd6
Author: yonzhang 
Date:   2016-08-13T06:33:34Z

gclog and metric collection conversion

commit e8ce38da43c5b6af473ad21e16bda0513357eae9
Author: yonzhang 
Date:   2016-08-13T06:37:57Z

merge with upstream develop




> convert eagle-gc app to use new app framework
> -
>
> Key: EAGLE-444
> URL: https://issues.apache.org/jira/browse/EAGLE-444
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-gc app should use new app framework to manage its lifecycle



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

[jira] [Commented] (EAGLE-444) convert eagle-gc app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419830#comment-15419830
 ] 

ASF GitHub Bot commented on EAGLE-444:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/339


> convert eagle-gc app to use new app framework
> -
>
> Key: EAGLE-444
> URL: https://issues.apache.org/jira/browse/EAGLE-444
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-gc app should use new app framework to manage its lifecycle



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

[GitHub] incubator-eagle pull request #339: convert eagle-gc app to use new app frame...

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/339


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #340: gclog and metric collection conversion

[yonzhang]

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/340

gclog and metric collection conversion

https://issues.apache.org/jira/browse/EAGLE-444

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/340.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #340


commit c8df6ae290796263f4687a91e37a88712a21f414
Author: yonzhang 
Date:   2016-08-13T06:44:45Z

gclog and metric collection conversion




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-444) convert eagle-gc app to use new app framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419831#comment-15419831
 ] 

ASF GitHub Bot commented on EAGLE-444:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/340

gclog and metric collection conversion

https://issues.apache.org/jira/browse/EAGLE-444

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/340.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #340


commit c8df6ae290796263f4687a91e37a88712a21f414
Author: yonzhang 
Date:   2016-08-13T06:44:45Z

gclog and metric collection conversion




> convert eagle-gc app to use new app framework
> -
>
> Key: EAGLE-444
> URL: https://issues.apache.org/jira/browse/EAGLE-444
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-gc app should use new app framework to manage its lifecycle



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