The Power and Cost of Data Cardinality

"The more attributes you add to your metrics, the more complex and valuable questions you can answer. Every additional attribute provides a new dimension for analysis and troubleshooting. For instance, adding an infrastructure attribute, such as region can help you determine if a performance issue is isolated to a specific geographic area or is widespread. Similarly, adding business context, like a store location attribute for an e-commerce platform, allows you to understand if an issue is specific to a particular set of stores"

"There is a cost to that additional power beyond the effort required to add it to the data. Increased Resources and Volume: More attributes mean larger data points, which require more resources to transfer and process the data. Higher Cardinality is a Key Cost Driver: More attributes generally lead to higher cardinality, and cardinality is a key driver of cost for metrics. Metric data is aggressively aggregated to keep queries fast, but this aggregation requires"

Effectively managing data cardinality balances analytical granularity against resource and cost constraints. Adding attributes increases the number of dimensions available for analysis and troubleshooting. Infrastructure attributes like region and business attributes like store location enable isolation of issues and correlation with business metrics such as revenue. Granular identifiers like user ID, product ID, or search query support deep trend and behavioral analysis. Each additional attribute increases data volume and processing requirements. Higher attribute counts raise cardinality, which drives metric storage and processing costs. Aggregation techniques keep queries fast but introduce storage, compute, and complexity trade-offs.

Read at New Relic