commit decefd9999dd49c0e87ac9b0a97510f9b33e85eb
parent de939ff8e91bb2cd5b4227a42a365c4cb928d201
Author: Javier Sepulveda <javier.sepulveda@uv.es>
Date: Fri, 17 May 2024 10:52:46 +0200
Corrections and adaptations to the new uptimekuma servers
Diffstat:
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/taler-monitoring-infrastructure.rst b/taler-monitoring-infrastructure.rst
@@ -24,14 +24,15 @@ GNU Taler monitoring
In order to check the availability of our server infrastructure, we use the Grafana and Uptime KUMA monitoring programs.
-On the one hand Grafana let us to see *graphically* the server consumption resources, and even alert us of some specific situations.
+On the one hand Grafana enables us to see *graphically* the server consumption resources, and even alert us of some specific situations.
On the other hand with a more basic tool such as Uptime KUMA (which does mostly ping and https checks),
-we get the very first status information, as the very first countermeasure.
+we get the very first status information, as a very first countermeasure.
Grafana
=======
- Our grafana instance can be reached at https://grafana.taler.net
+- Our grafana instance is installed on the (TUE) server
User accounts:
--------------
@@ -162,19 +163,22 @@ Grafana Alerting
Uptime Kuma
===========
-- URL: http://139.162.254.179:3001/dashboard
+- URL: https://uptimekuma.anastasis.lu (main)
- Users: One single administration account with full privileges.
-- Installation: With Docker
+- Installation: Without docker. All within the user home folder /home/uptime-kuma
+- Monitors almost all our servers, websites and certificates expiration dates.
+
+- URL: https://uptimekuma.taler.net
+- Users: One single administration account with full privileges.
+- Installation: Without docker. All within the user home folder /home/uptime-kuma
+- Monitors the "main" uptimekuma installation, to make sure it is up and running, and doing the monitoring properly.
.. image:: images/kuma.png
.. note::
- 1) In order to guarantee the KUMA is doing its work, it needs to be install 100% externally from the servers you want to monitor. (Server Kuma 1)
- 2) Also, it is important to monitor the KUMA server itself, so you don't endup without a monitoring system. (Server Kuma 2)
-
-In our case, we do both. We have the two Uptime KUMA servers completely outside our server infrastructure, so one monitors the other, and
-the latter one, monitors our own Taler servers.
+ 1) The main uptimekuma installation is under the server anastasis.lu
+ 2) The second uptimekuma installation on top, is installed on gv.taler.net.
Kuma monitor types
-------------------
@@ -187,9 +191,10 @@ expiration dates.
So in brief in our KUMA main server, we use these 3 monitor types (ping,https,certificate expiration) for each website that we monitor.
-Exceptionally for additional notifications, and specifically due of the importance of the Taler Operations server,
-we use in addition SMS notifications (clicksend provider). This way in case of KUMA detecting the Taler Operations unavailability,
-a SMS message will be sent to at the very least two persons from the deployment and operations department.
+Exceptionally for high priority notifications for essential services, and specifically due of the importance of the Taler Operations production
+server, we use in addition SMS notifications (Clicksend provider). This way in the case the main uptimekuma detecting the Taler Operations server unavailability, or any other essential service such as GIt,
+a SMS message would be sent to the system administrator and eventually some other team member of the deployment and operations department, for urgent action.
+
How to edit notifications:
