{"id":1823,"date":"2016-04-15T13:46:32","date_gmt":"2016-04-15T10:46:32","guid":{"rendered":"http:\/\/joseph.zikusooka.com\/?p=1823"},"modified":"2016-04-15T14:14:27","modified_gmt":"2016-04-15T11:14:27","slug":"receive-linux-server-alerts-phone-via-telegram","status":"publish","type":"post","link":"https:\/\/joseph.zikusooka.com\/?p=1823","title":{"rendered":"How to receive Linux server alerts on your phone via telegram"},"content":{"rendered":"

To monitor my Linux servers, I have been using icinga<\/a> since its forking from the popular Nagios<\/a>. Icinga has really matured over the last few years and currently at version 2.4.4, I would recommend anyone serious at network and server monitoring to check this open source project. Installation and setup of icinga2 is somewhat complex, but if you are an experienced command line sort of guy, its not that hard at all. In fact the introduction of icingaweb2<\/a> has made it possible to have an easy to use interface to setup your monitoring needs. I will not delve into the nitty gritty of install and setup. For that please take a look at the detailed documentation<\/a>.<\/p>\n

Several alerts are possible when using Icinga including e-mail, sms, XMPP, IRC, twitter etc. I wanted a way to get notified of host and service failures using telegram. Luckily, telegram provides an API to do just that.<\/p>\n

The secret source in all of this; is to install a command line interface for telegram called telegram-cli<\/a> . In order for telegram-cli to compile without any issues, ensure that all dependencies are installed<\/p>\n

For Fedora:<\/p>\n

sudo dnf -y install\r\nlua-devel openssl-devel libconfig-devel readline-devel libevent-devel\r\njansson-devel python-devel<\/code><\/pre>\n
For Ubuntu\/Debian:<\/p>\n
sudo apt-get install\r\nlibreadline-dev libconfig-dev libssl-dev lua5.2 liblua5.2-dev\r\nlibevent-dev libjansson-dev libpython-dev make <\/code>\r\n<\/pre>\n
Now install telegram-cli<\/p>\n
cd \/usr\/src && git clone \u2013recursive https:\/\/github.com\/vysheng\/tg.git<\/code><\/pre>\n
Note: Make sure you add the recursive flag to git clone, otherwise make will fail<\/em><\/p>\n
cd tg<\/code><\/pre>\n
.\/configure && make<\/code><\/pre>\n
The binary is under .\/bin\/telegram-cli. Simply create a symbolic link to it.<\/p>\n
cd \/usr\/sbin && ln -s \/usr\/src\/tg\/bin\/telegram-cli .<\/code><\/pre>\n
Thats it for the installation of telegram-cli. Please read the README file in the sources root folder, especially on how to use this application.<\/p>\n
Icinga2 telegram-cli setup<\/strong><\/p>\n
First ensure that the user icinga (created during icinga install process) can send a message using telegram-cli. Remember all alerts go out under the icinga user, so you have to get this part working first, lest you spend hours troubleshooting.<\/p>\n
Temporarily change the shell for icinga from ‘\/sbin\/nologin’ to ‘\/bin\/bash.’ Remember to change back to nologin for icinga user when testing is completed.<\/p>\n
usermod -s \/bin\/bash icinga<\/code><\/pre>\n
Now change to user icinga: Assumming that you are root user, if not you will be prompted for a password, which you would setup as root.<\/p>\n
su -l icinga<\/code><\/pre>\n
telegram-cli<\/code><\/pre>\n
Enter your phone number and SMS code sent when prompted<\/em><\/p>\n
Then test to see if you can send a message:<\/p>\n
telegram-cli -D -W -e \"msg [PEER_NAME] 'Hello World'\"<\/code><\/pre>\n
If it works, then you can proceed to configure icinga2.<\/p>\n
Create notification script for services<\/p>\n
cat > \/etc\/icinga2\/scripts\/notify_services_via_telegram.sh << EOF<\/p>\n
#!\/usr\/bin\/env bash<\/p>\n
TELEGRAM_CMD=\/usr\/sbin\/telegram-cli<\/p>\n
TELEGRAM_OPTS=”-D -W”<\/p>\n
TELEGRAM_PEER=[PEER_NAME]<\/p>\n
TELEGRAM_MSG=$(cat <<TEMPLATE<\/p>\n
[$HOSTALIAS] $NOTIFICATIONTYPE: $SERVICEDESC is $SERVICESTATE<\/p>\n
TEMPLATE<\/p>\n
)<\/p>\n
$TELEGRAM_CMD $TELEGRAM_OPTS -e “msg $TELEGRAM_PEER ‘$TELEGRAM_MSG'”<\/p>\n
EOF<\/p>\n
Ensure that above script is executable:<\/p>\n
chmod 755 \/etc\/icinga2\/scripts\/notify_services_via_telegram.sh<\/code><\/pre>\n
Proceed to configure commands, notifications, and hosts config files: Note: Am only setting up notifications for services. You can do the same for hosts information.<\/p>\n
cat >> \/etc\/icinga2\/conf.d\/commands.conf <<EOF<\/p>\n
\/** Telegram *\/<\/p>\n
object NotificationCommand “telegram-service-notification” {<\/p>\n
import “plugin-notification-command”<\/p>\n
command = [ SysconfDir + “\/icinga2\/scripts\/notify_services_via_telegram.sh” ]<\/p>\n
env = {<\/p>\n
“NOTIFICATIONTYPE” = “$notification.type$”<\/p>\n
“SERVICEDESC” = “$service.name$”<\/p>\n
“HOSTALIAS” = “$host.display_name$”,<\/p>\n
“HOSTADDRESS” = “$address$”,<\/p>\n
“SERVICESTATE” = “$service.state$”,<\/p>\n
“LONGDATETIME” = “$icinga.long_date_time$”,<\/p>\n
“SERVICEOUTPUT” = “$service.output$”,<\/p>\n
“NOTIFICATIONAUTHORNAME” = “$notification.author$”,<\/p>\n
“NOTIFICATIONCOMMENT” = “$notification.comment$”,<\/p>\n
“HOSTDISPLAYNAME” = “$host.display_name$”,<\/p>\n
“SERVICEDISPLAYNAME” = “$service.display_name$”,<\/p>\n
“USEREMAIL” = “$user.email$”<\/p>\n
}<\/p>\n
}<\/p>\n
EOF<\/p>\n
cat >> \/etc\/icinga2\/conf.d\/notifications.conf <<EOF<\/p>\n
\/** Telegram *\/<\/p>\n
apply Notification “telegram-icingaadmin” to Service {<\/p>\n
import “telegram-service-notification”<\/p>\n
user_groups = host.vars.notification.telegram.groups<\/p>\n
users = host.vars.notification.telegram.users<\/p>\n
assign where host.vars.notification.telegram<\/p>\n
}<\/p>\n
EOF<\/p>\n
To get alerts on services for a host, add the following stanza to the host configuration in \/etc\/icinga2\/conf.d\/hosts.conf<\/p>\n
\/* Telegram *\/<\/p>\n
vars.notification[“telegram”] = {<\/p>\n
groups = [ “icingaadmins” ]<\/p>\n
}<\/p>\n
Finally, check your config files<\/p>\n
icinga2 daemon -C<\/code><\/pre>\n
Restart icinga if all is OK. You will now be notified via telegram when services fail for the above configured host.<\/p>\n","protected":false},"excerpt":{"rendered":"
To monitor my Linux servers, I have been using icinga since its forking from the popular Nagios. Icinga has really matured over the last few years and currently at version 2.4.4, I would recommend anyone serious at network and server monitoring to check this open source project. Installation and setup of icinga2 is somewhat complex, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":3,"footnotes":""},"categories":[19],"tags":[],"class_list":["post-1823","post","type-post","status-publish","format-standard","hentry","category-tutorial"],"_links":{"self":[{"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/posts\/1823","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1823"}],"version-history":[{"count":12,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/posts\/1823\/revisions"}],"predecessor-version":[{"id":1835,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=\/wp\/v2\/posts\/1823\/revisions\/1835"}],"wp:attachment":[{"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/joseph.zikusooka.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}