[jira] [Resolved] (EAGLE-148) Master build failure due to siddhi ql test

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-148.

Resolution: Fixed

> Master build failure due to siddhi ql test
> --
>
> Key: EAGLE-148
> URL: https://issues.apache.org/jira/browse/EAGLE-148
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25



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

[jira] [Commented] (EAGLE-148) Master build failure due to siddhi ql test

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-148:
--

Github user asfgit closed the pull request at:

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


> Master build failure due to siddhi ql test
> --
>
> Key: EAGLE-148
> URL: https://issues.apache.org/jira/browse/EAGLE-148
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25



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

[GitHub] incubator-eagle pull request: EAGLE-148: Master build failure due ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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.
---

Re: [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25

[Liangfei.Su]

https://issues.apache.org/jira/browse/EAGLE-148, and PR
https://github.com/apache/incubator-eagle/pull/80
for this. This PR to fix the CI urgent.

I'm preparing another PR for the deep fix following along with more hadoop
metric cases.

On Wed, Feb 3, 2016 at 10:46 AM, Michael Wu  wrote:

> cool, thanks, Ralph!
>
> On Wed, Feb 3, 2016 at 9:35 AM, Liangfei.Su  wrote:
>
> > I will fix. The test case is about test the metric siddhi QL for hadoop
> > metrics during policy development.
> >
> > On Wed, Feb 3, 2016 at 8:45 AM, Michael Wu  wrote:
> >
> > > Hi guys,
> > >
> > > This new build has new unit test failing:
> > > org.apache.eagle.hadoop.metric.TestHadoopMetricSiddhiQL.testNameNodeLag
> > > <
> > >
> >
> https://builds.apache.org/job/incubator-eagle-main/25/testReport/org.apache.eagle.hadoop.metric/TestHadoopMetricSiddhiQL/testNameNodeLag/
> > > >
> > >
> > > Could anyone who own this case fix it please?
> > >
> > > Thanks,
> > > Michael
> > >
> > > On Fri, Jan 29, 2016 at 12:15 PM, Apache Jenkins Server <
> > > jenk...@builds.apache.org> wrote:
> > >
> > > > The Apache Jenkins build system has built incubator-eagle-main (build
> > > #25)
> > > > Status: Failure Check console output at
> > > > https://builds.apache.org/job/incubator-eagle-main/25/ to view the
> > > > results. Test Report is at: Test Result
> > > > 
> > >
> >
>

[GitHub] incubator-eagle pull request: EAGLE-148: Master build failure due ...

[RalphSu]

GitHub user RalphSu opened a pull request:

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

EAGLE-148: Master build failure due to siddhi ql test

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

Fix to ignore the case first. Another fix to this test will be provided

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

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

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

https://github.com/apache/incubator-eagle/pull/80.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 #80


commit cbeb174a49f80f2a19ba5da9fdb4ec61a780
Author: Ralph, Su 
Date:   2016-02-03T04:28:42Z

EAGLE-148: Master build failure due to siddhi ql test

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

Fix to ignore the case first. Another fix to this test will be provided




---
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-148) Master build failure due to siddhi ql test

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-148:
--

GitHub user RalphSu opened a pull request:

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

EAGLE-148: Master build failure due to siddhi ql test

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

Fix to ignore the case first. Another fix to this test will be provided

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

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

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

https://github.com/apache/incubator-eagle/pull/80.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 #80


commit cbeb174a49f80f2a19ba5da9fdb4ec61a780
Author: Ralph, Su 
Date:   2016-02-03T04:28:42Z

EAGLE-148: Master build failure due to siddhi ql test

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

Fix to ignore the case first. Another fix to this test will be provided




> Master build failure due to siddhi ql test
> --
>
> Key: EAGLE-148
> URL: https://issues.apache.org/jira/browse/EAGLE-148
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25



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

[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user murkrishn commented on the pull request:

https://github.com/apache/incubator-eagle/pull/71#issuecomment-179029623
  
@yonzhang Yes, the syntax you have mentioned is used.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[murkrishn]

Github user murkrishn commented on the pull request:

https://github.com/apache/incubator-eagle/pull/71#issuecomment-179029623
  
@yonzhang Yes, the syntax you have mentioned is used.


---
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: EAGLE-95 DAM HDFS topology fails to ...

[yonzhang]

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/71#issuecomment-179026687
  
it is not correct for showing log stack. Normally, it is LOG.error("some 
message", ex) where ex is the exception object which is passed from catch 
clause.


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user yonzhang commented on the pull request:

https://github.com/apache/incubator-eagle/pull/71#issuecomment-179026687
  
it is not correct for showing log stack. Normally, it is LOG.error("some 
message", ex) where ex is the exception object which is passed from catch 
clause.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680741
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

The updatePolicyDetails() already uses T for getting the entity. 
The logic inside of casting to AlertDefinitionAPIEntity and adding values 
specific to the class has been moved outside the impl class.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[murkrishn]

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680741
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

The updatePolicyDetails() already uses T for getting the entity. 
The logic inside of casting to AlertDefinitionAPIEntity and adding values 
specific to the class has been moved outside the impl class.


---
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: EAGLE-95 DAM HDFS topology fails to ...

[murkrishn]

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680576
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionDAO.java
 ---
@@ -21,6 +21,7 @@
 import java.util.Map;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Unused import AlertDefinitionAPIEntity removed.


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680557
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
--- End diff --

Exception object added to the log.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[murkrishn]

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680557
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
--- End diff --

Exception object added to the log.


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680576
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionDAO.java
 ---
@@ -21,6 +21,7 @@
 import java.util.Map;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Unused import AlertDefinitionAPIEntity removed.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680540
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
+   } finally {
+   try {
+   if (null != client)
+   client.close();
+   } catch (IOException exception) {
+   LOG.debug("Unable to close Eagle service 
client, " + exception.getMessage());
--- End diff --

Exception object added to the log.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[murkrishn]

Github user murkrishn commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51680540
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
+   } finally {
+   try {
+   if (null != client)
+   client.close();
+   } catch (IOException exception) {
+   LOG.debug("Unable to close Eagle service 
client, " + exception.getMessage());
--- End diff --

Exception object added to the log.


---
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: EAGLE-147 add checkstyle and jacoco ...

[anyway1021]

Github user anyway1021 closed the pull request at:

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


---
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] [Created] (EAGLE-148) Master build failure due to siddhi ql test

[Su Ralph (JIRA)]

Su Ralph created EAGLE-148:
--

 Summary: Master build failure due to siddhi ql test
 Key: EAGLE-148
 URL: https://issues.apache.org/jira/browse/EAGLE-148
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Su Ralph
Assignee: Su Ralph
 Fix For: 0.3.0


[EAGLE BUILD FAILED] incubator-eagle-main failed on build #25



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

[GitHub] incubator-eagle pull request: EAGLE-147 add checkstyle and jacoco ...

[anyway1021]

Github user anyway1021 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/79#issuecomment-178995314
  
checkstyle may not be the best solution, will close this pr, change the 
plugin and open another one.


---
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-147) Add checkstyle and jacoco plugin to eagle's pom.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-147:
--

Github user anyway1021 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/79#issuecomment-178995314
  
checkstyle may not be the best solution, will close this pr, change the 
plugin and open another one.


> Add checkstyle and jacoco plugin to eagle's pom.
> 
>
> Key: EAGLE-147
> URL: https://issues.apache.org/jira/browse/EAGLE-147
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[jira] [Commented] (EAGLE-147) Add checkstyle and jacoco plugin to eagle's pom.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-147:
--

Github user anyway1021 closed the pull request at:

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


> Add checkstyle and jacoco plugin to eagle's pom.
> 
>
> Key: EAGLE-147
> URL: https://issues.apache.org/jira/browse/EAGLE-147
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[jira] [Commented] (EAGLE-147) Add checkstyle and jacoco plugin to eagle's pom.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-147:
--

GitHub user anyway1021 opened a pull request:

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

EAGLE-147 add checkstyle and jacoco maven plugin, and ealge-qe sub-module 
to incubator-ealge/pom.xml

add checkstyle maven plugin to incubator-eagle/pom.xml
add jacoco maven plugin to incubator-eagle/pom.xml
add sub-module eagle-qe and modify incubator-eagle/pom.xml to depend on it 
for using eagle-qe/checkstyle.xml and analyze the project and its sub-modules

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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-147

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

https://github.com/apache/incubator-eagle/pull/79.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 #79


commit fad07cd37cbe83c8803e017414c958058d56b836
Author: ziwu 
Date:   2016-02-03T03:24:10Z

add checkstyle maven plugin to incubator-eagle/pom.xml
add jacoco maven plugin to incubator-eagle/pom.xml
add sub-module eagle-qe and modify incubator-eagle/pom.xml to depend on it 
for using eagle-qe/checkstyle.xml and analyze the project and its sub-modules




> Add checkstyle and jacoco plugin to eagle's pom.
> 
>
> Key: EAGLE-147
> URL: https://issues.apache.org/jira/browse/EAGLE-147
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>




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

[GitHub] incubator-eagle pull request: EAGLE-147 add checkstyle and jacoco ...

[anyway1021]

GitHub user anyway1021 opened a pull request:

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

EAGLE-147 add checkstyle and jacoco maven plugin, and ealge-qe sub-module 
to incubator-ealge/pom.xml

add checkstyle maven plugin to incubator-eagle/pom.xml
add jacoco maven plugin to incubator-eagle/pom.xml
add sub-module eagle-qe and modify incubator-eagle/pom.xml to depend on it 
for using eagle-qe/checkstyle.xml and analyze the project and its sub-modules

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

$ git pull https://github.com/anyway1021/incubator-eagle EAGLE-147

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

https://github.com/apache/incubator-eagle/pull/79.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 #79


commit fad07cd37cbe83c8803e017414c958058d56b836
Author: ziwu 
Date:   2016-02-03T03:24:10Z

add checkstyle maven plugin to incubator-eagle/pom.xml
add jacoco maven plugin to incubator-eagle/pom.xml
add sub-module eagle-qe and modify incubator-eagle/pom.xml to depend on it 
for using eagle-qe/checkstyle.xml and analyze the project and its sub-modules




---
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-132) Apply static code check on eagle quality pipeline.

[Michael Wu (JIRA)]

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

Michael Wu commented on EAGLE-132:
--

Depends on ticket EAGLE-147.

> Apply static code check on eagle quality pipeline.
> --
>
> Key: EAGLE-132
> URL: https://issues.apache.org/jira/browse/EAGLE-132
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>
> Need to add static code check to the pipeline, should take the CI job 
> https://builds.apache.org/job/incubator-eagle-main as the basis.
> And this task depends on the successful build phases of compilation and 
> unit-test-pass. Means the completion of ticket EAGLE-131.



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

[jira] [Commented] (EAGLE-133) Analyze code coverage of unit test in quality pipeline.

[Michael Wu (JIRA)]

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

Michael Wu commented on EAGLE-133:
--

Depends on ticket EAGLE-147.

> Analyze code coverage of unit test in quality pipeline.
> ---
>
> Key: EAGLE-133
> URL: https://issues.apache.org/jira/browse/EAGLE-133
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
>
> Need to analyze code coverage (CC) in the pipeline and showcase it to an 
> appropriate place, should take the CI job 
> https://builds.apache.org/job/incubator-eagle-main as the basis, and consider 
> if embedded CC report and a separate sonar makes sense.
> And this task depends on the successful build phases of compilation and 
> unit-test-pass. Means the completion of ticket EAGLE-131.



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

[jira] [Created] (EAGLE-147) Add checkstyle and jacoco plugin to eagle's pom.

[Michael Wu (JIRA)]

Michael Wu created EAGLE-147:


 Summary: Add checkstyle and jacoco plugin to eagle's pom.
 Key: EAGLE-147
 URL: https://issues.apache.org/jira/browse/EAGLE-147
 Project: Eagle
  Issue Type: Task
Reporter: Michael Wu
Assignee: Michael Wu






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

Re: [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25

[Michael Wu]

cool, thanks, Ralph!

On Wed, Feb 3, 2016 at 9:35 AM, Liangfei.Su  wrote:

> I will fix. The test case is about test the metric siddhi QL for hadoop
> metrics during policy development.
>
> On Wed, Feb 3, 2016 at 8:45 AM, Michael Wu  wrote:
>
> > Hi guys,
> >
> > This new build has new unit test failing:
> > org.apache.eagle.hadoop.metric.TestHadoopMetricSiddhiQL.testNameNodeLag
> > <
> >
> https://builds.apache.org/job/incubator-eagle-main/25/testReport/org.apache.eagle.hadoop.metric/TestHadoopMetricSiddhiQL/testNameNodeLag/
> > >
> >
> > Could anyone who own this case fix it please?
> >
> > Thanks,
> > Michael
> >
> > On Fri, Jan 29, 2016 at 12:15 PM, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> > > The Apache Jenkins build system has built incubator-eagle-main (build
> > #25)
> > > Status: Failure Check console output at
> > > https://builds.apache.org/job/incubator-eagle-main/25/ to view the
> > > results. Test Report is at: Test Result
> > > 
> >
>

Re: Release?

[Edward Zhang]

Hi Prasad,


Could you ask Eagle mentors to give the privileges of adding/editing a
wiki? Myself could not grant privilege.


Thanks

Edward

On Fri, Jan 22, 2016 at 2:03 PM, arunkarthick m 
wrote:

> I used to have administrator rights on the wiki. Not seeing the space admin
> button anymore. Will ask Edward once he is here.
>
> Thanks,
> Arun
>
> On Fri, Jan 22, 2016 at 1:50 PM, Prasad Mujumdar 
> wrote:
>
> >Looks like the formatting is bit messed up. My apologies. Hopefully it
> > will be better formatted on the wiki.
> >
> > thanks
> > Prasad
> >
> >
> > On Fri, Jan 22, 2016 at 1:48 PM, Prasad Mujumdar 
> > wrote:
> >
> > >
> > >@Julian, strong +1 to making release soon. Thanks for bring that up.
> > > @Ed and @Julien, we did some recent license cleanup (EAGLE-114). Based
> on
> > > my experience with other incubating project releases (as Julian
> > mentioned,
> > > primarily based on Justin's feedback in past) there some work that
> still
> > > needed. We EAGLE-115 to tracking that. I will try to prioritize
> getting a
> > > patch ready for that.
> > >
> > > Looks like we don't have a 'how to release' page that outlines the
> > release
> > > steps. Here's a draft that I put together (using some of the existing
> > > incubator project templates).
> > > @Ed and @Arun, if one of you could give me access to the wiki, I can
> > > upload the draft there so that community members can directly edit the
> > page.
> > >
> > >
> > > *How to Release*
> > >
> > > This document describes the release process for Apache Eagle release
> from
> > > Incubator. This is a working progress document till we have a few
> > releases
> > > and ironed out the process.
> > >
> > > *Release manager*
> > >
> > > Someone from the community should volunteer to become a release
> > > manager(RM) and coordinate the release process. The release steps
> listed
> > > below will mostly be carried out by the release manager. Ideally this
> > > person should be a committer or PPMC member, however it should be fine
> > for
> > > a contributor to take that responsibility with one of the committer or
> > PPMC
> > > to mentor him/her to make the release.
> > >
> > > The Release Manager (RM) must go through the policy document to
> > understand
> > > all the tasks and responsibilities of running a release.  Frequently
> > asked
> > > questions for making Apache releases are available on Releases FAQ
> > > page. Guide to Release
> > Management
> > > During Incubation
> > > <
> >
> http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager
> >
> > also
> > > has good information on best practices for releasing artifacts from an
> > > incubating Apache project.
> > >
> > >
> > >
> > > *Give a heads up*
> > >
> > > The RM should first create an umbrella issue to create the release and
> > > then setup a timeline for release branch point. The community should
> > decide
> > > on the cutoff point for the release branch on the release discussion
> > > thread.
> > >
> > > To: dev@eagle.incubator.apache.org
> > >
> > > Subject: Work on $release release has started
> > >
> > >
> > > Created a tracking jira (jira#) for the eagle $release and plan to
> branch
> > > tentatively on $date.
> > >
> > >
> > >
> > > What would you like to see included?
> > >
> > > Thanks,
> > >
> > > $RM
> > >
> > > *Sanitize JIRA*
> > >
> > >1. Before a release is done, make sure that any issues that are
> > >*fixed *have their fix version setup correctly. Run the following
> JIRA
> > >query to see which resolved issues do not have their fix version set
> > >up correctly:
> > >
> > >2. project = eagle and resolution = fixed and fixVersion is empty
> > >3.
> > >
> > >
> > >
> > >
> > >
> > >The result of the above query should be empty. If some issues do
> > >show up in this query that have been fixed since the last release,
> > >please bulk-edit them to set the fix version to ''.
> > >4. Move the unresolved jiras to the next release
> > >
> > >5. project = eagle and fixVersion =  and status not
> > >in( resolved, done, Accepted, Closed)
> > >6.
> > >
> > >
> > >
> > >7. You can also run the following query to make sure that the
> > >issues fixed for the to-be-released version look accurate:
> > >
> > >8. project = eagle and fixVersion = ''
> > >9.
> > >
> > >
> > >
> > >10. Finally, check out the output of the *JIRA release note tool*
> > ><
> >
> https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectName=eagle
> >
> > to
> > >see which JIRAs are included in the release, in order to do a sanity
> > check.
> > >
> > > *Creating Release Artifacts*
> > >
> > > *Communicate with the community*
> > >
> > >1.  Send an email to dev list to notify that you are about to
> > >branch. Ask to hold off any commits until this is finished.
> > >2. Send another email after branching is done.
> > >
> > > *Preparing b

Re: [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25

[Liangfei.Su]

I will fix. The test case is about test the metric siddhi QL for hadoop
metrics during policy development.

On Wed, Feb 3, 2016 at 8:45 AM, Michael Wu  wrote:

> Hi guys,
>
> This new build has new unit test failing:
> org.apache.eagle.hadoop.metric.TestHadoopMetricSiddhiQL.testNameNodeLag
> <
> https://builds.apache.org/job/incubator-eagle-main/25/testReport/org.apache.eagle.hadoop.metric/TestHadoopMetricSiddhiQL/testNameNodeLag/
> >
>
> Could anyone who own this case fix it please?
>
> Thanks,
> Michael
>
> On Fri, Jan 29, 2016 at 12:15 PM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > The Apache Jenkins build system has built incubator-eagle-main (build
> #25)
> > Status: Failure Check console output at
> > https://builds.apache.org/job/incubator-eagle-main/25/ to view the
> > results. Test Report is at: Test Result
> > 
>

Re: [VOTE]add committer into Eagle project

[Michael Wu]

+1

On Fri, Jan 29, 2016 at 11:55 AM, Krishna, Murali(AWF) 
wrote:

> +1
>
> - Murali Krishna
>
> -Original Message-
> From: Edward Zhang [mailto:yonzhang2...@apache.org]
> Sent: Tuesday, January 26, 2016 2:51 PM
> To: dev@eagle.incubator.apache.org; u...@eagle.incubator.apache.org
> Subject: [VOTE]add committer into Eagle project
>
> Hi Eagle Community,
>
> I would like to nominate Liangfei(Ralph), Su to be Eagle committer based
> on his continuous contribution in last 2 months. The detail is as follows:
>
> https://issues.apache.org/jira/browse/EAGLE-85
> https://issues.apache.org/jira/browse/EAGLE-88
> https://issues.apache.org/jira/browse/EAGLE-108
> https://issues.apache.org/jira/browse/EAGLE-128
> https://issues.apache.org/jira/browse/EAGLE-136
> https://issues.apache.org/jira/browse/EAGLE-79
>
>
> Among which, Eagle-79 metric aggregation siddhi support is a critical
> feature for Eagle to support declarative metric aggregation. Also Eagle-136
> hadoop metric monitoring is also an important feature for Eagle to monitor
> hadoop with jmx metric.
>
> Also Ralph active participated in various discussions and contributed some
> design documents for example
> https://cwiki.apache.org/confluence/display/EAG/Stream+Analyze.
>
> Please vote.
>
> Thanks
> Edward
>

Re: Work on Eagle 0.3.0 release has started

[Michael Wu]

Hi Edward,

Do you have a list of features that are planned to release in this version?
With the list, QE members could be aware of what to verify.

BTW, I don't know if we have it, but should eagle conform to any Release
Readiness Criteria?

Thanks,
Michael

On Tue, Feb 2, 2016 at 8:34 AM, Zhang, Edward (GDI Hadoop) <
yonzh...@ebay.com> wrote:

> Hi,
>
> This is a heads-up for creating Eagle release 0.3.0.
>
> Created a tracking jira https://issues.apache.org/jira/browse/EAGLE-143
> for the eagle 0.3.0 and plan to branch tentatively on 2/7.
>
> I will reference this wiki
> https://calcite.apache.org/docs/howto.html#making-a-release-for-calcite-committers,but
> Eagle mentors and contributors please correct me if something is wrong
> during this release.
>
> What would you like to see included?
>
> Thanks,
>
> Edward
>

Re: [EAGLE BUILD FAILED] incubator-eagle-main failed on build #25

[Michael Wu]

Hi guys,

This new build has new unit test failing:
org.apache.eagle.hadoop.metric.TestHadoopMetricSiddhiQL.testNameNodeLag


Could anyone who own this case fix it please?

Thanks,
Michael

On Fri, Jan 29, 2016 at 12:15 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

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

[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51577341
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

And the generic template parameter T is introduced for the purpose. I think 
we don't need to direct reference to AlertDefinitionAPIEntity here.


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51577341
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

And the generic template parameter T is introduced for the purpose. I think 
we don't need to direct reference to AlertDefinitionAPIEntity here.


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51576885
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Same as above, let us make 
PolicyDefinitionEntityDAO/PolicyDefinitionEntityDAOImpl not knowing specific 
subtype of alert definition. Ideally, all entity/daos that specific to Alerts 
should be refactor out from eagle-policies. We haven't achieve this goal, but 
let us keep it clear as much as possible


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51576885
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionEntityDAOImpl.java
 ---
@@ -17,14 +17,17 @@
 package org.apache.eagle.policy.dao;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Same as above, let us make 
PolicyDefinitionEntityDAO/PolicyDefinitionEntityDAOImpl not knowing specific 
subtype of alert definition. Ideally, all entity/daos that specific to Alerts 
should be refactor out from eagle-policies. We haven't achieve this goal, but 
let us keep it clear as much as possible


---
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: EAGLE-95 DAM HDFS topology fails to ...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51576194
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionDAO.java
 ---
@@ -21,6 +21,7 @@
 import java.util.Map;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Why need to have AlertDefinitionAPIEntity in PolicyDefinitionDAO? Ideally 
PolicyDefinitionDAO suppose not knowing any the specific subtype of 
AbstractPolicyDefinitionEntity. 


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51576194
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/PolicyDefinitionDAO.java
 ---
@@ -21,6 +21,7 @@
 import java.util.Map;
 
 import org.apache.eagle.alert.entity.AbstractPolicyDefinitionEntity;
+import org.apache.eagle.alert.entity.AlertDefinitionAPIEntity;
--- End diff --

Why need to have AlertDefinitionAPIEntity in PolicyDefinitionDAO? Ideally 
PolicyDefinitionDAO suppose not knowing any the specific subtype of 
AbstractPolicyDefinitionEntity. 


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[jira] [Commented] (EAGLE-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51575894
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
+   } finally {
+   try {
+   if (null != client)
+   client.close();
+   } catch (IOException exception) {
+   LOG.debug("Unable to close Eagle service 
client, " + exception.getMessage());
--- End diff --

Should the exception be error always? And please make sure not only the 
message is logged, but also the stack, you might want to pass the exception 
object to LOG here. 


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51575894
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
+   } finally {
+   try {
+   if (null != client)
+   client.close();
+   } catch (IOException exception) {
+   LOG.debug("Unable to close Eagle service 
client, " + exception.getMessage());
--- End diff --

Should the exception be error always? And please make sure not only the 
message is logged, but also the stack, you might want to pass the exception 
object to LOG here. 


---
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-95) DAM HDFS topology fails to start, if there is invalid policy.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-95:
-

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51575914
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
--- End diff --

Please make sure not only the message is logged, but also the stack, you 
might want to pass the exception object to LOG here. 


> DAM HDFS topology fails to start, if there is invalid policy.
> -
>
> Key: EAGLE-95
> URL: https://issues.apache.org/jira/browse/EAGLE-95
> Project: Eagle
>  Issue Type: Bug
>Reporter: hemanth dendukuri
>Assignee: Senthilkumar
>Priority: Critical
>
> Step 1: Create a invalid policy (from hdfsAuditLogEventStream[(cmd == 'open') 
> and (str:contains(src,'/tmp/p')==true)] select * insert into outputStream;) 
> Step 2 : Deploy Dam HDFS topology. 
> Actual : The HDFS topology could not start because of the invalid policy. 
> 2015-12-16 23:51:17 b.s.d.executor [INFO] Shutting down executor 
> AlertEntityDeduplicationExecutor_9:[2 2] 2015-12-16 23:51:17 b.s.util [INFO] 
> Async loop interrupted! 
> Expected: Topology should start ignoring the invalid policy.



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

[GitHub] incubator-eagle pull request: EAGLE-95 DAM HDFS topology fails to ...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/71#discussion_r51575914
  
--- Diff: 
eagle-core/eagle-policy/eagle-policy-base/src/main/java/org/apache/eagle/policy/dao/AlertDefinitionDAOImpl.java
 ---
@@ -83,4 +85,27 @@ public AlertDefinitionDAOImpl(EagleServiceConnector 
connector){
}
return map;
}
+
+   @Override
+   public void updatePolicyDetails(AlertDefinitionAPIEntity entity, 
boolean markdownEnabled, String markdownReason) {
+   IEagleServiceClient client = new 
EagleServiceClientImpl(connector);
+
+   List entityList = new ArrayList<>();
+   entity.setMarkdownReason(null != markdownReason ? 
markdownReason : "");
+   entity.setMarkdownEnabled(markdownEnabled);
+   entityList.add(entity);
+
+   try {
+   client.create(entityList, 
Constants.ALERT_DEFINITION_SERVICE_ENDPOINT_NAME);
+   } catch (IOException | EagleServiceClientException exception) {
+   LOG.error("Exception in updating markdown for policy in 
HBase", exception.getMessage());
--- End diff --

Please make sure not only the message is logged, but also the stack, you 
might want to pass the exception object to LOG here. 


---
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] [Created] (EAGLE-146) SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar

[Hao Chen (JIRA)]

Hao Chen created EAGLE-146:
--

 Summary: SiddhiExtensionLoader Error: viewing zip file for 
jar:./lib/ojdbc6.jar
 Key: EAGLE-146
 URL: https://issues.apache.org/jira/browse/EAGLE-146
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: 0.3.0


{code}
2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
siddhiCEPEngine
2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
MachineLearning
2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip 
file for jar:./lib/ojdbc6.jar
java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
at java.util.zip.ZipFile.open(Native Method) ~[na:1.7.0_60]
at java.util.zip.ZipFile.(ZipFile.java:215) ~[na:1.7.0_60]
at java.util.zip.ZipFile.(ZipFile.java:145) ~[na:1.7.0_60]
at java.util.zip.ZipFile.(ZipFile.java:159) ~[na:1.7.0_60]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromJarFile(SiddhiExtensionLoader.java:111)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:82)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.getResources(SiddhiExtensionLoader.java:71)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.util.SiddhiExtensionLoader.loadSiddhiExtensions(SiddhiExtensionLoader.java:51)
 [stormjar.jar:na]
at 
org.wso2.siddhi.core.config.SiddhiContext.(SiddhiContext.java:35) 
[stormjar.jar:na]
at org.wso2.siddhi.core.SiddhiManager.(SiddhiManager.java:40) 
[stormjar.jar:na]
at 
org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.createSiddhiRuntime(SiddhiPolicyEvaluator.java:108)
 [stormjar.jar:na]
at 
org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.init(SiddhiPolicyEvaluator.java:83)
 [stormjar.jar:na]
at 
org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.(SiddhiPolicyEvaluator.java:79)
 [stormjar.jar:na]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method) [na:1.7.0_60]
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 [na:1.7.0_60]
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 [na:1.7.0_60]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
[na:1.7.0_60]
at 
org.apache.eagle.policy.executor.PolicyProcessExecutor.createPolicyEvaluator(PolicyProcessExecutor.java:243)
 [stormjar.jar:na]
at 
org.apache.eagle.policy.executor.PolicyProcessExecutor.init(PolicyProcessExecutor.java:188)
 [stormjar.jar:na]
at 
org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
 [stormjar.jar:na]
at 
backtype.storm.daemon.executor$fn__5697$fn__5710.invoke(executor.clj:732) 
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463) 
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip 
file for jar:./lib/ojdbc6.jar
java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
{code}



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

[jira] [Created] (EAGLE-145) Send mail failed for javax.mail.internet.AddressException: Illegal semicolon, not in group

[Hao Chen (JIRA)]

Hao Chen created EAGLE-145:
--

 Summary: Send mail failed for 
javax.mail.internet.AddressException: Illegal semicolon, not in group
 Key: EAGLE-145
 URL: https://issues.apache.org/jira/browse/EAGLE-145
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: 0.3.0


{code}
2016-02-02 02:52:03 o.a.e.p.e.PolicyProcessExecutor [INFO] Detected 1 alerts 
for policy missingBlockPolicy
2016-02-02 02:52:03 o.a.e.m.r.EagleServiceReporterMetricListener [INFO] Wrote 1 
entities to service
2016-02-02 02:52:03 o.a.e.a.p.EaglePersist [INFO] Going to persist entities, 
type:  AlertAPIEntity, list size: 1
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Initialized 
Thread-4-AlertNotificationExecutor_10: origin is : 
druid-test-host1-556191.slc01.dev.ebayc3.com(pid:14052), recipient of the 
email: li...@ebay.com;hch...@ebay.com, velocity TPL file: ALERT_DEFAULT.vm
2016-02-02 02:52:03 o.a.e.a.n.AlertEmailGenerator [INFO] Sending email  in 
asynchronous to: h...@apache.org, cc: null
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sending email, tried: 1, 
max: 3
2016-02-02 02:52:03 STDIO [INFO] DEBUG: setDebug: JavaMail version 1.4ea
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Env is: prod
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] After calling 
generateCommonContext...
2016-02-02 02:52:03 o.a.velocity [ERROR] ResourceManager : unable to find 
resource 'templates/ALERT_DEFAULT.vm' in any resource loader.
2016-02-02 02:52:03 o.a.e.c.e.EagleMailClient [INFO] Send mail failed, got an 
AddressException: Illegal semicolon, not in group
javax.mail.internet.AddressException: Illegal semicolon, not in group
at javax.mail.internet.InternetAddress.parse(InternetAddress.java:780) 
~[stormjar.jar:na]
at javax.mail.internet.InternetAddress.parse(InternetAddress.java:555) 
~[stormjar.jar:na]
at javax.mail.internet.InternetAddress.parse(InternetAddress.java:532) 
~[stormjar.jar:na]
at 
org.apache.eagle.common.email.EagleMailClient._send(EagleMailClient.java:104) 
[stormjar.jar:na]
at 
org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:167) 
[stormjar.jar:na]
at 
org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:187) 
[stormjar.jar:na]
at 
org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:193) 
[stormjar.jar:na]
at 
org.apache.eagle.alert.common.AlertEmailSender.run(AlertEmailSender.java:129) 
[stormjar.jar:na]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
[na:1.7.0_60]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
[na:1.7.0_60]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
[na:1.7.0_60]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
[na:1.7.0_60]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Success of sending email: 
false
2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sleep for a while before 
retrying
{code}



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

[jira] [Assigned] (EAGLE-144) Support activity monitoring for Knox

[Senthilkumar (JIRA)]

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

Senthilkumar reassigned EAGLE-144:
--

Assignee: Senthilkumar

> Support activity monitoring for Knox
> 
>
> Key: EAGLE-144
> URL: https://issues.apache.org/jira/browse/EAGLE-144
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Senthilkumar
>Assignee: Senthilkumar
>
> The Knox Gateway provides a single access point for all REST interactions 
> with Hadoop clusters. It will be valuable to monitor the access events 
> happening in knox gateway and see if there is an anomaly and generate an 
> alert.



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

[jira] [Created] (EAGLE-144) Support activity monitoring for Knox

[Senthilkumar (JIRA)]

Senthilkumar created EAGLE-144:
--

 Summary: Support activity monitoring for Knox
 Key: EAGLE-144
 URL: https://issues.apache.org/jira/browse/EAGLE-144
 Project: Eagle
  Issue Type: New Feature
Reporter: Senthilkumar


The Knox Gateway provides a single access point for all REST interactions with 
Hadoop clusters. It will be valuable to monitor the access events happening in 
knox gateway and see if there is an anomaly and generate an alert.



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

[jira] [Commented] (EAGLE-144) Support activity monitoring for Knox

[Senthilkumar (JIRA)]

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

Senthilkumar commented on EAGLE-144:


Comments from John Scheibmeir:

Brainstorming a little here with regard to desired end state.

Knox proxy is employed on several hosts behind a load balancer.

Each proxy instance forwards its auditing data to a central activity monitor 
(ala Eagle). Eagle may treat the multiple inputs as single logical stream for 
criteria evaluation.

Eagle would understand the Knox audit file format.

Within Eagle I would either leverage standard activity monitor patterns if they 
exist or code new items for Knox.

Example patterns could include:
1) more than x failed logon attempts for same user within y amount of time from 
same endpoint (knox client) [brute force password]
2) more than x failed logon attempts for mutliple users within y amount of time 
from same endpoint (knox client) [brute force user/password]
3) more than x permission errors for single user or single endpoint within y 
amount of time [probing data paths potentially for data to steal]
4) more than x bytes transferred out via knox (?? - is this audited in knox) 
[improperly extracting or stealing data]

Eagle may also reformat logs into standard format (e.g. Splunk) and forward 
accordingly such that other systems may also leverage data/etc


> Support activity monitoring for Knox
> 
>
> Key: EAGLE-144
> URL: https://issues.apache.org/jira/browse/EAGLE-144
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Senthilkumar
>
> The Knox Gateway provides a single access point for all REST interactions 
> with Hadoop clusters. It will be valuable to monitor the access events 
> happening in knox gateway and see if there is an anomaly and generate an 
> alert.



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