@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 | |
|---|---|---|---|---|
| Single database+multiple measurements vs Multiple databases | 6 | 4220 | September 20, 2022 | |
|
Using same measurement name with different retention policies
|
1 | 385 | April 6, 2021 | |
| One measurement with two retention policies possible? | 1 | 818 | March 26, 2018 | |
| How to configure different retention policies for different measurements | 10 | 7961 | April 18, 2019 | |
| Example of single measurement belonging to different retention policies | 4 | 4206 | June 18, 2019 |
