- 07 Sep, 2017 2 commits
-
-
Mitsuhiro Tanda committed
-
* (prometheus) cache metric suggest query result * add test
Mitsuhiro Tanda committed
-
- 06 Sep, 2017 3 commits
-
-
* Prometheus: Fix actual step computation logic when a min_step is specified and the range is longer than min_step * 11000. * Have the 'Hide series with only zeros' option also apply to series with some null values.
Alin Sinpalean committed -
Patrick O'Carroll committed
-
Torkel Ödegaard committed
-
- 05 Sep, 2017 8 commits
-
-
Torkel Ödegaard committed
-
Fixing type of parameters from "select" to "boolean" for working with carbonapi (like it was done in summarize function) + some commas prettify.
Sergey Korobov committed -
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Make it clearer that it only works with basic auth
Daniel Lee committed
-
- 04 Sep, 2017 14 commits
-
-
bergquist committed
-
Add the missing step of "grunt build" to the README.md
Carl Bergquist committed -
Allen committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
- use charset would issue additional 'SET NAMES <VALUE>' queries, set collation would be better. see: https://github.com/go-sql-driver/mysql#charset
mxlxm committed -
Torkel Ödegaard committed
-
bergquist committed
-
- 01 Sep, 2017 5 commits
-
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Marcel Anacker committed
-
Nevins committed
-
Torkel Ödegaard committed
-
- 31 Aug, 2017 5 commits
-
-
Torkel Ödegaard committed
-
plugin change: make interval, cache timeout & max data points options in plugin.json, remove query.options component feature, add help markdown feature and toggle for data sources
Torkel Ödegaard committed -
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
The generated queries when selecting multiple tags are incorrect. In InfluxQL, `AND` has a higher precedence than `OR` so the condition: WHERE "hostname" = 'server1' OR "hostname" = 'server2' AND time > now() - 5m This is parsed as if it were: WHERE "hostname" = 'server1' OR ("hostname" = 'server2' AND time > now() - 5m) But the intention is to write a query like this: WHERE ("hostname" = 'server1' OR "hostname" = 'server2') AND time > now() - 5m This change modifies the generated query so it surrounds a query with multiple conditions in parenthesis so it doesn't conflict with the time expression in an unexpected way. This is currently not an issue because InfluxDB doesn't actually evaluate the condition for the time expression correctly. It just looks through the AST for anything that looks like a time expression and then assumes the proper format of `AND` was used rather than validating that it was used correctly.
Jonathan A. Sternberg committed
-
- 30 Aug, 2017 2 commits
-
-
Torkel Ödegaard committed
-
ref #9002
Daniel Lee committed
-
- 29 Aug, 2017 1 commit
-
-
: Please enter a commit message to explain why this merge is necessary,
Torkel Ödegaard committed
-