View Issue Details

IDProjectCategoryView StatusLast Update
0008302Talerdeployment and operationspublic2026-09-19 14:40
Reporterjavier.sepulveda Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeveritytextReproducibilityhave not tried
Status informingResolutionreopened 
Product Versiongit (master) 
Target Version1.6Fixed in Version1.6 
Summary0008302: Current monitoring tools - Write documentation
DescriptionAt this point we have currently up and running: Netdata, Grafana and Kuma.
So write documentation about what exactly is being monitored by each program.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

javier.sepulveda

2024-02-07 13:18

reporter   ~0021193

Agreed to create a completely new .rst file under docs.git

javier.sepulveda

2024-02-14 13:16

reporter   ~0021290

Doing quite good progress with drafting of this document. Right now I do have quite a nice skeleton of it, and are getting into the detail of each section.

javier.sepulveda

2024-03-05 12:56

reporter   ~0021672

Pushed to git the reviewed Draft. Still need to be linked somewhere in the --menu.
Even though I refer in this document to Loki and Promotail, yet, we don't have them installed on taler.net (loki+promtail). Installing those packages is easy, but
configuring the logs is another story. I need to --learn first how to manage Loki+Promtail through
the Grafana admin panel, and after that learn how to track specific logs.
Nowadays, there is different and opened bug for that 0008303.

Christian Grothoff

2024-03-07 08:29

manager   ~0021746

Did you forget to Git add images?

/research/taler/docs/taler-monitoring-infrastructure.rst:24: WARNING: image file not readable: images/taler-monitoring-infrastructure.png
/research/taler/docs/taler-monitoring-infrastructure.rst:91: WARNING: image file not readable: images/grafana-postgres-exporter.png
/research/taler/docs/taler-monitoring-infrastructure.rst:108: WARNING: image file not readable: images/uptime-kuma-from-grafana.png
/research/taler/docs/taler-monitoring-infrastructure.rst:170: WARNING: image file not readable: images/kuma.png
/research/taler/docs/taler-monitoring-infrastructure.rst:197: WARNING: image file not readable: images/uptime-kuma-edit.png

javier.sepulveda

2024-03-07 08:32

reporter   ~0021747

Yes. I realized that yesterday and added to my caldav tasks. I will do that in not time. Thank you.

javier.sepulveda

2024-03-07 11:53

reporter   ~0021755

I have checked this, as I was sure I had copied those images to the --images folder beforehand. So I thought doing "git add ." would have include them.
Now I can see, the .gitignore is avoiding to track these .png files.

# generated images
*.png

So, no idea what's the plan now. As until I can't change the .gitignore file, I won't able to commit to add these images files.
I can find my way to upload them manually but I am not sure if this what we want to do forever, when adding image files on the rst files.

javier.sepulveda

2024-03-11 08:08

reporter   ~0021832

Added missing image files by using: git add -f
I will add that to my notes, to take that into account for the next time.

Christian Grothoff

2024-03-12 12:59

manager   ~0021864

Last edited: 2024-03-18 11:19

Reopening now to give feedback on both documentation and the setup.

1) In the main figure on top, it would be good to consistently have the real hostnames (not: TALER OPS, not: "external server") in the architecture diagram. Also, we have 6 internal machines: firefly.gnunet.org (BFH), sam.gnunet.org (TUM), gv.taler.net (BFH), $tbd.taler.net (TUE), anastasis.lu (contabo) and taler-ops.ch (hosttech). They are at 5 different hosters -- that should be *plenty* to run the uptime kuma servers _within_ our own infrastructure instead of depending on any external hosts. I propose we run one at TUE, and a second one at contabo. Also, we should monitor _all_ of our hosts, not just taler.net and taler-ops.ch. In fact, we should now *also* start monitoring exchange.e.netzbon-basel.ch ;-). The diagram should also say where grafana is hosted.

2) Grafana dashboards: Marco Boss had developed some taler-specific Grafana dashboards as part of this BS thesis. You can find them in the grid5k.git, and probably should unearth and deploy them (and then document that).

3) The Node exporter, Postgres exporter and Prometheus seem perfect targets for an Ansible playbook for taler-ops.ch (and in the future other hosts).

4) Managing logs: it is totally unclear from what you write *where* this is done.

