date:20170613

[jira] [Created] (EAGLE-1042) Metrics preview support metric name display

2017-06-13 Thread Jilin, Jiang (JIRA)

Jilin, Jiang created EAGLE-1042:
---

 Summary: Metrics preview support metric name display
 Key: EAGLE-1042
 URL: https://issues.apache.org/jira/browse/EAGLE-1042
 Project: Eagle
  Issue Type: Improvement
Reporter: Jilin, Jiang
Assignee: Jilin, Jiang
Priority: Critical


For metric preview page. There should be display the title of the chart for 
quick snapshot



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-1037) Add alertDeduplication configurations on Eagle UI

2017-06-13 Thread Jilin, Jiang (JIRA)


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

Jilin, Jiang resolved EAGLE-1037.
-
Resolution: Fixed

> Add alertDeduplication configurations on Eagle UI
> -
>
> Key: EAGLE-1037
> URL: https://issues.apache.org/jira/browse/EAGLE-1037
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.6.0
>Reporter: Zhao, Qingwen
>Assignee: Jilin, Jiang
>Priority: Critical
>
> Add alertDeduplication configurations on Eagle UI
> Here is the sample policy
> {code}
> {
> "name": "capacityUsage",
> "description": "Policy for 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CAPACITY_USAGE_OUT",
> "inputStreams": [
>   "HADOOP_JMX_METRIC_STREAM_SANDBOX"
> ],
> "outputStreams": [
>   "HADOOP_JMX_METRIC_STREAM_SANDBOX_CAPACITY_USAGE_OUT"
> ],
> "siteId": "sandbox",
> "definition": {
>   "type": "siddhi",
>   "value": "from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> \"hadoop.namenode.fsnamesystemstate.capacityusage\" and convert(value, 
> \"long\") > 90]select site, host, component, metric, convert(value, \"long\") 
> as value, timestamp insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CAPACITY_USAGE_OUT;",
>   "handlerClass": null,
>   "properties": {},
>   "inputStreams": [],
>   "outputStreams": []
> },
> "stateDefinition": null,
> "policyStatus": "ENABLED",
> "alertDefinition": {
>   "templateType": "TEXT",
>   "subject": "$site capacity exceeds 90%",
>   "body": "$site capacity exceeds 90%",
>   "severity": "WARNING",
>   "category": "HDFS"
> },
> "alertDeduplications": [
>   {
> "outputStreamId": 
> "HADOOP_JMX_METRIC_STREAM_SANDBOX_CAPACITY_USAGE_OUT",
> "dedupIntervalMin": "1",
> "dedupFields": [
>   "site",
>   "component",
>   "host",
>   "metric"
> ]
>   }
> ],
> "partitionSpec": [
>   {
> "streamId": "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> "type": "SHUFFLE",
> "columns": [],
> "sortSpec": null
>   }
> ],
> "dedicated": false,
> "parallelismHint": 5,
> "alertSeverity": "WARNING",
> "alertCategory": "HDFS"
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EAGLE-1041) Support policy processing pipeline

2017-06-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-1041:
---

Github user zombieJ commented on the issue:

https://github.com/apache/eagle/pull/947
  
Remove `console` & LGTM


