search

Icinga / icingaweb2-module-vspheredb

The easiest way to monitor a VMware vSphere environment.
https://icinga.com/docs/vsphere/latest
GNU General Public License v2.0
100 stars 34 forks source link

High availability docs clarification #550

Open EmRowlands opened 9 months ago

EmRowlands commented 9 months ago

Expected Behavior

The "High availability" section in the FAQ should be explicit about what configurations work.

Current Behavior

https://github.com/Icinga/icingaweb2-module-vspheredb/blob/v1.7.1/doc/01-Installation.md

The current docs say that "using an active-active replication is the preferred way", but also says "please do not run multiple daemons writing into the same database". Does this mean that running multiple daemons is supported, but only if they write to different MariaDB instances in a cluster?

I also noticed #203, which states that the daemon should (amongst other things) "support starting multiple instances, with only one of them being active". This issue was closed as it was "implemented with v1.2". Does this mean that using multiple service instances is safe now?

Possible Solution

Update or clarify installation documentation.

Your Environment

skupjoe commented 9 months ago

Curious about this myself. Looking forward to official support for multiple vSphereDB agents in order to support multiple different vcenter connections in different networks.

I've been unofficially running multiple agents, and it does work, but there are times when they collide and get into a bad state, so I still don't think this is fully working and the design needs to be improved so agents are more aware of each other and can be restricted to certain vcenter assignments.