Monitoring-Benachrichtigungen über Telegram oder Microsoft Teams versenden
Üblicherweise werden auftretende Probleme mittels E-Mail oder SMS an die zuständigen IT-Mitarbeiter gemeldet. Aber sind das tatsächlich schon alle möglichen Kanäle um Benachrichtigungen zu versenden?
Natürlich nicht. Zwei sehr geschickte Beispiele sind diese hier:
Benachrichtigungen über die Telegram App (CLI)
Benachrichtigungen über die Office 365 Web API (Microsoft Teams)
Telegram
Wie Sie wahrscheinlich wissen, ermöglicht die WhatsApp-ähnliche App “Telegram” das Versenden von Nachrichten an Kontakte, Gruppen und Channels. Im Gegensatz zu WhatsApp stellt Telegram eine installierbares Command Line Interface bereit, durch welches Sie das Versenden von Nachrichten vom Computer aus skripten können. Sie müssen dazu die Telegram Binaries herunterladen und auf Ihrem Monitoring Server installieren. Anschließend definieren Sie den Benachrichtigungsbefehl im Monitoring folgendermaßen:
Natürlich sollten Sie vorher Ihren Monitoring-Host als Telegram-Sender registrieren (wie Sie es auch auf Ihrem Smartphone tun würden). Hierfür können Sie die selbe Telefonnummer verwenden wie für den SMS-Versand.
Office 365
Hier haben Sie die Möglichkeit Gruppen zu registrieren. Für die Benachrichtigung benötigen Sie genau diese GUID, danach können Sie diesen Befehl nutzen um die Benachrichtigungen zu versenden:
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix (now Würth IT Italy). Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Author
Juergen Vigna
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix (now Würth IT Italy). Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Error during generation of SLA reports We have fixed a bug that was causing an error during the generation of SLA reports. List of updated packages To solve the issue mentioned above, the following packages have been updated for NetEye Read More
Fix NagVis navigation using IcingaDB Web URLs When clicking on a host or service from a NagVis map, you were redirected to the legacy Monitoring module. The links have been updated to correctly point to the IcingaDB Web module. List Read More
Fixing Misplaced Plugin Output in Icinga Web Interface When plugin output contained HTML content (like links), it was incorrectly displayed near the service name instead of in the Plugin Output section. The plugin output section now correctly renders all content. Read More
Icinga Director Now Responsive During Configuration Deployments Previously, users were unable to interact with Icinga Director while configuration deployments were running. Any attempt to access the interface or API would be blocked until the deployment completed, causing unnecessary delays in Read More
Bug Fix We updated the version of GLPI in order to fix some relevant vulnerabilities. List of updated packages The following packages have been updated for NetEye 4.45: glpi, glpi-autosetup, glpi-configurator, glpi-neteye-config to version 10.0.22_neteye1.17.5-1.