> Support policy processing pipeline
> --
>
> Key: EAGLE-1041
> URL: https://issues.apache.org/jira/browse/EAGLE-1041
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> In some cases, like increment or decrement pattern, data need to be processed 
> in more than one stage. For example, alert if the metric value increases by 
> N. Two steps to get the right alert.
> 1. sort & filter events which meet the filter conditions.
> 2. define data change pattern. 
> Here is a sample policy
> {code}
> fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
>  select * group by site,host,component, metric insert into temp;
> from every 
> a=HADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"],
> b=HADOOP_JMX_METRIC_STREAM_SANDBOX[b.component==a.component and 
> b.metric==a.metric and b.host==a.host and b.value>a.value and a.value>100]
> select b.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks, 
> a.value as oldNumOfMissingBlocks, (b.value-a.value) as 
> increastedNumOfMissingBlocks insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
> {code}
> There are two queries in this policy. The first one with the time window 
> condition tells Eagle to sort the original events. The second one defines the 
> data pattern. As the constraint of Siddhi syntax 
> (https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1#SiddhiQLGuide3.1-Pattern),
>  the filtering of input events does not work. 
> Luckily, if we put the output stream of the first query as the input stream 
> of the second query, it works. That's the problem this ticket tries to solve. 
> Ideally, the right policy can be written as 
> {code}
> fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
>  select * group by site,host,component, metric insert into MISSING_BLOCK_OUT;
> from every a=MISSING_BLOCK_OUT[metric=="hadoop.namenode.dfs.missingblocks"],
> b=MISSING_BLOCK_OUT[b.component==a.component and b.metric==a.metric and 
> b.host==a.host and b.value>a.value and a.value>100]
> select b.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks, 
> a.value as oldNumOfMissingBlocks, (b.value-a.value) as 
> increastedNumOfMissingBlocks insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] eagle issue #947: EAGLE-1041: Support policy processing pipeline

2017-06-13 Thread zombieJ

Github user zombieJ commented on the issue:

https://github.com/apache/eagle/pull/947
  
Remove `console` & 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.
---

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

2017-06-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-968:
--

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

https://github.com/apache/eagle/pull/941#discussion_r121674184
  
--- Diff: 
eagle-core/eagle-common/src/main/java/org/apache/eagle/common/mail/EagleMailClient.java
 ---
@@ -53,16 +53,18 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS, 
Log4JLogChute.class.getName());
--- End diff --

@jhsenjaliya fixed


> using Email Notification Feature throws IncompatibleClassChangeError
> 
>
> Key: EAGLE-968
> URL: https://issues.apache.org/jira/browse/EAGLE-968
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> {code}
> 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator 
> Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to 
> @gmail.com,@gmail.com, due 
> to:java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
> java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> ~[?:1.8.0_102]
>   at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> ~[?:1.8.0_102]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92)
>  [stormjar.jar:?]
>   at 
> org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846)
>  [storm-core-1.0.3.jar:1.0.3]
>   at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) 
> [storm-core-1.0.3.jar:1.0.3]
>   at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
>   at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
> Caused by: java.lang.IncompatibleClassChangeError: Implementing class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:763) 
> ~[?:1.8.0_102]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:73) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:361) 
> ~[?:1.8.0_102]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
>

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

2017-06-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-968:
--

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

https://github.com/apache/eagle/pull/941#discussion_r121674160
  
--- Diff: 
eagle-core/eagle-common/src/main/java/org/apache/eagle/common/mail/EagleMailClient.java
 ---
@@ -53,16 +53,18 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS, 
Log4JLogChute.class.getName());
+
velocityEngine.setProperty("runtime.log.logsystem.log4j.logger", LOG.getName());
 velocityEngine.init();
 
 config.put("mail.transport.protocol", "smtp");
 if 
(Boolean.parseBoolean(config.getProperty(AlertEmailConstants.CONF_MAIL_AUTH))) {
 session = Session.getInstance(config, new Authenticator() {
 protected PasswordAuthentication 
getPasswordAuthentication() {
 return new PasswordAuthentication(
-
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
-
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
-);
+
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
--- End diff --

@jhsenjaliya fixed


> using Email Notification Feature throws IncompatibleClassChangeError
> 
>
> Key: EAGLE-968
> URL: https://issues.apache.org/jira/browse/EAGLE-968
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> {code}
> 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator 
> Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to 
> @gmail.com,@gmail.com, due 
> to:java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
> java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> ~[?:1.8.0_102]
>   at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> ~[?:1.8.0_102]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92)
>  [stormjar.jar:?]
>   at 
> org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846)
>  [storm-core-1.0.3.jar:1.0.3]
>   at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) 
> [storm-core-1.0.3.jar:1.0.3]
>   at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
>   at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
> Caused by: java.lang.IncompatibleClassChangeError: Implementing class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102]
>   at

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

2017-06-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-968:
--

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

https://github.com/apache/eagle/pull/941#discussion_r121674210
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
 ---
