Telco system, that creates series per Access Point Name (APN) name as label value (similar to a user-id or a pod-IP but very much important to record)
/Teja On Tuesday, June 14, 2022 at 1:52:19 PM UTC+2 Stuart Clark wrote: > On 14/06/2022 12:32, tejaswini vadlamudi wrote: > > Thanks Stuart, this expectation is coming as a legacy requirement for > > a Telco cloud-native application that has huge cardinality (3000 > > values for a label-1) and little dimensionality (2 labels) for 300 > > metrics. > > > > Is there any recommendation like not more than 1k or 10k series per > > endpoint? > > The general expectation is that each Prometheus server would have no > more than a few million time series in total. The normal use case is to > have 10s/100s of jobs & targets, each exposing 100s/1000s of time > series, rather than a single target exposing significant number of time > series itself. > > If this is a single application what is the need for that level of > cardinality? For example something like a high volume e-commerce system > with millions of users might only need labels with say a cardinality of > a few 10s/100s each (for example HTTP status code, section of website, > etc.). What is it about this system that you think it needs very high > cardinality labels? > > -- > Stuart Clark > > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/4686a9de-20e6-466a-a26d-1eef8b04300an%40googlegroups.com.
