#22

docs/devops/alm/hosting_maintain.md

@@ -49,6 +49,36 @@ so we use Elasticsearch for analysis. This analysis can also result in an alert,
 With Netdata and logging in place we can provide a comprehensive analysis of all our components. It allows us to retrace problems or even
 avoid problems, which might appear in the future.
 
+### Flexible distribution of Alerts
+
+Specific Alerts can be distributed by Netdata to several channels. 
+
+'*' Channels supported by Netdata:
+
+* e-mails (using the sendmail command),
+* push notifications to your mobile phone [pushover.net](https://pushover.net/),
+* messages to your slack team [slack.com](https://slack.com/intl/de-de/),
+* messages to your alerta server [Alerta](https://alerta.io/),
+* messages to your flock team [Flock](https://www.flock.com/),
+* messages to your discord guild [Discord](https://discord.com/),
+* messages to your telegram chat / group chat [Telegram](https://telegram.org/)
+* sms messages to your cell phone or any sms enabled device [Twilio](https://ahoy.twilio.com/)
+* sms messages to your cell phone or any sms enabled device (messagebird.com)
+* sms messages to your cell phone or any sms enabled device (smstools3)
+* notifications to users on pagerduty.com
+* push notifications to iOS devices (via prowlapp.com)
+* notifications to Amazon SNS topics (aws.amazon.com)
+* messages to your irc channel on your selected network
+* messages to a local or remote syslog daemon
+* message to Microsoft Team (through webhook)
+* message to Rocket.Chat (through webhook)
+* message to Google Hangouts Chat (through webhook)
+
+### Fallback Scenario
+
+In case of an outage of the alerting system, we have an external fallback platform, called
+[Matrix](https://app.element.io/). All alerts will be sent to this platform as well.
+
 ### Alert Deduplication
 
 As seen in the picture this component has four incoming channels: