I just wrote a module that shows you your cluster layout from zones and endpoints.
Check it out, feedback welcome! There is some tweaking to the visuals to go, but it works.
4 Likes
just did our second release with thanks to @moreamazingnick for a big contribution.
1 Like
This module sounds interesting, it would help if you had a screenshot or two so people had an idea of what it looked like once installed.
Thank you for the effort in creating this.
1 Like
Yeah I agree. I just have to mess with it a bit to garble the output, so as not to give away confidential cluster information. I will update it shortly.
That looks quite impressive.
I believe I will be installing that module. Its usefulness is quite apparent.
Does it reflect the status of hosts at all, eg: hosts turn red when there is a problem on them, or are unreachable? If it does not it is still a very useful addition.
No status.
Check out meerkat for that
We updated the code to be laid out better, and have some status highlights
2 Likes
Hi,
just stumbled across this and really like the idea.
But I dont get it to work, it displays no output in icingaweb2.
The logs say:
Uncaught ErrorException: Uncaught Zend_Controller_Response_Exception: Invalid HTTP response code in /usr/share/icinga-php/vendor/vendor/shardj/zf1-future/library/Zend/Controller/Response/Abstract.php:288
Any ideas?
Icinga2 Version 2.14.2-1+ubuntu24.04
icingadb Version 1.2.0-1+ubuntu24.04
icingaweb2 Version 2.12.1-1+ubuntu24.04
PHP-Version 8.3.6
icinga/icinga-php-library Version 0.14.1
icinga/icinga-php-thirdparty Version 0.12.1
Thanks,
Christian
thanks for checking it out @torcolato . Can you give me a view of your config at all? Modules → Clustergraph → config
@davekempe
API User/Password as configured in Icinga, with the permissions noted on the configuration page (“objects/query/Zone”, “objects/query/Endpoint”, “objects/query/Host”).
Api Endpoint fqdn of our icingahost like i.e. https://icinga.example.com
Port 5665
WebUI: tried both Icingaweb2 and Icingadb Web
Ouch.
Seems like the “https://” in API Endpoint was the mistake.
Using just the fqdn does the trick.
Sorry…
Ah yep. I should make that clearer in the documentation. Given port 5665 traffic is always https anyway, I figured it was redundant to have people put it in.
Does it look ok for you? The various cluster sizes can have trouble on various resolutions and screen sizes. I’m happy to take feedback on the layout. Its a tricky problem to find the balance.
Right now the module is installed in a test environment and output is looking really good.
Will give further information when it is used in a larger environment.
Thanks for your great work!