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
Getting generic system information (Disk usage, etc) once per hour would be fine.
For application-defined metrics we are happy with more fine-grained intervals.
Right now we need to use the lowest common value. This leads to increased costs in terms of network traffic, ingestions, and storage costs.
What we suggest is an extension of the behavior of BlockedMetrics towards a new element like "TimeFilteredMetrics". This would basically be a list of elements consisting of
a time definition ala ScrapeFrequencyInSecs.
A regex of metrics ala BlockedMetrics
This would block reporting of the included metrics unless at least the specified frequency has been passed.
Any thoughts on this, would this be useful? Would you be willing to accept a PR for such a change?
Hi!
Currently, we can control the drequency of scraping via ScrapeFrequencyInSecs.
However, we have different requirements for various metrics in terms of granularity.
https://github.com/Azure/iotedge/blob/main/edge-modules/metrics-collector/src/README.md
Practical example:
Right now we need to use the lowest common value. This leads to increased costs in terms of network traffic, ingestions, and storage costs.
What we suggest is an extension of the behavior of BlockedMetrics towards a new element like "TimeFilteredMetrics". This would basically be a list of elements consisting of
This would block reporting of the included metrics unless at least the specified frequency has been passed.
Any thoughts on this, would this be useful? Would you be willing to accept a PR for such a change?
Note: I have also posted this at https://feedback.azure.com/d365community/idea/e929bf5b-fa40-ee11-a81c-000d3a040137.
But scrolling over that, it appears to have little to no activity.
Thanks and best regards,
Florian
The text was updated successfully, but these errors were encountered: