Hi InfluxDB Community,
We are exploring AWS Managed InfluxDB, which currently supports InfluxDB v2.7, and I have a question regarding cardinality limitations. According to the InfluxDB documentation, if series cardinality exceeds 10 million, InfluxDB recommends using the Enterprise version. However, I haven’t found any detailed explanation of the implications if we exceed this 10-million cardinality threshold.
Here’s an outline of our use case:
- Data Type: IoT data
- Measurement Names: device_type (e.g., sensors, camera, gateway, adv_security)
- Tags:
account_id
(10 million unique account IDs)partner
(up to 4 unique values)device_id
(each account can have approximately 5 unique devices)
- Fields: Varies based on
device_type
From my understanding, InfluxDB calculates cardinality based on the measurement name and unique tag key values. In our case, the unique combination of account_id
and device_id
should represent our maximum cardinality. However, in my testing, the cardinality seems to reflect only the unique account_id
, which I’m uncertain about.
My questions are:
- What will be the true cardinality calculation for our data structure?
- What are the potential implications or performance impacts if our cardinality exceeds 10 million on the AWS Managed InfluxDB (v2.7) setup?
Our estimated ingestion rate is around 200-300 events per second, with read requests in the range of 10-20 per second. Any insights on how this cardinality limit might affect performance or stability at these rates would be greatly appreciated!
Thanks in advance for your help!