Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable scrape frequency for different metrics #7086

Open
florianfischerx opened this issue Aug 22, 2023 · 1 comment
Open

Variable scrape frequency for different metrics #7086

florianfischerx opened this issue Aug 22, 2023 · 1 comment

Comments

@florianfischerx
Copy link

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:

  • 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?

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

@github-actions
Copy link

This issue is being marked as stale because it has been open for 30 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant