#icinga2 — Public Fediverse posts

Huihui, der #Rootserver war um Punkt 13:00 tot und #icinga2 hat auch Bescheid gegeben, aber Arbeit und Privatleben haben mich das übersehen lassen. Morgen schaue ich mal, ob ich den Grund finde.

Huihui, der #Rootserver war um Punkt 13:00 tot und #icinga2 hat auch Bescheid gegeben, aber Arbeit und Privatleben haben mich das übersehen lassen. Morgen schaue ich mal, ob ich den Grund finde.

Huihui, der #Rootserver war um Punkt 13:00 tot und #icinga2 hat auch Bescheid gegeben, aber Arbeit und Privatleben haben mich das übersehen lassen. Morgen schaue ich mal, ob ich den Grund finde.

Huihui, der #Rootserver war um Punkt 13:00 tot und #icinga2 hat auch Bescheid gegeben, aber Arbeit und Privatleben haben mich das übersehen lassen. Morgen schaue ich mal, ob ich den Grund finde.

Just in case you are using Icinga2 as a monitoring system with some

- RHEL
- CentOS
- AlmaLinux
- RockyLinux

servers and you missed the giant middle finger from the Icinga company:

Because you are using an "enterprise" distribution, it's 5000€ per year now to unlock access to the packages and updates.

No packages for you there on AlmaLinux /RockyLinux 9 and 10.

Apparently Debian and Ubuntu are toy distributions then?

Ah well, time to migrate.

#sysadmin #monitoring #observability #icinga2 #rhel #linux #rockyLinux #enshittification

Just in case you are using Icinga2 as a monitoring system with some

- RHEL
- CentOS
- AlmaLinux
- RockyLinux

servers and you missed the giant middle finger from the Icinga company:

Because you are using an "enterprise" distribution, it's 5000€ per year now to unlock access to the packages and updates.

No packages for you there on AlmaLinux /RockyLinux 9 and 10.

Apparently Debian and Ubuntu are toy distributions then?

Ah well, time to migrate.

#sysadmin #monitoring #observability #icinga2 #rhel #linux #rockyLinux #enshittification

Just in case you are using Icinga2 as a monitoring system with some

- RHEL
- CentOS
- AlmaLinux
- RockyLinux

servers and you missed the giant middle finger from the Icinga company:

Because you are using an "enterprise" distribution, it's 5000€ per year now to unlock access to the packages and updates.

No packages for you there on AlmaLinux /RockyLinux 9 and 10.

Apparently Debian and Ubuntu are toy distributions then?

Ah well, time to migrate.

#sysadmin #monitoring #observability #icinga2 #rhel #linux #rockyLinux #enshittification

Just in case you are using Icinga2 as a monitoring system with some

- RHEL
- CentOS
- AlmaLinux
- RockyLinux

servers and you missed the giant middle finger from the Icinga company:

Because you are using an "enterprise" distribution, it's 5000€ per year now to unlock access to the packages and updates.

No packages for you there on AlmaLinux /RockyLinux 9 and 10.

Apparently Debian and Ubuntu are toy distributions then?

Ah well, time to migrate.

#sysadmin #monitoring #observability #icinga2 #rhel #linux #rockyLinux #enshittification

Setting up #icinga2 looks a bit more complicated to me than I remember for nagios/icinga. Do I hold it wrong, or what's the suggestion? I need just a bit of monitoring for home use, nothing big or fancy.

Setting up #icinga2 looks a bit more complicated to me than I remember for nagios/icinga. Do I hold it wrong, or what's the suggestion? I need just a bit of monitoring for home use, nothing big or fancy.

Setting up #icinga2 looks a bit more complicated to me than I remember for nagios/icinga. Do I hold it wrong, or what's the suggestion? I need just a bit of monitoring for home use, nothing big or fancy.

Setting up #icinga2 looks a bit more complicated to me than I remember for nagios/icinga. Do I hold it wrong, or what's the suggestion? I need just a bit of monitoring for home use, nothing big or fancy.

Setting up #icinga2 looks a bit more complicated to me than I remember for nagios/icinga. Do I hold it wrong, or what's the suggestion? I need just a bit of monitoring for home use, nothing big or fancy.

After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

