News for hackers. Stuff that matters.
Re:Real-time notifications from systemd to Slack by deathanatos on Monday March 13, 2017 @09:34AM (#13857645)
Actually, the PagerDuty integration for Slack allows in-Slack acknowledgement (and/or resolution) of alerts.

(we used this in addition to, not in lieu of, the pagerduty dashboard itself, as well as mobile notification via pagerduty, and Nagio's web UI.)

> fine-grained notifications

what do you mean by this, out of curiosity?

Re:Real-time notifications from systemd to Slack by lima on Monday March 13, 2017 @11:33AM (#13858682)
With PagerDuty on top it's fine from an operational point of view (you'll still have to trust both PagerDuty and Slack to keep your data secure).

> fine-grained notifications

A common approach is having a "alerts" channel that grabs everyones attention, even though most alerts are only relevant for a small subset of people. A company-wide #general channel is bad enough, and an #alerts channel only makes it worse.

You can totally do this with Slack by having something like PagerDuty in-between. We use a custom-written alerting broker that makes it easier to correctly handle some of the more complicated cases but it's pretty much the same idea.

Re:Real-time notifications from systemd to Slack by pavel_lishin on Monday March 13, 2017 @02:24PM (#13860787)
If your company is large enough to have alerts that aren't universally applicable, it makes sense to create different channels for different alerts, grouped however you want.
Re:Real-time notifications from systemd to Slack by lima on Monday March 13, 2017 @03:32PM (#13861482)
Totally agree, it's exactly what we do. The broker sits in between and decide which alert goes where.