diff options
| author | Paul Buetow <paul@buetow.org> | 2023-06-01 20:58:56 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2023-06-01 20:58:56 +0300 |
| commit | 0abc740292463d29c1d28e74ec1967864746a2c1 (patch) | |
| tree | e3d94dfaa9c37e7e58afcffff0897710141b93f4 /README.md | |
| parent | 125c4c8a8d6e78e55d6d88977c1f8a244c07b6a4 (diff) | |
mention Gorumv1.0.2
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -177,7 +177,8 @@ To create a high-availability Gogios setup, you can install Gogios on two server * Install the NRPE server (out of scope for this document) and plugin on both servers. This plugin allows you to execute Nagios check scripts on remote hosts. * Configure Gogios on both servers to monitor each other using the NRPE plugin. Add a check to the Gogios configuration file (`/etc/gogios.json`) on both servers that uses the NRPE plugin to execute a check script on the other server. For example, if you have Server A and Server B, the configuration on Server A should include a check for Server B, and vice versa. * Set up alternate CRON intervals on both servers. Configure the CRON job on Server A to run Gogios at minutes 0, 10, 20, ..., and on Server B to run at minutes 5, 15, 25, ... This will ensure that if one server goes down, the other server will continue monitoring and sending notifications. -* Gogios doesn't support clustering. So it means when both servers are up, unhandled alerts will be notified via E-Mail twice; from each server once. That's the trade-off for simplicity. +* Gogios doesn't support clustering. So it means when both servers are up, unhandled alerts will be notified via E-Mail twice; from each server once. That's the trade-off for simplicity. +* There are plans to make it possible to execute certain checks only on certain nodes (e.g. on elected leader or master nodes). This is still in progress (check out my `Gorum` git project). # But why? |