#icinga2 #icinga "You say “Eee-Chingaa”, I say “Aye-Singa” – but how do the Zulus say it? We consulted a couple Zulu speakers and even received a pronunciation guide from Megan Wells to help us all out. As she told us:
“The I in Icinga is actually a Romanized representation of the Zulu click. The easiest way to approximate the click is by putting your tongue behind your top teeth and pulling it down, kind of like a tsk-tsk noise. The vowels on either side of the click are “eee” noises, like in “see”. There is no hard “g” sound in Icinga – the “ng” is pronounced like the end of “sing”. Finally, the “a” is pronounced like the “a” in “father”."
https://icinga.com/blog/archive/a-lesson-in-zulu-icinga/

#icinga2 #icinga "You say “Eee-Chingaa”, I say “Aye-Singa” – but how do the Zulus say it? We consulted a couple Zulu speakers and even received a pronunciation guide from Megan Wells to help us all out. As she told us:
“The I in Icinga is actually a Romanized representation of the Zulu click. The easiest way to approximate the click is by putting your tongue behind your top teeth and pulling it down, kind of like a tsk-tsk noise. The vowels on either side of the click are “eee” noises, like in “see”. There is no hard “g” sound in Icinga – the “ng” is pronounced like the end of “sing”. Finally, the “a” is pronounced like the “a” in “father”."
https://icinga.com/blog/archive/a-lesson-in-zulu-icinga/

#icinga2 #icinga "You say “Eee-Chingaa”, I say “Aye-Singa” – but how do the Zulus say it? We consulted a couple Zulu speakers and even received a pronunciation guide from Megan Wells to help us all out. As she told us:
“The I in Icinga is actually a Romanized representation of the Zulu click. The easiest way to approximate the click is by putting your tongue behind your top teeth and pulling it down, kind of like a tsk-tsk noise. The vowels on either side of the click are “eee” noises, like in “see”. There is no hard “g” sound in Icinga – the “ng” is pronounced like the end of “sing”. Finally, the “a” is pronounced like the “a” in “father”."
https://icinga.com/blog/archive/a-lesson-in-zulu-icinga/

#icinga2 #icinga "You say “Eee-Chingaa”, I say “Aye-Singa” – but how do the Zulus say it? We consulted a couple Zulu speakers and even received a pronunciation guide from Megan Wells to help us all out. As she told us:
“The I in Icinga is actually a Romanized representation of the Zulu click. The easiest way to approximate the click is by putting your tongue behind your top teeth and pulling it down, kind of like a tsk-tsk noise. The vowels on either side of the click are “eee” noises, like in “see”. There is no hard “g” sound in Icinga – the “ng” is pronounced like the end of “sing”. Finally, the “a” is pronounced like the “a” in “father”."
https://icinga.com/blog/archive/a-lesson-in-zulu-icinga/

So, mein #icinga2-graphite-Problem war ein Bug. Den jemand 2023 gefixt hat, der es aber nicht in die Packages bei Ubuntu geschafft hat. *hmpf*

So, mein #icinga2-graphite-Problem war ein Bug. Den jemand 2023 gefixt hat, der es aber nicht in die Packages bei Ubuntu geschafft hat. *hmpf*

Wieder mal eine #icinga2-Frage: Wie generiert #Icingaweb2 die Aufrufe nach #Graphite? Wenn ich den GET von Icinga richtig tracke, bekommt es eine Grafik zurück. Aber darstellen tut es sie nicht... und ich bin ratlos wie ich das debuggen kann...

Wieder mal eine #icinga2-Frage: Wie generiert #Icingaweb2 die Aufrufe nach #Graphite? Wenn ich den GET von Icinga richtig tracke, bekommt es eine Grafik zurück. Aber darstellen tut es sie nicht... und ich bin ratlos wie ich das debuggen kann...

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

#monitoring-Fails: Um Reports aus #icinga2 zu erstellen, sollen #pdfs generiert werden - gut! Aber warum muss dafür ein Internetbrowser installiert werden? Warum kein #ghostscript? Das ist genau dafür gedacht...

#monitoring-Fails: Um Reports aus #icinga2 zu erstellen, sollen #pdfs generiert werden - gut! Aber warum muss dafür ein Internetbrowser installiert werden? Warum kein #ghostscript? Das ist genau dafür gedacht...

Ich am überlegen ob ich das #ICINGA2 #Grafana Modul forken soll und alle ausstehenden Änderungen mal zusammen packe. Leider scheint der eigenliche Maintainer sich nämlich nicht mehr drum zu kümmern.

Wenn ich jetzt noch wirklich entwickeln könnte, würde ich sogar aktiv weiter betreiben, aber so.