Christian Grothoff

2024-06-26 16:08

manager   ~0022730

Javier, are you working on this? Please try to address this for 0.13!

Florian Dold

2026-09-11 13:34

manager   ~0029952

There's now basic documentation for the monitoring setup in taler-docs.git and more extensive documentation in tsys-infra.git/monitoring.

Issue History

Date ModifiedUsernameFieldChange
2024-02-01 09:17javier.sepulvedaNew Issue
2024-02-01 09:17javier.sepulvedaStatusnew => assigned
2024-02-01 09:17javier.sepulvedaAssigned To => javier.sepulveda
2024-02-07 13:18javier.sepulvedaNote Added: 0021193
2024-02-14 13:16javier.sepulvedaNote Added: 0021290
2024-02-14 13:28Christian GrothoffSeverityminor => text
2024-02-14 13:28Christian GrothoffTarget Version => 0.11
2024-03-05 12:56javier.sepulvedaNote Added: 0021672
2024-03-05 12:56javier.sepulvedaAssigned Tojavier.sepulveda => Christian Grothoff
2024-03-05 12:56javier.sepulvedaStatusassigned => feedback
2024-03-07 08:29Christian GrothoffNote Added: 0021746
2024-03-07 08:30Christian GrothoffAssigned ToChristian Grothoff => javier.sepulveda
2024-03-07 08:32javier.sepulvedaNote Added: 0021747
2024-03-07 11:53javier.sepulvedaNote Added: 0021755
2024-03-11 08:08javier.sepulvedaNote Added: 0021832
2024-03-12 08:03javier.sepulvedaStatusfeedback => informing
2024-03-12 08:03javier.sepulvedaResolutionopen => fixed
2024-03-12 12:46Christian GrothoffProduct Version => git (master)
2024-03-12 12:46Christian GrothoffFixed in Version => 0.10
2024-03-12 12:46Christian GrothoffTarget Version0.11 => 0.10
2024-03-12 12:48Christian GrothoffAssigned Tojavier.sepulveda => Christian Grothoff
2024-03-12 12:48Christian GrothoffStatusinforming => feedback
2024-03-12 12:48Christian GrothoffResolutionfixed => reopened
2024-03-12 12:59Christian GrothoffNote Added: 0021864
2024-03-13 16:19Christian GrothoffView Statusprivate => public
2024-03-18 11:19Christian GrothoffNote Edited: 0021864
2024-03-18 11:19Christian GrothoffAssigned ToChristian Grothoff => javier.sepulveda
2024-03-18 11:20Christian GrothoffStatusfeedback => assigned
2024-04-12 16:10Christian GrothoffPrioritynormal => high
2024-04-12 16:10Christian GrothoffFixed in Version0.10 =>
2024-04-12 16:10Christian GrothoffTarget Version0.10 => 0.11
2024-05-13 19:22Christian GrothoffTarget Version0.11 => 0.12
2024-06-26 16:08Christian GrothoffTarget Version0.12 => 0.13
2024-06-26 16:08Christian GrothoffNote Added: 0022730
2024-07-25 22:35Christian GrothoffTarget Version0.13 => 0.14
2024-09-07 15:24Christian GrothoffAssigned Tojavier.sepulveda =>
2024-09-07 15:24Christian GrothoffStatusassigned => implementing
2024-09-07 15:24Christian GrothoffTarget Version0.14 => 1.0
2024-12-29 16:22dvnAssigned To => dvn
2024-12-29 16:22dvnStatusimplementing => assigned
2025-02-02 23:00Christian GrothoffTarget Version1.0 => 1.0 stretch goals
2025-04-25 05:17Christian GrothoffTarget Version1.0 stretch goals => post-1.0
2025-06-21 21:00Christian GrothoffAssigned Todvn =>
2025-06-21 21:00Christian GrothoffStatusassigned => implementing
2026-09-11 13:34Florian DoldAssigned To => Florian Dold
2026-09-11 13:34Florian DoldStatusimplementing => informing
2026-09-11 13:34Florian DoldNote Added: 0029952
2026-09-19 14:38Christian GrothoffTarget Versionpost-1.0 => 1.6
2026-09-19 14:40Christian GrothoffFixed in Version => 1.6