[jira] [Created] (EAGLE-756) metadata change (with coordinator build) in publishment is not sent to runtime bolts
Zeng, Bryant created EAGLE-756: -- Summary: metadata change (with coordinator build) in publishment is not sent to runtime bolts Key: EAGLE-756 URL: https://issues.apache.org/jira/browse/EAGLE-756 Project: Eagle Issue Type: Bug Reporter: Zeng, Bryant Assignee: Zeng, Bryant During test Alert Engine publisher, it looks like when we have slack publishment, the metadata reload become slow refreshed when use change the metadata and manually trigger the coordinator schedule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-683) AlertEngine : Improve metadata store performance
[ https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant updated EAGLE-683: --- Summary: AlertEngine : Improve metadata store performance (was: AlertEngine : use capped collection for mongodb schedule specs, keep last 1000) > AlertEngine : Improve metadata store performance > > > Key: EAGLE-683 > URL: https://issues.apache.org/jira/browse/EAGLE-683 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant > Fix For: v0.5.0 > > > Currently, we enable periodically schedule in coordinator service itself. If > this is enabled, the schedule spec will finally used up metadata storage. > We should > 1. Disable periodically schedule by default (storage like mysql doesn't have > capped feature) > 2. For mongodb storage, use capped collection for schedule_specs, > policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams, > spoutSpecs (all schedule spec related collection). > Let use default config of 20,000 as capped collection size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-671) AlertEngine: incorrect metric system use : too many metric object create and registered
[ https://issues.apache.org/jira/browse/EAGLE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-671. -- > AlertEngine: incorrect metric system use : too many metric object create and > registered > --- > > Key: EAGLE-671 > URL: https://issues.apache.org/jira/browse/EAGLE-671 > Project: Eagle > Issue Type: Task >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant > Fix For: v0.5.0 > > > In AlertBolt: we should register one metric to metric system, then use the > metric object to send metric. Not every-time register the metric to metric > systm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK
[ https://issues.apache.org/jira/browse/EAGLE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-616. -- Resolution: Fixed > AlertEngine: Reduce the connection from alert-service to ZK > --- > > Key: EAGLE-616 > URL: https://issues.apache.org/jira/browse/EAGLE-616 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > In QA, it used to show too much connection from alert-service to zookeeper. > We only use zk for exclusive lock and spec version notify, should not have so > much connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK
Zeng, Bryant created EAGLE-616: -- Summary: AlertEngine: Reduce the connection from alert-service to ZK Key: EAGLE-616 URL: https://issues.apache.org/jira/browse/EAGLE-616 Project: Eagle Issue Type: Bug Reporter: Zeng, Bryant Assignee: Zeng, Bryant In QA, it used to show too much connection from alert-service to zookeeper. We only use zk for exclusive lock and spec version notify, should not have so much connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-614) NPE in DynamicPolicyLoader
[ https://issues.apache.org/jira/browse/EAGLE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-614. -- Resolution: Fixed > NPE in DynamicPolicyLoader > -- > > Key: EAGLE-614 > URL: https://issues.apache.org/jira/browse/EAGLE-614 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Find exception as below: > INFO [2016-10-13 01:15:02,965] > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: policies > loader start. > INFO [2016-10-13 01:15:02,966] > org.apache.eagle.alert.service.MetadataServiceClientImpl: query URL > http://localhost:8080/rest/metadata/policies > ERROR [2016-10-13 01:15:02,972] > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: error loading > policy, but continue to run > ! java.lang.NullPointerException: null > ! at > org.apache.eagle.alert.engine.coordinator.PolicyDefinition.equals(PolicyDefinition.java:150) > ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.jar > :0.5.0-incubating-SNAPSHOT] > ! at > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader.run(DynamicPolicyLoader.java:69) > ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded. > jar:0.5.0-incubating-SNAPSHOT] > ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_102] > ! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_102] > ! at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_102] > ! at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [na:1.8.0_102] > ! at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_102] > ! at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_102] > ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102] > we have compare null with other object which should be avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-614) NPE in DynamicPolicyLoader
[ https://issues.apache.org/jira/browse/EAGLE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant updated EAGLE-614: --- Summary: NPE in DynamicPolicyLoader (was: NPE Exception in DynamicPolicyLoader) > NPE in DynamicPolicyLoader > -- > > Key: EAGLE-614 > URL: https://issues.apache.org/jira/browse/EAGLE-614 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Find exception as below: > INFO [2016-10-13 01:15:02,965] > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: policies > loader start. > INFO [2016-10-13 01:15:02,966] > org.apache.eagle.alert.service.MetadataServiceClientImpl: query URL > http://localhost:8080/rest/metadata/policies > ERROR [2016-10-13 01:15:02,972] > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: error loading > policy, but continue to run > ! java.lang.NullPointerException: null > ! at > org.apache.eagle.alert.engine.coordinator.PolicyDefinition.equals(PolicyDefinition.java:150) > ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.jar > :0.5.0-incubating-SNAPSHOT] > ! at > org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader.run(DynamicPolicyLoader.java:69) > ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded. > jar:0.5.0-incubating-SNAPSHOT] > ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_102] > ! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_102] > ! at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_102] > ! at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [na:1.8.0_102] > ! at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_102] > ! at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_102] > ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102] > we have compare null with other object which should be avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-614) NPE Exception in DynamicPolicyLoader
Zeng, Bryant created EAGLE-614: -- Summary: NPE Exception in DynamicPolicyLoader Key: EAGLE-614 URL: https://issues.apache.org/jira/browse/EAGLE-614 Project: Eagle Issue Type: Bug Reporter: Zeng, Bryant Assignee: Zeng, Bryant Find exception as below: INFO [2016-10-13 01:15:02,965] org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: policies loader start. INFO [2016-10-13 01:15:02,966] org.apache.eagle.alert.service.MetadataServiceClientImpl: query URL http://localhost:8080/rest/metadata/policies ERROR [2016-10-13 01:15:02,972] org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader: error loading policy, but continue to run ! java.lang.NullPointerException: null ! at org.apache.eagle.alert.engine.coordinator.PolicyDefinition.equals(PolicyDefinition.java:150) ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded.jar :0.5.0-incubating-SNAPSHOT] ! at org.apache.eagle.alert.coordinator.trigger.DynamicPolicyLoader.run(DynamicPolicyLoader.java:69) ~[alert-service-0.5.0-incubating-SNAPSHOT-shaded. jar:0.5.0-incubating-SNAPSHOT] ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_102] ! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_102] ! at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_102] ! at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_102] ! at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_102] ! at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_102] ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102] we have compare null with other object which should be avoided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-602) Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event Version [null]!
[ https://issues.apache.org/jira/browse/EAGLE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant updated EAGLE-602: --- Description: Just find exception as below: 2016-10-06 22:51:41 org.apache.eagle.alert.engine.runner.AlertBolt [WARN] Spec Version [spec_version_1475817732537] of AlertBolt is newer than Stream Event Version [null]! Seems there's an error when get meta version from stream event or initialising failed when stream event version is null. was: Just find exception as below: Spec Version [spec_version_1475817732537] of AlertBolt is newer than Stream Event Version [null]! Seems there's an error when get meta version from stream event or initialising failed when stream event version is null. > Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event > Version [null]! > - > > Key: EAGLE-602 > URL: https://issues.apache.org/jira/browse/EAGLE-602 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Just find exception as below: > 2016-10-06 22:51:41 org.apache.eagle.alert.engine.runner.AlertBolt [WARN] > Spec Version [spec_version_1475817732537] of AlertBolt is newer than Stream > Event Version [null]! > Seems there's an error when get meta version from stream event or > initialising failed when stream event version is null. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-602) Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event Version [null]!
Zeng, Bryant created EAGLE-602: -- Summary: Exception that Spec Version [xxx] of AlertBolt is newer than Stream Event Version [null]! Key: EAGLE-602 URL: https://issues.apache.org/jira/browse/EAGLE-602 Project: Eagle Issue Type: Bug Reporter: Zeng, Bryant Assignee: Zeng, Bryant Just find exception as below: Spec Version [spec_version_1475817732537] of AlertBolt is newer than Stream Event Version [null]! Seems there's an error when get meta version from stream event or initialising failed when stream event version is null. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-471) AlertBolt introduce un-serializble member
[ https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant updated EAGLE-471: --- Description: Exception is as below: 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set topology.message.timeout.secs as 3600 Exception in thread "main" java.lang.RuntimeException: java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor at backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43) at backtype.storm.utils.Utils.serialize(Utils.java:85) at backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193) at org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) Caused by: java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15] It seems there's some member in AlertBolt which is not serialized. was: AlerBolt.executors 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set topology.message.timeout.secs as 3600 Exception in thread "main" java.lang.RuntimeException: java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor at backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43) at backtype.storm.utils.Utils.serialize(Utils.java:85) at backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168) at org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193) at org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) Caused by: java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15] idea里跑UnitTopologyMain > AlertBolt introduce un-serializble member > -- > > Key: EAGLE-471 > URL: https://issues.apache.org/jira/browse/EAGLE-471 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant >Priority: Blocker > > Exception is as below: > 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set > topology.message.timeout.secs as 3600 > Exception in thread "main" java.lang.RuntimeException: > java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor >at >
[jira] [Reopened] (EAGLE-471) AlertBolt introduce un-serializble member
[ https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant reopened EAGLE-471: > AlertBolt introduce un-serializble member > -- > > Key: EAGLE-471 > URL: https://issues.apache.org/jira/browse/EAGLE-471 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant >Priority: Blocker > > AlerBolt.executors > 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set > topology.message.timeout.secs as 3600 > Exception in thread "main" java.lang.RuntimeException: > java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor >at > backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43) > at backtype.storm.utils.Utils.serialize(Utils.java:85) > at > backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193) > at > org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > Caused by: java.io.NotSerializableException: > java.util.concurrent.ThreadPoolExecutor > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) > at > backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15] > > idea里跑UnitTopologyMain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-570) Refactor: Make sure engine publisher only have general feature.
[ https://issues.apache.org/jira/browse/EAGLE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-570. -- Resolution: Fixed > Refactor: Make sure engine publisher only have general feature. > --- > > Key: EAGLE-570 > URL: https://issues.apache.org/jira/browse/EAGLE-570 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant > Fix For: v0.5.0 > > > Eagle-567 intend to provide better formatting of slack channel message. But > the implementation introduce too much specific logic that beyond a common > alerting engine should have. > Need to refactor to move the specific logic to either vendor specific > extension or have configurable formatting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-595) Make Alert Slack Publisher more generic
[ https://issues.apache.org/jira/browse/EAGLE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-595. -- Resolution: Duplicate duplicate with https://issues.apache.org/jira/browse/EAGLE-570 > Make Alert Slack Publisher more generic > --- > > Key: EAGLE-595 > URL: https://issues.apache.org/jira/browse/EAGLE-595 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Original Slack Publisher has some specific logic like defined field names. To > make it more generic, need to move all of them out, and make it simple for > user to extend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-595) Make Alert Slack Publisher more generic
Zeng, Bryant created EAGLE-595: -- Summary: Make Alert Slack Publisher more generic Key: EAGLE-595 URL: https://issues.apache.org/jira/browse/EAGLE-595 Project: Eagle Issue Type: Improvement Reporter: Zeng, Bryant Assignee: Zeng, Bryant Original Slack Publisher has some specific logic like defined field names. To make it more generic, need to move all of them out, and make it simple for user to extend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-567) Enhance Slack publish format
Zeng, Bryant created EAGLE-567: -- Summary: Enhance Slack publish format Key: EAGLE-567 URL: https://issues.apache.org/jira/browse/EAGLE-567 Project: Eagle Issue Type: Improvement Reporter: Zeng, Bryant Assignee: Zeng, Bryant Currently message publish to Slack is raw String, and this is not very clear for user. So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-550) Add Alert publish implementation for Slack
[
https://issues.apache.org/jira/browse/EAGLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zeng, Bryant updated EAGLE-550:
---
Description:
Add one more publish implement (Slack) for Alert.
How to implement
1. Here uses a lib "simple-slack-api" to connecting to Slack and publish alert
messages to Slack.
2. Add one more publisher of Slack which extends "AbstractPublishPlugin" to
process received AlertStreamEvent, and according to Slack config which defined
in publishment.json to send messages.
How to use
1. Create a bot user in Slack, and remember its token.
2. Create some channels if you want send messages to if they do not exist.
3. Add your bot user to these channels.
4. Then define Slack config and declare to use Slack publisher in config file
such as below (Especially the "type" and "properties". Here urltemplate will
form an output url link based on docId if downstream have it.), we can use it
very easily:
{
"name": "test-slack-output",
"type": "org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher",
"policyIds": [
"switch_check"
],
"properties": {
"token": "your token",
"channels": "your channel1, your channel2",
"severitys": "CRITICAL",
"urltemplate": "your template/?id=%s"
},
"dedupIntervalMin": "PT1M",
"dedupFields": [
"appname"
],
"serializer":
"org.apache.eagle.alert.engine.publisher.impl.StringEventSerializer"
}
Something about the metadata schema
1. token: your bot user token.
2. channels: Slack channel names.
3. severitys: which severity level alert message you want to send to Slack.
Other level message will be skipped.
4. urltemplate: used to form an output url link based on docId if downstream
have it. A typical use case will be that downstream stored all the alerts in
Elasticsearch, so we can previously append an ES link in the slack message.
was:Add one more publish implement (Slack) for Alert.
> Add Alert publish implementation for Slack
> --
>
> Key: EAGLE-550
> URL: https://issues.apache.org/jira/browse/EAGLE-550
> Project: Eagle
> Issue Type: New Feature
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Add one more publish implement (Slack) for Alert.
> How to implement
> 1. Here uses a lib "simple-slack-api" to connecting to Slack and publish
> alert messages to Slack.
> 2. Add one more publisher of Slack which extends "AbstractPublishPlugin" to
> process received AlertStreamEvent, and according to Slack config which
> defined in publishment.json to send messages.
> How to use
> 1. Create a bot user in Slack, and remember its token.
> 2. Create some channels if you want send messages to if they do not exist.
> 3. Add your bot user to these channels.
> 4. Then define Slack config and declare to use Slack publisher in config file
> such as below (Especially the "type" and "properties". Here urltemplate will
> form an output url link based on docId if downstream have it.), we can use it
> very easily:
> {
> "name": "test-slack-output",
> "type":
> "org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher",
> "policyIds": [
> "switch_check"
> ],
> "properties": {
> "token": "your token",
> "channels": "your channel1, your channel2",
> "severitys": "CRITICAL",
> "urltemplate": "your template/?id=%s"
> },
> "dedupIntervalMin": "PT1M",
> "dedupFields": [
> "appname"
> ],
> "serializer":
> "org.apache.eagle.alert.engine.publisher.impl.StringEventSerializer"
> }
> Something about the metadata schema
> 1. token: your bot user token.
> 2. channels: Slack channel names.
> 3. severitys: which severity level alert message you want to send to Slack.
> Other level message will be skipped.
> 4. urltemplate: used to form an output url link based on docId if downstream
> have it. A typical use case will be that downstream stored all the alerts in
> Elasticsearch, so we can previously append an ES link in the slack message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-550) Add Alert publish implementation for Slack
[
https://issues.apache.org/jira/browse/EAGLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zeng, Bryant closed EAGLE-550.
--
Resolution: Fixed
> Add Alert publish implementation for Slack
> --
>
> Key: EAGLE-550
> URL: https://issues.apache.org/jira/browse/EAGLE-550
> Project: Eagle
> Issue Type: New Feature
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Add one more publish implement (Slack) for Alert.
> How to implement
> 1. Here uses a lib "simple-slack-api" to connecting to Slack and publish
> alert messages to Slack.
> 2. Add one more publisher of Slack which extends "AbstractPublishPlugin" to
> process received AlertStreamEvent, and according to Slack config which
> defined in publishment.json to send messages.
> How to use
> 1. Create a bot user in Slack, and remember its token.
> 2. Create some channels if you want send messages to if they do not exist.
> 3. Add your bot user to these channels.
> 4. Then define Slack config and declare to use Slack publisher in config file
> such as below (Especially the "type" and "properties". Here urltemplate will
> form an output url link based on docId if downstream have it.), we can use it
> very easily:
> {
> "name": "test-slack-output",
> "type":
> "org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher",
> "policyIds": [
> "switch_check"
> ],
> "properties": {
> "token": "your token",
> "channels": "your channel1, your channel2",
> "severitys": "CRITICAL",
> "urltemplate": "your template/?id=%s"
> },
> "dedupIntervalMin": "PT1M",
> "dedupFields": [
> "appname"
> ],
> "serializer":
> "org.apache.eagle.alert.engine.publisher.impl.StringEventSerializer"
> }
> Something about the metadata schema
> 1. token: your bot user token.
> 2. channels: Slack channel names.
> 3. severitys: which severity level alert message you want to send to Slack.
> Other level message will be skipped.
> 4. urltemplate: used to form an output url link based on docId if downstream
> have it. A typical use case will be that downstream stored all the alerts in
> Elasticsearch, so we can previously append an ES link in the slack message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (EAGLE-550) Add Alert publish implementation for Slack
[ https://issues.apache.org/jira/browse/EAGLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant reopened EAGLE-550: Add more description. > Add Alert publish implementation for Slack > -- > > Key: EAGLE-550 > URL: https://issues.apache.org/jira/browse/EAGLE-550 > Project: Eagle > Issue Type: New Feature >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Add one more publish implement (Slack) for Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-550) Add Alert publish implementation for Slack
[ https://issues.apache.org/jira/browse/EAGLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505295#comment-15505295 ] Zeng, Bryant commented on EAGLE-550: Sure. > Add Alert publish implementation for Slack > -- > > Key: EAGLE-550 > URL: https://issues.apache.org/jira/browse/EAGLE-550 > Project: Eagle > Issue Type: New Feature >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Add one more publish implement (Slack) for Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-550) Add Alert publish implementation for Slack
[ https://issues.apache.org/jira/browse/EAGLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-550. -- Resolution: Fixed > Add Alert publish implementation for Slack > -- > > Key: EAGLE-550 > URL: https://issues.apache.org/jira/browse/EAGLE-550 > Project: Eagle > Issue Type: New Feature >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Add one more publish implement (Slack) for Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-491) AlertPublisherImpl dedup throws exception when dedup column is not configured
[ https://issues.apache.org/jira/browse/EAGLE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-491. -- Resolution: Fixed > AlertPublisherImpl dedup throws exception when dedup column is not configured > - > > Key: EAGLE-491 > URL: https://issues.apache.org/jira/browse/EAGLE-491 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Zeng, Bryant >Priority: Trivial > Fix For: v0.5.0 > > > 2016-08-22 14:51:49,728 WARN [alertBolt1-evaluator_stage1] > runner.AlertBolt[127]: Spec Version [spec_version_1471902692329] of AlertBolt > is newer than Stream Event Version [null]! > 2016-08-22 14:51:49,729 ERROR [Thread-45-alertPublishBolt] > impl.AlertPublisherImpl[80]: Fail invoking publisher's onAlert, continue > java.lang.NullPointerException > at > org.apache.eagle.alert.engine.publisher.impl.DefaultDeduplicator.dedup(DefaultDeduplicator.java:114) > at > org.apache.eagle.alert.engine.publisher.impl.AbstractPublishPlugin.dedup(AbstractPublishPlugin.java:68) > at > org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:67) > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:78) > at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:65) > at > org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:68) > at > backtype.storm.daemon.executor$fn__3441$tuple_action_fn__3443.invoke(executor.clj:633) > at > backtype.storm.daemon.executor$mk_task_receiver$fn__3364.invoke(executor.clj:401) > at > backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58) > at > backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125) > at > backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99) > at > backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80) > at > backtype.storm.daemon.executor$fn__3441$fn__3453$fn__3500.invoke(executor.clj:748) > at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463) > at clojure.lang.AFn.run(AFn.java:24) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-462) Alert Dudup - same metric generate alert should be deduped
[ https://issues.apache.org/jira/browse/EAGLE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-462. -- Resolution: Fixed > Alert Dudup - same metric generate alert should be deduped > -- > > Key: EAGLE-462 > URL: https://issues.apache.org/jira/browse/EAGLE-462 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-471) AlertBolt introduce un-serializble member
[ https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-471. -- Resolution: Fixed > AlertBolt introduce un-serializble member > -- > > Key: EAGLE-471 > URL: https://issues.apache.org/jira/browse/EAGLE-471 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Zeng, Bryant >Priority: Blocker > > AlerBolt.executors > 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set > topology.message.timeout.secs as 3600 > Exception in thread "main" java.lang.RuntimeException: > java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor >at > backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43) > at backtype.storm.utils.Utils.serialize(Utils.java:85) > at > backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168) > at > org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193) > at > org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > Caused by: java.io.NotSerializableException: > java.util.concurrent.ThreadPoolExecutor > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) > at > backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15] > > idea里跑UnitTopologyMain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-440) Alert mongodb storage refine
[ https://issues.apache.org/jira/browse/EAGLE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-440. -- Resolution: Fixed > Alert mongodb storage refine > > > Key: EAGLE-440 > URL: https://issues.apache.org/jira/browse/EAGLE-440 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently, some Alert Mongo Collection is too large. Consider future > increase, need to split large collection to some small collections. > To back compatible, need to keep the interface as the same as before. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-450) Alert check meta version conflict between runtime modules
[ https://issues.apache.org/jira/browse/EAGLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zeng, Bryant closed EAGLE-450. -- Resolution: Fixed > Alert check meta version conflict between runtime modules > - > > Key: EAGLE-450 > URL: https://issues.apache.org/jira/browse/EAGLE-450 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-462) Alert Dudup - same metric generate alert should be deduped
Zeng, Bryant created EAGLE-462: -- Summary: Alert Dudup - same metric generate alert should be deduped Key: EAGLE-462 URL: https://issues.apache.org/jira/browse/EAGLE-462 Project: Eagle Issue Type: Improvement Reporter: Zeng, Bryant Assignee: Zeng, Bryant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-450) Alert check meta version conflict between runtime modules
Zeng, Bryant created EAGLE-450: -- Summary: Alert check meta version conflict between runtime modules Key: EAGLE-450 URL: https://issues.apache.org/jira/browse/EAGLE-450 Project: Eagle Issue Type: Improvement Reporter: Zeng, Bryant Assignee: Zeng, Bryant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