Ich am überlegen ob ich das #ICINGA2 #Grafana Modul forken soll und alle ausstehenden Änderungen mal zusammen packe. Leider scheint der eigenliche Maintainer sich nämlich nicht mehr drum zu kümmern.

Wenn ich jetzt noch wirklich entwickeln könnte, würde ich sogar aktiv weiter betreiben, aber so.

Ich am überlegen ob ich das #ICINGA2 #Grafana Modul forken soll und alle ausstehenden Änderungen mal zusammen packe. Leider scheint der eigenliche Maintainer sich nämlich nicht mehr drum zu kümmern.

Wenn ich jetzt noch wirklich entwickeln könnte, würde ich sogar aktiv weiter betreiben, aber so.

#icinga2 in Debian has command definitions not matching the Debian available check command binaries.

Icinga2 says - use "nagios plugins" which are not available in Debian. monitoring-plugins says modify the existing definitions.

I am puzzled that these 2 Maintainers have no interest in integrations between Icinga2 and corresponding check plugins.

I though that was the whole reason of packaging to get a "Distribution" work as a whole ...

Bug 1085355 & 1085411

#icinga2 in Debian has command definitions not matching the Debian available check command binaries.

Icinga2 says - use "nagios plugins" which are not available in Debian. monitoring-plugins says modify the existing definitions.

I am puzzled that these 2 Maintainers have no interest in integrations between Icinga2 and corresponding check plugins.

I though that was the whole reason of packaging to get a "Distribution" work as a whole ...

Bug 1085355 & 1085411

#icinga2 in Debian has command definitions not matching the Debian available check command binaries.

Icinga2 says - use "nagios plugins" which are not available in Debian. monitoring-plugins says modify the existing definitions.

I am puzzled that these 2 Maintainers have no interest in integrations between Icinga2 and corresponding check plugins.

I though that was the whole reason of packaging to get a "Distribution" work as a whole ...

Bug 1085355 & 1085411

#icinga2 in Debian has command definitions not matching the Debian available check command binaries.

Icinga2 says - use "nagios plugins" which are not available in Debian. monitoring-plugins says modify the existing definitions.

I am puzzled that these 2 Maintainers have no interest in integrations between Icinga2 and corresponding check plugins.

I though that was the whole reason of packaging to get a "Distribution" work as a whole ...

Bug 1085355 & 1085411

Auf der Suche nach einer Alternative zu #icinga2, #monit und Ähnliches bin ich über simplemonitor gestolpert: https://github.com/jamesoff/simplemonitor/tree/main

Ziel für mich: Einfach Emails bekommen, wenn Dienste auf den privaten Servern nicht so laufen, wie sie sollen.

Wie löst ihr das denn so?

For those of you who are interested in #homeserver & #homelab setups, what is your approach to monitoring and alerting?

I've always really loved #icinga but I'm wondering what other people are using.

#server #icinga2 #monitoring #alerting #serverlife

When your #icinga2 complains about a plant beeing to dry but over its daily watering limit.

Self made check + esp32 iot watering + rest api for the check

Monitoring the automatic watering of your plants. Having limits in pump activity to not water the whole house. Now on one plant the daily "pump active seconds" has been reached but its still to dry. Send me a pager notification ..

#icinga2

Are you curious to learn how Icinga 2 worked for us at the University of Bern? Come to the #IcingaSummit and learn how it went from Zero to hero.

Don't miss https://icinga.com/summit/program/icinga-2-from-zero-to-hero-how-icinga2-became-our-central-monitor/

Reserve your spot now: https://icinga.com/summit/tickets/

I started to prepare the first slides But there is enough time left :-)

#icinga2

Also bald kommt das Display und ich frage mich schon wie ich an #awtrix uptime #kuma und #icinga2 anbinden kann.

Ich habe das Gefühl, dass ich hier Neuland betrete, da ich bis jetzt nichts gefunden habe.

#ioBroker wäre hier ein Stichwort

#adminlife #opensource #monitoring

https://github.com/ioBroker/ioBroker

When your #icinga2 complains about a plant beeing to dry but over its daily watering limit.

Self made check + esp32 iot watering + rest api for the check

When your #icinga2 complains about a plant beeing to dry but over its daily watering limit.

Self made check + esp32 iot watering + rest api for the check

When your #icinga2 complains about a plant beeing to dry but over its daily watering limit.

Self made check + esp32 iot watering + rest api for the check

When your #icinga2 complains about a plant beeing to dry but over its daily watering limit.

Self made check + esp32 iot watering + rest api for the check