I would like to express my concern regarding the current stagnation in the development of the vSphereDB module. Unfortunately, the ongoing lack of updates has led to considerable frustration, as our infrastructure relies heavily on this module. Depending on the feedback provided in this thread, we may be compelled to discontinue its use across more than 50 vCenters, as the current state is becoming increasingly unsustainable.
IcingaDB Support Support for Icinga DB · Issue #463 · Icinga/icingaweb2-module-vspheredb · GitHub
Open for several years. The transition to IcingaDB as the new standard occurred long ago, yet this module continues to lack compatibility. Unfortunately, there has been no visible progress or communication from the development team.
High Availability (HA) Support
Improved HA support is essential. The module remains the sole component in our monitoring stack incapable of handling simultaneous daemon instances effectively. Although prepared to failover to alternative nodes in emergency scenarios, data collection remains limited to a single endpoint due to database handling constraints (MariaDB/MySQL). This limitation was initially raised in 2019 (Issue #105) and reiterated recently (Issue #550), yet no progress or roadmap for resolution is apparent.
Additionally, several fixes have been merged into the main branch, but no new releases or tags have been published, creating uncertainty about their practical availability and stability.
The perceived lack of active maintenance is becoming increasingly problematic for our organization, and we are considering alternative solutions for our VMware monitoring requirements. My intention is not to criticize unnecessarily, but to clearly communicate the impact this situation has on our operations. A clear commitment to continued development, improved communication, or an indication of the project’s future roadmap would be greatly appreciated.
Thank you very much for your attention. I look forward to your feedback.
That’s funny, since just today I talked to a colleague about whether it might be a good idea to set up the vSphereDB module. We then had a look at the repo, and were wondering why the last release is from two years ago. Considering that, I’m also very interested in what is going on.
but since there is also a newer ticket / merge request for a CSP problem, this is of course not addressed here.
As for HA:
I think there a two ways to do that:
A)
2 databases
2 daemon
2 different resource inis on the two machines for the different databases
sync you vcenter credentials or configure them twice
If you use rules configure them twice or sync them
Both independent
B)
active-passive
use pacemaker or something else to start the daemon on the passive node
kill the deamon on the previous active node.
How do you solve “High Availability” the reporting service?
I share the concerns expressed here regarding the development trajectory of the entire Icinga project. Already at Icinga Camp 2023 (unfortunately, I couldn’t attend the 2024 event), I highlighted significant issues related to the high-availability (HA) capabilities of Icingaweb2 and its associated modules. Back then, as now, statements suggesting that HA should be managed externally rather than within Icinga itself were unsatisfactory. Such responses create the impression that responsibility for operating a critical 24x7 monitoring system is being shifted away from Icinga’s core competencies.
I was planning to implement the vSphereDB module shortly, but if it indeed lacks support in IcingaDB, I might need to reconsider my decision. Furthermore, the state of other modules, notably the Director—which currently struggles with a substantial backlog of issues and pull requests—is alarming.
Additionally, the absence of visible progress or clear direction in cloud monitoring capabilities is concerning. Competitors seem to be rapidly advancing in these areas, leaving Icinga increasingly behind.
I urge the Icinga team to communicate transparently about the project’s mid- to long-term strategy and roadmap. Clearly articulating future priorities, especially regarding HA, module support, and cloud integrations, would significantly benefit the user community and help regain confidence in Icinga’s ongoing viability.
