<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recipients on</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/</link><description>Recent content in Recipients on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Tue, 06 Oct 2020 08:48:23 +0000</lastBuildDate><atom:link href="https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/index.xml" rel="self" type="application/rss+xml"/><item><title>Recipients</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/receivers/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/receivers/</guid><description>By default, alerts are routed to the VictoriaMetrics monitoring cluster located in the management cluster. You can see triggered alerts in the client cluster interface in the Alerts/View Alerts.
To configure additional routing, you must create recipients and routes. If you need to add time intervals during which notifications will not be received, set time intervals and indicate them in routes.
Screenshot The &amp;ldquo;Recipients&amp;rdquo; page is a table with the following fields:</description></item><item><title>Webhook</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/webhook/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/webhook/</guid><description>Webhook is used to send messages to notification aggregation services, service-desk, task-manager.
Username (optional field. Used for authorization paired with a password. Not required when using a Bearer token.); Password (optional field. Used for authorization paired with the username. Not required when using a Bearer token.); Bearer token (optional field. Used for authorization. Not required when using username and password); URL proxy; Send resolved: triggers the sending of a message indicating that the alert is no longer relevant.</description></item><item><title>Telegram</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/telegram/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/telegram/</guid><description>To set up sending notifications in telegram you need to:
Create a telegram bot. Please note! The bot token is issued once when created via @BotFather. Determine the recipient: this can be sent to a user or to a chat group of users. Once the bot and recipients are defined, in the GUI, configure the recipient:
Telegram API URL (has a default value, optional) Message format: Markdown, Markdownv2, HTML (default HTML); Bot token on behalf of which the notification will be sent; Chat ID (individual or group).</description></item><item><title>Email</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/email/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/alerting/alert-manager-config/receivers/email/</guid><description>Depending on your email provider, you will need to fill out information to set up an email alert. For example, Gmail requires authorization data.
Authorization ID: required for SMTP authorization using PLAIN. Username: required for SMTP authorization using CRAM-MD5, LOGIN or PLAIN. If authorization is not used, leave the field blank. Password: required for SMTP authorization using CRAM-MD5, LOGIN or PLAIN. If authorization is not used, leave the field blank. Authorization secret: required for SMTP authorization using CRAM-MD5.</description></item></channel></rss>