Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script for telegram notification #10063

Closed
psztoch opened this issue May 16, 2024 · 3 comments
Closed

Script for telegram notification #10063

psztoch opened this issue May 16, 2024 · 3 comments

Comments

@psztoch
Copy link

psztoch commented May 16, 2024

Describe the solution you'd like

Ready for use script /etc/icinga2/scripts/telegram-host-notification.sh and
/etc/icinga2/scripts/telegram-service-notification.sh.

Updated /etc/icinga2/conf.d/commands.conf.

Is your feature request related to a problem? Please describe.

I believe that Telegram is so popular that it is worth including this script in the official distribution along with "object NotificationCommand".

@moreamazingnick
Copy link

Telegram is indeed very nice but here are some things to consider

  • messages by bots do not include end-to-end encryption
  • you are trusting a third party with no Data Processing Agreement with you alert data.
  • If you are not paying for it you are the product, not the customer

@oxzi
Copy link
Member

oxzi commented May 27, 2024

I would second @moreamazingnick's opinion. Personally I would not use Telegram for sensitive information, or anything at all.

Furthermore, there are already lots of notification plugins out there. Please use some of those scripts, as adding this additional maintenance to the main Icinga 2 repository should not be worth the effort.

@abielan
Copy link

abielan commented May 27, 2024

A plugin for several of the most popular messengers should be in the main repo and standard package.
The lack of a plugin for Telegram is a problem that is definitely worth solving.
Icinga has great monitoring but poor reporting and average notifications.

@Al2Klimov Al2Klimov closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants