The situation here is that out team provide centralized prometheus service,
while other
teams maintain their own exporter and pulled by our prometheus service. So
the reason
for a "white list" is that I'm trying to do ratelimit for my prometheus
service, on dimensions
of metrics.
在2021年7月19日星期
On 19/07/2021 13:57, Yingtao Wang wrote:
thanks for your reminding. A "white list" is actually what I'm trying
to do. If some
useful metrics be dropped by relabling rules, that would be OK. For
now I need to
init my white list by metrics currently using in dashboards and alert
rules. So a way
t
thanks for your reminding. A "white list" is actually what I'm trying to
do. If some
useful metrics be dropped by relabling rules, that would be OK. For now I
need to
init my white list by metrics currently using in dashboards and alert
rules. So a way
to find out these metrics is what I'm looki
thanks for your reminding. A "white list" is actually what I'm trying to
do. If some
useful metrics be dropped by relabling rules, that would be OK. For now I
need to
init my white list by metrics currently using in dashboards and alert
rules. So a way
to find out these metrics is what I'm looki
On 2021-07-19 10:36, Yingtao Wang wrote:
Hi, I'm trying to analyze metrics scraped from the same instance. And
I want to find out among these metrics, how many metrics are rarely or
never be queried, which means these metrics are not necessary thus no
need to be stored. Then I can drop this kind
Hi, I'm trying to analyze metrics scraped from the same instance. And I
want to find out among these metrics, how many metrics are rarely or never
be queried, which means these metrics are not necessary thus no need to be
stored. Then I can drop this kind of metrics using metric_relabel configs.
6 matches
Mail list logo
