influxdata / influxdata/influxdb
Mathematics across measurements
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Apologies if this is a duplicate, I had a look and couldn't see a relevant issue.
I can see from the documentation how to select from multiple measurements (although it calls them series, still, at https://influxdb.com/docs/v0.9/query_language/data_exploration.html )
For example, with data inserted by telegraf, you can do:
select * from disk_used,disk_total where host = 'myhostname' and path = '/'
How would you express that as a percentage? I've tried variations of the following, and none seem to work:
select disk_used.value/disk_total.value from disk_used, disk_total where host = 'myhostname' and path='/'
The "mydb"."retentionpolicy"."measurement" syntax doesn't work there, either.
Is it a good idea to add aggregation functions for cases like diff(value1, value2) from m1, m2 and divide(value, value) from m1, m2, or should the arithmetic operators be working?
Also, I noticed when experimenting that it's also not possible to divide one derivative by another. For example, if I have two counters, bytes transferred and api calls made - both of which are constantly going up - how would you calculate the mean bytes per api call?
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
Start with the linked data exploration documentation and reproduce the cross-measurement percentage and derivative queries described in the issue. The issue names no source files or tests; completion would require a decided query-language behavior for arithmetic across measurements and corresponding validation.
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
- 25/100