influxdata / influxdata/influxdb
Best way to store/design metrics
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Hello all,
I am designing the best architecture for a large scale system based on InfluxDB and I have a doubt regarding the best way to store the data as thanks to telegraf and pivot processor I have 2 identified options to store "same" data. Would you be so kind as to tell me the benefits or drawbacks of using one or other method? Here you have an example of the two options:
OPTION1
MillingMachine1,country=spain,plant=madrid speed=82,torque=50 1465839830100400200
OPTION2
speed,country=spain,plant=madrid,machine=MillingMachine1 value=82 1465839830100400200
torque,country=spain,plant=madrid,machine=MillingMachine1 value=50 1465839830100400200
Thanks in advance for your advices.
Contributor guide
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
No repository files, tests, or entry points are mentioned. Start by comparing the two InfluxDB schemas described in the issue and reviewing the relevant data-modeling guidance; done would require a settled architectural recommendation, which the issue does not define.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100