This project is mirrored from Updated .
  1. 09 Jun, 2020 1 commit
  2. 20 Mar, 2020 1 commit
  3. 13 Mar, 2020 1 commit
  4. 17 Feb, 2020 2 commits
  5. 14 Mar, 2019 1 commit
  6. 16 Jan, 2019 1 commit
  7. 08 Jan, 2019 1 commit
  8. 07 Jan, 2019 1 commit
  9. 04 Jun, 2018 1 commit
  10. 07 Jul, 2017 1 commit
  11. 26 Aug, 2015 1 commit
    • Fix most golint warnings. · 995d3b83
      This is with `golint -min_confidence=0.5`.
      I left several lint warnings untouched because they were either
      incorrect or I felt it was better not to change them at the moment.
      Julius Volz authored
  12. 18 May, 2015 5 commits
  13. 28 Apr, 2015 1 commit
    • Refactor query evaluation. · 5602328c
      This copies the evaluation logic from the current rules/ package.
      The new engine handles the execution process from query string to final result.
      It provides query timeout and cancellation and general flexibility for
      future changes.
      functions.go: Add evaluation implementation. Slight changes to in/out data but
      	not to the processing logic.
      quantile.go: No changes.
      analyzer.go: No changes.
      engine.go: Actually new part. Mainly consists of evaluation methods
      	which were not changed.
      setup_test.go: Copy of rules/helpers_test.go to setup test storage.
      promql_test.go: Copy of rules/rules_test.go.
      Fabian Reinartz authored
  14. 17 Apr, 2015 1 commit
  15. 16 Apr, 2015 2 commits
  16. 16 Mar, 2015 2 commits
  17. 05 Mar, 2015 1 commit
  18. 03 Mar, 2015 2 commits
    • Fix unary +/- expressions. · 182de6b9
      Unary expressions cause parsing errors if they are done in the lexer
      by tokenizing them into the number.
      This fix moves unary expressions to the parser.
      Fabian Reinartz authored
    • Add OR operation and vector matching options. · 6f754073
      This commits implements the OR operation between two vectors.
      Vector matching using the ON clause is added to limit the set of
      labels that define a match between two elements. Group modifiers
      (GROUP_LEFT/GROUP_RIGHT) to request many-to-one matching are added.
      Fabian Reinartz authored
  19. 02 Mar, 2015 1 commit
  20. 01 Mar, 2015 1 commit
    • Support scientific notation and special float values. · c2ab54e9
      This adds support for scientific notation in the expression language, as
      well as for all possible literal forms of +Inf/-Inf/NaN.
      TODO: Keep enough state in the parser/lexer to distinguish contexts in
      which "Inf", "NaN", etc. should be parsed as a number vs. parsed as a
      label name. Currently, foo{nan="bar"} would be a syntax error. However,
      that is an existing bug for all our reserved words. E.g. foo{sum="bar"}
      is a syntax error as well. This should be fixed separately.
      Julius Volz authored
  21. 22 Feb, 2015 1 commit
    • Add the histogram_quantile function. · 9e7c3e3b
      Since we are now getting really deep into floating point calculation,
      the tests had to take into account the precision loss. Since the rule
      tests are based on direct line matching in the output, implementing
      the "almost equal" semantics was pretty cumbersome, but here we are.
      beorn7 authored
  22. 21 Feb, 2015 2 commits
  23. 18 Feb, 2015 2 commits
    • Add tests for invalid uses of "offset". · 15b2b5aa
      Julius Volz authored
    • Implement offset operator. · 72d7b325
      This allows changing the time offset for individual instant and range
      vectors in a query.
      For example, this returns the value of `foo` 5 minutes in the past
      relative to the current query evaluation time:
          foo offset 5m
      Note that the `offset` modifier always needs to follow the selector
      immediately. I.e. the following would be correct:
          sum(foo offset 5m) // GOOD.
      While the following would be *incorrect*:
          sum(foo) offset 5m // INVALID.
      The same works for range vectors. This returns the 5-minutes-rate that
      `foo` had a week ago:
          rate(foo[5m] offset 1w)
      This change touches the following components:
      * Lexer/parser: additions to correctly parse the new `offset`/`OFFSET`
      * AST: vector and matrix nodes now have an additional `offset` field.
        This is used during their evaluation to adjust query and result times
      * Query analyzer: now works on separate sets of ranges and instants per
        offset. Isolating different offsets from each other completely in this
        way keeps the preloading code relatively simple.
      No storage engine changes were needed by this change.
      The rules tests have been changed to not probe the internal
      implementation details of the query analyzer anymore (how many instants
      and ranges have been preloaded). This would also become too cumbersome
      to test with the new model, and measuring the result of the query should
      be sufficient.
      This fixes
      This fixed
      Julius Volz authored
  24. 05 Feb, 2015 1 commit
  25. 04 Feb, 2015 1 commit
  26. 23 Jan, 2015 1 commit
    • Make 2nd arg to delta optional. Add a deriv() function. · a31730e8
      The 2nd isCounter argument to delta is ugly, make it optional as the first step
      of deprecating it. This will makes delta only ever applied to gauges.
      Add a deriv function to calculate the least squares
      slope of a gauge. This is more useful for prediction than delta,
      as it isn't as heavily influenced by outliers at the boundaries.
      Brian Brazil authored
  27. 21 Jan, 2015 1 commit
    • Clean up license issues. · 5859b74f
      - Move to the more common AUTHORS.
      - Added the required NOTICE file.
      - Changed "Prometheus Team" to "The Prometheus Authors".
      - Reverted the erroneous changes to the Apache License.
      Bjoern Rabenstein authored
  28. 25 Dec, 2014 1 commit
  29. 12 Dec, 2014 1 commit
    • Add regression tests for metrics mutations in AST. · 00a2a93a
      It turned out in the end, that only drop_common_metrics() produced any
      erroneous output in the old system. The second expression in the test
      ("sum(testmetric) keeping_extra") already worked in the old code, but
      why not keep it in...
      The way to test ranged evaluations is a bit clumsy so far, so I want to
      build a nicer test framework in the end, where all the test cases can be
      specified as text files which specify desired inputs, outputs, query
      step widths, etc.
      Change-Id: I821859789e69b8232bededf670a1b76e9e8c8ca4
      Julius Volz authored
  30. 25 Nov, 2014 1 commit