1. 04 11月, 2017 2 次提交
  2. 03 11月, 2017 1 次提交
  3. 27 10月, 2017 5 次提交
  4. 26 10月, 2017 3 次提交
  5. 23 10月, 2017 1 次提交
    • B
      Remote read endpoint should handle matchers for external labels. (#3325) · 3a7c51ab
      Brian Brazil 提交于
      If the other Prometheus has an external label that matches that of
      the Prometheus being read from, then we need to remove that matcher
      from the request as it's not actually stored in the database - it's
      only added for alerts, federation and on the output of the remote read
      endpoint.
      Instead we check for that label being empty, in case there is a time
      series with a different label value for that external label.
      3a7c51ab
  6. 19 10月, 2017 2 次提交
  7. 16 10月, 2017 1 次提交
  8. 07 10月, 2017 3 次提交
  9. 06 10月, 2017 6 次提交
  10. 05 10月, 2017 2 次提交
  11. 04 10月, 2017 2 次提交
    • P
      cmd/prometheus: don't allow quotes at beginning or end of url · 08af129b
      Paul Gier 提交于
      This prevents accidental copy/paste error where a the web.external-url
      or alertmanager.url params could have an extra set of quotes.
      See also: https://github.com/prometheus/prometheus/issues/1229
      08af129b
    • P
      cmd/prometheus: remove govalidator for url validation · f79b55d0
      Paul Gier 提交于
      The usage of govalidator is redundant with the call to url.Parse for
      url validation. Removing it has the following benefits:
      
       - The explicit error message is displayed instead of just a generic
         valid/invalid message
       - Slightly smaller code with one fewer external dependency
       - Speed improvement by removing duplicate call to url.Parse (inside
         govalidator.IsURL()
       - Resolves issue #2717
      
      The only potential drawback of removing govalidator is that certain
      URLs will be considered valid which were previously invalid. For example:
      
       - URLs with hostnames that start and/or end with an underscore (http://_example.com_)
       - URLs with hostnames that contain some special characters (http://foo&*bar.org)
      
      These are valid URIs according to RFC 3986 and valid domain names per RFC 2181,
      however they are not valid hostnames per RFC 952.
      f79b55d0
  12. 29 9月, 2017 1 次提交
  13. 28 9月, 2017 2 次提交
  14. 26 9月, 2017 7 次提交
  15. 22 9月, 2017 2 次提交