influxdata / influxdata/docs-v2
docs mention a possible source of high cardinality but offer no advice for this issue
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
_Describe the issue here._
The docs mention a specific type of issue that can cause high cardinality, but then offer no advice to alleviate the issue.
> Unique tag values that grow over time For example, a user ID tag may work at a small startup, but may begin to cause issues when the company grows to hundreds of thousands of users.
We have lots of devices pushing data, with their ID as a tag which is required so it can be searched. So what do?
##### Relevant URLs
- https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/resolve-high-cardinality/
- _Provide other relevant URLs (project issues, community threads, etc.)_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the high-cardinality guidance at the linked InfluxDB documentation URL and review the section on unique tag values that grow over time. Clarify the advice for users who need device IDs searchable as tags, then verify that the page explains practical alternatives or mitigation steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100