View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008641 | Taler | deployment and operations | public | 2024-03-14 10:44 | 2025-01-27 13:53 |
| Reporter | javier.sepulveda | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| 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. | ||||
| related to | 0009482 | resolved | Christian Grothoff | monitoring should check for non-empty global fees |
|
|
The following jsonata code will work for monitoring a /keys exchange for expiration using uptime-Kuma. We should use it in HTTPS JSON-query mode for all /keys endpoints: $min($append($append( [$max($map(global_fees, function($f) { $f.end_date.t_s}))], [$max($map(signkeys, function($f) { $f.stamp_expire.t_s}))]), [$max($map(denominations,function ($a){ $max($map($a.denoms, function ($d){ $d.stamp_expire_withdraw.t_s } )) } ))])) > $millis()/1000 |
|
|
Documented in docs.git :: dcbc9ea5..a5396bcd |
| 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 |
| 2024-07-28 21:55 | Christian Grothoff | Severity | minor => feature |
| 2024-07-28 22:09 | Christian Grothoff | Target Version | => post-1.0 |
| 2024-09-07 17:26 | Christian Grothoff | Assigned To | javier.sepulveda => |
| 2024-09-07 17:26 | Christian Grothoff | Status | assigned => confirmed |
| 2024-09-07 17:26 | Christian Grothoff | Product Version | => git (master) |
| 2024-09-07 17:26 | Christian Grothoff | Target Version | post-1.0 => 1.0 stretch goals |
| 2024-12-07 22:54 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-12-07 22:54 | Christian Grothoff | Status | confirmed => assigned |
| 2024-12-27 16:17 | Christian Grothoff | Note Added: 0023916 | |
| 2024-12-27 16:41 | Christian Grothoff | Note Added: 0023917 | |
| 2024-12-27 16:41 | Christian Grothoff | Status | assigned => resolved |
| 2024-12-27 16:41 | Christian Grothoff | Resolution | open => fixed |
| 2024-12-27 16:41 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2024-12-27 16:41 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.0 |
| 2025-01-27 13:53 | Christian Grothoff | Relationship added | related to 0009482 |
