Icinga Multi Status helps you monitor your Icinga instances with alert badges and notifications about incidents.
** Problems or Ideas? **
Please report bugs or ideas on the official GitHub project page:
https://github.com/bashgeek/icinga-multi-status
** Features **
- Monitoring of multiple Icinga Instances (Version 1 and 2) using it's JSON data interface and/or API
- Ability to hide/ignore certain host or service patterns and hosts/services with downtimes
- Configurable refresh time
- Ability to temporarily disable instances without deleting them
- Status-Icon in Toolbar, showing indicator for problems or number of hosts if everything is okay
- Overview Tab showing status of your Icinga instances as well as it's current host or service problems
- Hosts Tab showing you all hosts of all Instances with a quick filter to search for a host
- Services Tab showing you all services of all hosts of all Instances with a quick filter to search for a service
- Instant Chrome Notifications about new problems, if enabled
- Interface completely build on TailwindCSS and DaisyUI
** Changelog **
v1.0.3 (2024-12-21)
- Improved startup/install behavior
v1.0.2 (2024-12-09)
- Improve message and error handling
v1.0.1 (2024-12-04)
- Merge background logics
- Make sure background scripts keep running (Firefox stopped updating after a while)
v1.0.0 (2024-11-27)
- Refactor the whole extension to work properly as a Manifest V3 extension (as required by Chrome now)
- Still works with Firefox (Background Scripts) and Chrome (Service Worker)
- Replaced Bootstrap design UI with TailwindCSS and DaisyUI
Latest reviews
- (2017-10-24) Daniel Langemann: Unusable: error Message was like "unknown error" Api login over curl was possible.
- (2016-10-13) adrian lopez: Great! Better than having thousands of emails in the inbox. Would be great to have an option to omit the notifies at the start of chrome. With many alarms, it's a little bit spammy.
- (2016-03-08) in this version, connecting to http sources or https-sources with .local-domain not possible ... bad-url-error maybe i would give a better repsonse if i'm able to test it