View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008641 | Taler | deployment and operations | public | 2024-03-14 10:44 | 2024-03-14 10:44 |
| Reporter | javier.sepulveda | Assigned To | javier.sepulveda | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0008641: Take into account Taler "keys" while monitoring with Grafana. | ||||
| Description | During the "all-hands" Taler mumble call of this month, this matter came up, and I was requested to file this bug. But as I said I am not familiar enough with either specific Taler content, or even with grafana graphical backend features to create tailored rules for monitoring specific Taler things. Yet, the Loki service and the Promtail service, are not installed on gv.taler.net. These will be installed directly on the new Taler server (TUE), as if I am not yet able (lack of time to devote time to learn the Grafana Loki insights) to create these specific Loki rules by hand (I tried in a test server, but I couldn't 0008303) When trying to create new rules by hand I I realized it was a whole world where I knew nothing. Not only about managing those Grafana Loki+Promtail forms, but to link them to either specific logs or Taler content. So probably to either achieve to monitor "Taler keys" or "Taler logs", we will have to do a joint job among the parties that can shed some light on this. As soon as I get installed this Loki+Promtail tools in the new server, I will update this thread. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-14 10:44 | javier.sepulveda | New Issue | |
| 2024-03-14 10:44 | javier.sepulveda | Status | new => assigned |
| 2024-03-14 10:44 | javier.sepulveda | Assigned To | => javier.sepulveda |
