Re: [prometheus-users] Separate endpoint for aggregate metrics?

2023-03-30 Thread Brian Candler
Right: high cardinality is bad. But what matters is the number of timeseries which have ingested a point in the last ~2 hours. Whether each of those time series ingests 1 data point or 10,000 data points in 2 hours makes almost no difference. Therefore, scraping them less frequently doesn't

Re: [prometheus-users] Separate endpoint for aggregate metrics?

2023-03-29 Thread Kevin Z
This label scales as users interact with our server and create new accounts. It is problematic right now because it currently is added to all metrics. On Monday, March 27, 2023 at 1:39:57 AM UTC-7 Stuart Clark wrote: > On 2023-03-25 07:30, Kevin Z wrote: > > Hi, > > > > We have a server that

Re: [prometheus-users] Separate endpoint for aggregate metrics?

2023-03-27 Thread Stuart Clark
On 2023-03-25 07:30, Kevin Z wrote: Hi, We have a server that has a high cardinality of metrics, mainly due to a label that is tagged on the majority of the metrics. However, most of our dashboards/queries don't use this label, and just use aggregate queries. There are specific scenarios where

[prometheus-users] Separate endpoint for aggregate metrics?

2023-03-26 Thread Kevin Z
Hi, We have a server that has a high cardinality of metrics, mainly due to a label that is tagged on the majority of the metrics. However, most of our dashboards/queries don't use this label, and just use aggregate queries. There are specific scenarios where we would need to debug and sort