action #127265
openAdd timestamp to influxdb openqa_download_rate size:M
0%
Description
Motivation¶
The endpoint is /influxdb/minion
- note that it is only accessible within the worker.
At the end of a download we measure the download rate and save it to the minion database.
When the influxdb route is called by telegraf, we report this value, even if it stays the same
because no new download happened meanwhile.
But the download rate is just measured at a certain point, so it would be more correct to add a timestamp
to the influxdb output, so it wouldn't record the same value for different timestamps.
It would also result in less data in the influxdb.
Acceptance criteria¶
- AC1: The timestamp of the last update is included in each row
- AC2: InfluxDB does not take records if the data does not change anyways
- AC3: Graphs on Grafana are not impacted (e.g. no gaps)
Suggestions¶
- Make sure not to confuse the similarly named webui endpoint with this one, this feature is about the cache service running on workers
- Introduce a new field in the database that saves the timestamp of the last update.
- Use the metrics sqlite storage from the cache service
Updated by tinita over 1 year ago
- Copied from action #127055: [alert] Download rate alert openQA (openqaworker{14,16,17,18}) added
Updated by mkittler over 1 year ago
This is mainly about the Minion service on the workers (and not https://openqa.opensuse.org/admin/influxdb/minion which would be on the web UI host).
Updated by okurz over 1 year ago
- Due date deleted (
2023-04-19) - Target version set to Ready
- Start date deleted (
2023-04-01)
Updated by livdywan over 1 year ago
- Subject changed from Add timestamp to influxdb openqa_download_rate to Add timestamp to influxdb openqa_download_rate size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz over 1 year ago
- Target version changed from Ready to future
As suggested by the team removing more low tickets from backlog as we are exceeding our backlog length