@@ -54,23 +54,24 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS,Log4JLogChute.class.getName());
+
velocityEngine.setProperty("runtime.log.logsystem.log4j.logger", LOG.getName());
 velocityEngine.init();
 
 config.put("mail.transport.protocol", "smtp");
 if 
(Boolean.parseBoolean(config.getProperty(AlertEmailConstants.CONF_MAIL_AUTH))) {
 session = Session.getInstance(config, new Authenticator() {
 protected PasswordAuthentication 
getPasswordAuthentication() {
 return new PasswordAuthentication(
-
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
-
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
-);
+
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
+
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
+);
 }
 });
 } else {
 session = Session.getInstance(config, new Authenticator() {
 });
 }
-
--- End diff --

@jhsenjaliya fixed


> using Email Notification Feature throws IncompatibleClassChangeError
> 
>
> Key: EAGLE-968
> URL: https://issues.apache.org/jira/browse/EAGLE-968
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> {code}
> 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator 
> Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to 
> @gmail.com,@gmail.com, due 
> to:java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
> java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> ~[?:1.8.0_102]
>   at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> ~[?:1.8.0_102]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92)
>  [stormjar.jar:?]
>   at 
> org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846)
>  [storm-core-1.0.3.jar:1.0.3]
>

[GitHub] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

2017-06-13 Thread rushikesavareddy

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

https://github.com/apache/eagle/pull/941#discussion_r121674223
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
 ---
@@ -54,23 +54,24 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS,Log4JLogChute.class.getName());
+
velocityEngine.setProperty("runtime.log.logsystem.log4j.logger", LOG.getName());
 velocityEngine.init();
 
 config.put("mail.transport.protocol", "smtp");
 if 
(Boolean.parseBoolean(config.getProperty(AlertEmailConstants.CONF_MAIL_AUTH))) {
 session = Session.getInstance(config, new Authenticator() {
 protected PasswordAuthentication 
getPasswordAuthentication() {
 return new PasswordAuthentication(
-
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
-
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
-);
+
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
--- End diff --

@jhsenjaliya fixed


---
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] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

2017-06-13 Thread rushikesavareddy

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

https://github.com/apache/eagle/pull/941#discussion_r121674210
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
 ---
@@ -54,23 +54,24 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS,Log4JLogChute.class.getName());
+
velocityEngine.setProperty("runtime.log.logsystem.log4j.logger", LOG.getName());
 velocityEngine.init();
 
 config.put("mail.transport.protocol", "smtp");
 if 
(Boolean.parseBoolean(config.getProperty(AlertEmailConstants.CONF_MAIL_AUTH))) {
 session = Session.getInstance(config, new Authenticator() {
 protected PasswordAuthentication 
getPasswordAuthentication() {
 return new PasswordAuthentication(
-
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
-
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
-);
+
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
+
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
+);
 }
 });
 } else {
 session = Session.getInstance(config, new Authenticator() {
 });
 }
-
--- End diff --

@jhsenjaliya fixed


---
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] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

2017-06-13 Thread rushikesavareddy

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

https://github.com/apache/eagle/pull/941#discussion_r121674160
  
--- Diff: 
eagle-core/eagle-common/src/main/java/org/apache/eagle/common/mail/EagleMailClient.java
 ---
@@ -53,16 +53,18 @@ public EagleMailClient(final Properties config) {
 velocityEngine = new VelocityEngine();
 velocityEngine.setProperty(RuntimeConstants.RESOURCE_LOADER, 
"classpath");
 velocityEngine.setProperty("classpath.resource.loader.class", 
ClasspathResourceLoader.class.getName());
+
velocityEngine.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS, 
Log4JLogChute.class.getName());
+
velocityEngine.setProperty("runtime.log.logsystem.log4j.logger", LOG.getName());
 velocityEngine.init();
 
 config.put("mail.transport.protocol", "smtp");
 if 
