v1.5.1

In this release, several contributions #17, #18 and #19 have been adopted and the documentation has been revised.

v1.5.0

In this release, thanks to contribution #14, the use of custom user attributes and macros is adapted. This makes it very easy to send Telegram messages to different Telegram users, even in combination with Telegram groups.

v1.4.2

In this release, the name of the OMD site has been added to the Telegram output. This is a useful addition when multiple Check_MK instances are used to see which instance sent the notification.

v1.4.1

Bugfix: Little warning on line 29 (unary operator) fixed
#8

v1.4.0

Thanks to contribution #7 now the checkmk-telegram-notify module has additionally emojis according to notification state for better user experience.

v1.3.1

Compatibility with Check_MK version 2.0.0 tested, adaptation of the documentation for configuration with the new dashboard layout.

v1.3.0

The current version of this script allows you to optionally enable IP anonymization. This gives you the option to comply with your own privacy policy or the recommendations of data protection authorities in certain countries if they prohibit the transmission of the full IP address. This masks IPv4 and IPv6 IP addresses before they are transmitted in a message to the Telegram service.

v1.2.0

In this release, thanks to a contribution #4 by @ThomasKaiser, writes to a temporary file have been replaced and script now only uses the variables already passed by Check_MK. This prevents the vulnerability by temporary files. Error handling was also added to the script and a bug was fixed.

v1.1.0

The Telegram token (API key) and the chat/group ID are no longer stored in a separate XML file and instead are passed directly by Check_MK as parameters. This offers the possibility to create several notification groups and to use the script universally.

v1.0.0

Initial version of the Telegram Notification Script with a separate XML file for the Telegram Token and Chat ID.