replacing BOTID by CHATID

TELEGRAM_BOTID becomes TELEGRAM_CHATID

it is misleading to name it bot id - imho as the id we need here
is actually the chat id, either from a user or group.
that id is not related to the bot itself.
This commit is contained in:
Thomas 2019-07-22 13:07:58 +02:00
parent d35cdf14d4
commit 514d8a69e7
No known key found for this signature in database
GPG Key ID: E4F2353ADA69D870
3 changed files with 5 additions and 5 deletions

View File

@ -14,7 +14,7 @@ apply Notification "Host by Telegram" to Host {
users = [ "telegram_unixe" ]
vars.notification_logtosyslog = true
vars.telegram_bot = "<YOUR_TELEGRAM_BOT_NAME>"
vars.telegram_botid = "<YOUR_TELEGRAM_BOT_ID>"
vars.telegram_chatid = "<YOUR_TELEGRAM_CHAT_ID>"
vars.telegram_bottoken = "<YOUR_TELEGRAM_BOT_TOKEN>"
}
```

View File

@ -26,7 +26,7 @@ The following are mandatory:
-n HOSTDISPLAYNAME (\$host.display_name$)
-o HOSTOUTPUT (\$host.output$)
-p TELEGRAM_BOT (\$telegram_bot$)
-q TELEGRAM_BOTID (\$telegram_botid$)
-q TELEGRAM_CHATID (\$telegram_chatid$)
-r TELEGRAM_BOTTOKEN (\$telegram_bottoken$)
-s HOSTSTATE (\$host.state$)
-t NOTIFICATIONTYPE (\$notification.type$)
@ -56,7 +56,7 @@ do
n) HOSTDISPLAYNAME=$OPTARG ;;
o) HOSTOUTPUT=$OPTARG ;;
p) TELEGRAM_BOT=$OPTARG ;;
q) TELEGRAM_BOTID=$OPTARG ;;
q) TELEGRAM_CHATID=$OPTARG ;;
r) TELEGRAM_BOTTOKEN=$OPTARG ;;
s) HOSTSTATE=$OPTARG ;;
t) NOTIFICATIONTYPE=$OPTARG ;;

View File

@ -27,7 +27,7 @@ The following are mandatory:
-n HOSTDISPLAYNAME (\$host.display_name$)
-o SERVICEOUTPUT (\$service.output$)
-p TELEGRAM_BOT (\$telegram_bot$)
-q TELEGRAM_BOTID (\$telegram_botid$)
-q TELEGRAM_CHATID (\$telegram_chatid$)
-r TELEGRAM_BOTTOKEN (\$telegram_bottoken$)
-s SERVICESTATE (\$service.state$)
-t NOTIFICATIONTYPE (\$notification.type$)
@ -58,7 +58,7 @@ do
n) HOSTDISPLAYNAME=$OPTARG ;;
o) SERVICEOUTPUT=$OPTARG ;;
p) TELEGRAM_BOT=$OPTARG ;;
q) TELEGRAM_BOTID=$OPTARG ;;
q) TELEGRAM_CHATID=$OPTARG ;;
r) TELEGRAM_BOTTOKEN=$OPTARG ;;
s) SERVICESTATE=$OPTARG ;;
t) NOTIFICATIONTYPE=$OPTARG ;;