Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
As far as I understand, hw-health at the moment sends health reports to core with a fixed frequency. The fixed frequency has a tradeoff
- if sending is too infrequent, there is a delay in signalling problems (e.g. leaks)
- if sending is too frequent, the load on the core api server increases
Feature Description
To achieve a tradeoff, we can implement sending health reports with variable frequency:
- If a health reports would get sent that has the same contents as the last sent health report, the frequency can be reduced. This would only lead to a visibility delay if the core-server was restarted.
- If the health report contains a new alert, the report can be forwarded earlier.
- If the health report contains no alert, the report can be forwarded later
The logic can probably be contain in an extra crate/library, so that it can be reused by multiple components that need to transmit health reports.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
As far as I understand, hw-health at the moment sends health reports to core with a fixed frequency. The fixed frequency has a tradeoff
Feature Description
To achieve a tradeoff, we can implement sending health reports with variable frequency:
The logic can probably be contain in an extra crate/library, so that it can be reused by multiple components that need to transmit health reports.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct