Slide 3 of 7

Where the mistakes happen

Where the mistakes happen

Cardinality problems usually enter a stack at ingestion setup, not in application code reviews. Enabling an integration with an app or service with default settings, such as the Kubernetes Monitoring Helm chart across all your clusters, can turn on thousands of metrics and labels at once. That visibility is valuable, but only if your budget expects it. When you set up a new integration:

  • Review what metrics the defaults send before pushing them to production.
  • Use allowlists to keep only the metrics and labels you’ll use.
  • Check the Cardinality tab after enabling anything new, and watch for New badges.

Script

You might expect cardinality problems to sneak in through application code reviews, but that’s usually not where they start. They usually enter at ingestion setup.

Enabling an integration with default settings, like the Kubernetes Monitoring Helm chart across all your clusters, can turn on thousands of metrics and labels at once. That visibility is valuable, but only if your budget expects it.

So treat every new integration as a labeling decision. Review what metrics the defaults send before pushing them to production, and use allowlists to keep only the metrics and labels you’ll use.

Then check the Cardinality tab after enabling anything new, and watch for the New badges.

Previous Next