logstash-plugins/logstash-output-slack

Name: logstash-output-slack

Owner: Logstash Plugins

Description: null

Created: 2015-04-15 00:41:22.0

Updated: 2018-04-06 23:00:25.0

Pushed: 2018-04-06 23:01:12.0

Homepage: null

Size: 47

Language: Ruby

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Reviews of the code/contributions are very welcome (particularly with testing!), since I don't really know Ruby.

Logstash Slack Output Plugin

This is a plugin for Logstash that pushes log events to Slack using their incoming webhooks API.

It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.

======= Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one central location.

• For formatting code or config example, you can use the asciidoc [source,ruby] directive
• For more asciidoc formatting tips, see the excellent reference here https://github.com/elastic/docs#asciidoc-guide.

Need Help?

Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.

Usage

t {
...


ers {
...


ut {
...
slack {
    url => <YOUR SLACK WEBHOOK URL HERE>
    channel => [channel-name - optional]
    username => [slack username - optional]
    icon_emoji => [emoji, something like ":simple_smile:" - optional]
    icon_url => [icon url, would be overriden by icon_emoji - optional]
    format => [default is "%{message}", but used to format the text - optional]
    attachments => [an array of attachment maps as specified by the slack API - optional; if there is an "attachments" field in the event map and it is valid, it will override what is configured here, even if it's empty]
}

Contributing

All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.

Programming is not a required skill. Whatever you've seen about open source and maintainers or community members saying “send patches or die” - you will not see that here.

It is more important to the community that you are able to contribute.

For more information about contributing, see the CONTRIBUTING file.