[jira] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/442
  
@garrettlish can you please add more information to this PR so people can 
learn what are the changes for?


> 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] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user asfgit closed the pull request at:

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


> 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] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user mizeng commented on the issue:

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


> 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] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

GitHub user garrettlish opened a pull request:

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

EAGLE-550: periodically clean up dedup cache



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

$ git pull https://github.com/garrettlish/incubator-eagle master

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

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


commit e5f8c2e323861199aa2f0c3a7497b99c1e9f2206
Author: Xiancheng Li 
Date:   2016-09-20T02:51:05Z

EAGLE-550: periodically clean up dedup cache




> 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

[Hao Chen (JIRA)]

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

Hao Chen commented on EAGLE-550:


Thanks.

> 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

[Zeng, Bryant (JIRA)]

[ 
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] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/441
  
@mizeng Could you add more information on the Description of JIRA? For 
example how it's implemented , how to use, or what's the metadata schema. 
Thanks very much as it's very important for us to track every changes.



> 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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user asfgit closed the pull request at:

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


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