update Plugin to work with new Notification/Alert System in Graylog 3.1

Question

update Plugin to work with new Notification/Alert System in Graylog 3.1

Opened this issue 5 years ago · 14 comments

This Plugin needs to be updated to work with the new alerting/notification system.

Answer 1 · 2019-09-24T14:54:37.000Z

is not working with Graylog 3.1.2 as well: Legacy alarm callbacks are deprecated. Please switch to the new notification types as soon as possible!

Answer 2 · 2019-09-26T11:03:28.000Z

I'm sorely tempted to have a go at this, it would be extremely useful for us (the existing version seems to duplicate some backlog items in 3.1).

This would be my first foray into Graylog development, is there an example 3.1 alert plugin that anyone can point me at?

Answer 3 · 2019-09-26T11:24:39.000Z

@tabascoterrier That would be awesome! 😃

There is no external plugin yet but you can take a look at the HTTP event notification in the server repository. All the internal notifications are implemented as plugins as well:

Answer 4 · 2019-09-26T12:13:51.000Z

Thanks @bernd, I'll have a look!

Answer 5 · 2019-10-09T20:34:48.000Z

As i had the same problem i simply wrote a new slack plugin for graylog 3.1 using the new notification system.
As the code significantly changed i created it as a new project instead of a merge request.

https://marketplace.graylog.org/addons/d87f19f5-4a91-4099-8179-c4700b6c8f6d
https://github.com/sportalliance/graylog-plugin-slack-notification

Answer 6 · 2019-10-24T09:01:43.000Z

Is anyone working on this? If not I will take care of it as I really need it

Answer 7 · 2019-10-24T11:03:14.000Z

@radykal-com Feel free to work on this! 😃 Thank you! 👍

Answer 8 · 2019-10-24T11:49:16.000Z

@radykal-com I would recommend you the plugin I wrote and mentioned three comments above.
Only the support of matterhorn has been dropped but slack is working the same way as in this plugin

Answer 9 · 2019-10-27T13:27:29.000Z

@sboeingSPA why dont contribute your changes back to the original plugin? Its much easier to maintain one plugin instead of 2 different ones that actually are doing the same.

Answer 10 · 2019-11-01T06:58:53.000Z

Because all the code of the original plugin is deprecated. Meaning i would deleted all of it and replace it with new one. But the original plugin currently supports Mattermost which i don't know and don't want to explicitly support and test.

Also this project looks quite unmaintained to me. The last release is more than a year old and there are merge requests no one takes care of.

Answer 11 · 2019-11-04T07:51:25.000Z

@sboeingSPA Please feel free to submit your work as a PR, regardless how much code you changed. I do my best to check in on this repo from time to time for critical issues, but I have a full time career not affiliated with Graylog and a family. There is only so much time I can contribute. If you would like to take over repository maintenance, I’m happy to pass the torch.

Answer 12 · 2019-11-04T11:19:53.000Z

@sboeingSPA @Aenima4six2 Thanks folks for taking care! 👍

We don't need to delete the legacy plugin. I think it's good to keep it until everyone migrated off to the new event notification. So it would be enough to just add the new event notification code to the existing structure.

Answer 13 · 2019-11-12T09:04:29.000Z

@bernd @Aenima4six2 i will take another look into it the next weeks during my vacation

Answer 14 · 2020-02-18T10:29:31.000Z

Hi everyone,

Any news on this? We miss this plugin in Graylog :-/