Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #1591 from influxdata/new-notification-endpoints 

Add Telegram endpoint (addresses #1198 )
pull/1607/head
noramullen1 2020-10-06 10:17:57 -07:00 committed by GitHub
parent 3646da3db9 56610498eb
commit 56481cee45
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/influxdb/v2.0/monitor-alert/notification-endpoints/_index.md
View File

@ -15,6 +15,6 @@ related:
Notification endpoints store information to connect to a third party service.
If you're using the Free Plan, create a Slack endpoint.
If you're using the Usage-based Plan, create a connection to a HTTP, Slack, or PagerDuty endpoint.
If you're using the Usage-based Plan, create a connection to a HTTP, Slack, Telegram, or PagerDuty endpoint.
{{< children >}}

4
content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md
View File

@ -31,6 +31,7 @@ To send notifications about changes in your data, start by creating a notificati
| **Slack** | **{{< icon "check" >}}** | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
| **PagerDuty** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
| **HTTP** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
| **Telegram** | **{{< icon "check" >}}** | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
5. In the **Name** and **Description** fields, enter a name and description for the endpoint.
6. Enter enter information to connect to the endpoint:
@ -43,4 +44,7 @@ To send notifications about changes in your data, start by creating a notificati
- [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service), [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service), and then enter the PagerDuty integration key for your new service in the **Routing Key** field.
- The **Client URL** provides a useful link in your PagerDuty notification. Enter any URL that you'd like to use to investigate issues. This URL is sent as the `client_url` property in the PagerDuty trigger event. By default, the **Client URL** is set to your Monitoring & Alerting History page, and the following included in the PagerDuty trigger event: `"client_url": "https://us-west-2-1.aws.cloud2.influxdata.net/orgs/<your-org-ID>/alert-history”`
- For Telegram:
- Enter a Telegram **Bot Token** and **Chat ID**. For details, see [Set up a Telegram bot](/influxdb/v2.0/reference/flux/stdlib/contrib/telegram/#set-up-a-telegram-bot).
6. Click **Create Notification Endpoint**.

6
content/influxdb/v2.0/reference/flux/stdlib/contrib/telegram/_index.md
View File

@ -24,8 +24,8 @@ import "contrib/sranka/telegram"
{{< children type="functions" show="pages" >}}
## Set up a Telegram bot
The **Telegram Bot API** requires a **bot token** and a **channel ID**.
To set up a Telegram bot and obtain the required bot token and channel ID:
The **Telegram Bot API** requires a **bot token** and a **chat ID**.
To set up a Telegram bot and obtain the required bot token and chat ID:
1. [Create a new Telegram account](https://telegram.org/) or use an existing account.
2. [Create a Telegram bot](https://core.telegram.org/bots#creating-a-new-bot).
@ -40,7 +40,7 @@ To set up a Telegram bot and obtain the required bot token and channel ID:
curl https://api.telegram.org/bot$token/getUpdates
```
Find your **channel ID** in the `id` field of the response.
Find your **chat ID** in the `id` field of the response.
{{% note %}}