We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
MetricFetcher
Related to #1615 (comment)
localReceiver 將所有目標的 metric 拉下來 -> 過濾 -> 儲存。 然而,當 kafka cluster 內有許多 partition 時,metric 的數量也會增大。(數量大約是 2000 partition broker 大約要拉 20615 metric, 0 partition broker 大約要拉 614 metrics)
localReceiver
所以,若是只拉取需要的 metric 將有機會大大降低 "metric 拉下來" 的時間。 數量的來源主要是 partition level 的 metric,所以我認為把可以剔除不必要的 "partition level metric" 就好。
這裡討論有哪些 metric 是需要拉取的,我先列出 NetworkCost 會用到的 metric ,以及所有 metric 的數量級,供大家參考。
The text was updated successfully, but these errors were encountered:
@chinghongfang 感謝建議,#1622 有提一個類似的作法,目前我們先以拉取 built-in 會用到的 beans就好,妳覺得如何
Sorry, something went wrong.
No branches or pull requests
Related to #1615 (comment)
localReceiver
將所有目標的 metric 拉下來 -> 過濾 -> 儲存。然而,當 kafka cluster 內有許多 partition 時,metric 的數量也會增大。(數量大約是 2000 partition broker 大約要拉 20615 metric, 0 partition broker 大約要拉 614 metrics)
所以,若是只拉取需要的 metric 將有機會大大降低 "metric 拉下來" 的時間。
數量的來源主要是 partition level 的 metric,所以我認為把可以剔除不必要的 "partition level metric" 就好。
這裡討論有哪些 metric 是需要拉取的,我先列出 NetworkCost 會用到的 metric ,以及所有 metric 的數量級,供大家參考。
NetworkCost
All metrics
The text was updated successfully, but these errors were encountered: