@andyfeller Ideally you have a standard set of fields/tags within the same measurement. That, as you astutely point out, means that you can have data that is orthogonal in the same measurement. This is not recommended and is not a performant way to store data. There are use cases where this can be advantageous and, because we are a columnar store, performant (this post is a good example).
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Example of single measurement belonging to different retention policies | 4 | 4276 | June 18, 2019 | |
| What's the logical connection between buckets, measurements & retention policies in InfluxDB 2.0? | 5 | 9035 | May 26, 2023 | |
| Best practices for choosing measurement, tags and fields | 15 | 2723 | August 4, 2025 | |
| Influxdb performance tuning question | 0 | 872 | March 6, 2019 | |
| Single database+multiple measurements vs Multiple databases | 6 | 4398 | September 20, 2022 |
