You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After [identification of metrics](see #661) we can implement collecting those metrics.
To avoid putting postgresql database under too much stress we would prefer to collect info in the monitoring influxdb database, using a recurring task in scheduler.
Hourly granularity might be enough.
Ideally we should remember last time we computed the metric, to be able to fill the gap if the metric was stalled for some time (maybe add a table to store when each task was last run). This could also be a way to bootstrap a new metric and add previous data that can be computed.
This discussion was converted from issue #662 on August 29, 2023 13:07.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After [identification of metrics](see #661) we can implement collecting those metrics.
To avoid putting postgresql database under too much stress we would prefer to collect info in the monitoring influxdb database, using a recurring task in scheduler.
Hourly granularity might be enough.
Ideally we should remember last time we computed the metric, to be able to fill the gap if the metric was stalled for some time (maybe add a table to store when each task was last run). This could also be a way to bootstrap a new metric and add previous data that can be computed.
Beta Was this translation helpful? Give feedback.
All reactions