diff options
| author | Paul Buetow <paul@buetow.org> | 2023-04-23 01:20:13 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2023-04-23 01:20:13 +0300 |
| commit | 9d5421902f0ca5d4ad8a12f7e98455e6b632ae4a (patch) | |
| tree | b56b7ad52bde64a208cead9bf7f9441a794a93c7 | |
| parent | 553d963d55bc026a0f65a21755963bfb91461e2f (diff) | |
typo
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -156,7 +156,7 @@ 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. # But why? |