(Boolean.parseBoolean(config.getProperty(AlertEmailConstants.CONF_MAIL_AUTH))) {
 session = Session.getInstance(config, new Authenticator() {
 protected PasswordAuthentication 
getPasswordAuthentication() {
 return new PasswordAuthentication(
-
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
-
config.getProperty(AlertEmailConstants.CONF_AUTH_PASSWORD)
-);
+
config.getProperty(AlertEmailConstants.CONF_AUTH_USER),
--- End diff --

@jhsenjaliya fixed


---
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] eagle pull request #947: EAGLE-1041: Support policy processing pipeline

2017-06-13 Thread qingwen220

GitHub user qingwen220 opened a pull request:

https://github.com/apache/eagle/pull/947

EAGLE-1041: Support policy processing pipeline

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

Two updates:
* if an inputStream is an intermediate stream (defined by select clause 
statement), then remove it from inputStream list and outputStream list
* if an inputStream is an intermediate stream, remove its PartitionSpec 

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

$ git pull https://github.com/qingwen220/eagle EAGLE-1041

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

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


commit ea47b849700a89e15bc6a2e6b28317ee7a50b315
Author: Zhao, Qingwen 
Date:   2017-06-13T12:22:15Z

update alertEditCtrl.js




---
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-1041) Support policy processing pipeline

2017-06-13 Thread Zhao, Qingwen (JIRA)

Zhao, Qingwen created EAGLE-1041:


 Summary: Support policy processing pipeline
 Key: EAGLE-1041
 URL: https://issues.apache.org/jira/browse/EAGLE-1041
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen


In some cases, like increment or decrement pattern, data need to be processed 
in more than one stage. For example, alert if the metric value increases by N. 
Two steps to get the right alert.
1. sort & filter events which meet the filter conditions.
2. define data change pattern. 

Here is a sample policy
{code}
fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
 select * group by site,host,component, metric insert into temp;
from every 
a=HADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"],
b=HADOOP_JMX_METRIC_STREAM_SANDBOX[b.component==a.componentandb.metric==a.metricandb.host==a.hostandb.value>a.valueanda.value>100]
selectb.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks, 
a.value as oldNumOfMissingBlocks, (b.value-a.value) as 
increastedNumOfMissingBlocks insert into 
HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
{code}

There are two queries in this policy. The first one with the time window 
condition tells Eagle to sort the original events. The second one defines the 
data pattern. As the constraint of Siddhi syntax 
(https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1#SiddhiQLGuide3.1-Pattern),
 the filtering of input events does not work. 

Luckily, if we put the output stream of the first query as the input stream of 
the second query, it works. That's the problem this ticket tries to solve. 

Ideally, the right policy can be written as 
{code}
fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
 select * group by site,host,component, metric insert into MISSING_BLOCK_OUT;
from every a=MISSING_BLOCK_OUT[metric=="hadoop.namenode.dfs.missingblocks"],
b=MISSING_BLOCK_OUT[b.component==a.componentandb.metric==a.metricandb.host==a.hostandb.value>a.valueanda.value>100]
selectb.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks, 
a.value as oldNumOfMissingBlocks, (b.value-a.value) as 
increastedNumOfMissingBlocks insert into 
HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (EAGLE-1040) Metric

2017-06-13 Thread Zhao, Qingwen (JIRA)


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

Zhao, Qingwen closed EAGLE-1040.

Resolution: Not A Problem

> Metric
> --
>
> Key: EAGLE-1040
> URL: https://issues.apache.org/jira/browse/EAGLE-1040
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>
> In the metric preview page(/#/metric/preview), users can choose host and value



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (EAGLE-1042) Metrics preview support metric name display

[jira] [Resolved] (EAGLE-1037) Add alertDeduplication configurations on Eagle UI

[jira] [Commented] (EAGLE-1041) Support policy processing pipeline

[GitHub] eagle issue #947: EAGLE-1041: Support policy processing pipeline

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

[GitHub] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

[GitHub] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

[GitHub] eagle pull request #941: [EAGLE-968] Fix for email issue in 0.5 eagle versio...

[GitHub] eagle pull request #947: EAGLE-1041: Support policy processing pipeline

[jira] [Created] (EAGLE-1041) Support policy processing pipeline

[jira] [Closed] (EAGLE-1040) Metric

13 matches

Site Navigation

Mail list logo

Footer information