This project is mirrored from https://github.com/prometheus/prometheus.git. Updated .
  1. 20 Aug, 2020 1 commit
  2. 01 Mar, 2020 1 commit
    • scrape/target_test.go: remove deprecated function BuildNameToCertificate() · d9cb4a14
      Related to https://github.com/golang/go/commit/eb93c684d40de4924fc0664d7d9e98a84d5a100b
      
      See,
      $ make lint
      >> running golangci-lint
      GO111MODULE=on go list -e -compiled -test=true -export=false -deps=true -find=false -tags= -- ./... > /dev/null
      GO111MODULE=on /home/mt/go/packages/bin/golangci-lint run  ./...
      scrape/target_test.go:260:2: SA1019: tlsConfig.BuildNameToCertificate is deprecated: NameToCertificate only allows associating a single certificate with a given name. Leave that field nil to let the library select the first compatible chain from Certificates.  (staticcheck)
      	tlsConfig.BuildNameToCertificate()
      	^
      scrape/target_test.go:357:2: SA1019: tlsConfig.BuildNameToCertificate is deprecated: NameToCertificate only allows associating a single certificate with a given name. Leave that field nil to let the library select the first compatible chain from Certificates.  (staticcheck)
      	tlsConfig.BuildNameToCertificate()
      	^
      make: *** [Makefile.common:181: common-lint] Error 1
      
      $ go version
      go version go1.14 linux/amd64
      Signed-off-by: 's avatarMario Trangoni <mjtrangoni@gmail.com>
      Mario Trangoni authored
  3. 14 Aug, 2019 1 commit
  4. 12 Mar, 2019 1 commit
    • scrape: Add global jitter for HA server (#5181) · 0d1a6935
      * scrape: Add global jitter for HA server
      
      Covers issue in https://github.com/prometheus/prometheus/pull/4926#issuecomment-449039848
      where the HA setup become a problem for targets unable to be scraped simultaneously.
      The new jitter per server relies on the hostname and external labels which necessarily to be uniq.
      
      As before, scrape offset will be calculated with regard the absolute time, so even
      restart/reload doesn't change scrape time per scrape target + prometheus instance.
      
      Use fqdn if possible, otherwise fall back to the hostname. It adds extra random seed
      to calculate server hash to be distinguish on machines with the same hostname, but
      different DC.
      Signed-off-by: 's avatarAleksei Semiglazov <xjewer@gmail.com>
      xjewer authored
  5. 21 Feb, 2019 1 commit
  6. 25 Apr, 2018 1 commit
  7. 01 Feb, 2018 1 commit
  8. 11 Jan, 2018 1 commit
  9. 29 Dec, 2017 1 commit
    • Refactor SD configuration to remove `config` dependency (#3629) · ec94df49
      * refactor: move targetGroup struct and CheckOverflow() to their own package
      
      * refactor: move auth and security related structs to a utility package, fix import error in utility package
      
      * refactor: Azure SD, remove SD struct from config
      
      * refactor: DNS SD, remove SD struct from config into dns package
      
      * refactor: ec2 SD, move SD struct from config into the ec2 package
      
      * refactor: file SD, move SD struct from config to file discovery package
      
      * refactor: gce, move SD struct from config to gce discovery package
      
      * refactor: move HTTPClientConfig and URL into util/config, fix import error in httputil
      
      * refactor: consul, move SD struct from config into consul discovery package
      
      * refactor: marathon, move SD struct from config into marathon discovery package
      
      * refactor: triton, move SD struct from config to triton discovery package, fix test
      
      * refactor: zookeeper, move SD structs from config to zookeeper discovery package
      
      * refactor: openstack, remove SD struct from config, move into openstack discovery package
      
      * refactor: kubernetes, move SD struct from config into kubernetes discovery package
      
      * refactor: notifier, use targetgroup package instead of config
      
      * refactor: tests for file, marathon, triton SD - use targetgroup package instead of config.TargetGroup
      
      * refactor: retrieval, use targetgroup package instead of config.TargetGroup
      
      * refactor: storage, use config util package
      
      * refactor: discovery manager, use targetgroup package instead of config.TargetGroup
      
      * refactor: use HTTPClient and TLS config from configUtil instead of config
      
      * refactor: tests, use targetgroup package instead of config.TargetGroup
      
      * refactor: fix tagetgroup.Group pointers that were removed by mistake
      
      * refactor: openstack, kubernetes: drop prefixes
      
      * refactor: remove import aliases forced due to vscode bug
      
      * refactor: move main SD struct out of config into discovery/config
      
      * refactor: rename configUtil to config_util
      
      * refactor: rename yamlUtil to yaml_config
      
      * refactor: kubernetes, remove prefixes
      
      * refactor: move the TargetGroup package to discovery/
      
      * refactor: fix order of imports
      Shubheksha Jalan authored
  10. 09 Oct, 2017 1 commit
  11. 06 Oct, 2017 1 commit
  12. 28 Aug, 2017 1 commit
  13. 20 Mar, 2017 1 commit
  14. 29 Dec, 2016 1 commit
  15. 23 Nov, 2016 1 commit
  16. 15 Sep, 2016 1 commit
  17. 07 Sep, 2016 1 commit
  18. 05 Sep, 2016 1 commit
  19. 26 May, 2016 2 commits
  20. 01 Mar, 2016 8 commits
  21. 15 Feb, 2016 4 commits
  22. 13 Feb, 2016 1 commit
  23. 08 Feb, 2016 1 commit
  24. 01 Feb, 2016 1 commit
    • Rework the way to communicate backpressure (AKA suspended ingestion) · ec08c9a3
      This gives up on the idea to communicate throuh the Append() call (by
      either not returning as it is now or returning an error as
      suggested/explored elsewhere). Here I have added a Throttled() call,
      which has the advantage that it can be called before a whole _batch_
      of Append()'s. Scrapes will happen completely or not at all. Same for
      rule group evaluations. That's a highly desired behavior (as discussed
      elsewhere). The code is even simpler now as the whole ingestion buffer
      could be removed.
      
      Logging of throttled mode has been streamlined and will create at most
      one message per minute.
      beorn7 authored
  25. 29 Jan, 2016 1 commit
    • Unify duration parsing · a7408bfb
      It's actually happening in several places (and for flags, we use the
      standard Go time.Duration...). This at least reduces all our
      home-grown parsing to one place (in model).
      beorn7 authored
  26. 28 Sep, 2015 1 commit
  27. 23 Sep, 2015 1 commit
  28. 22 Sep, 2015 1 commit
  29. 09 Sep, 2015 1 commit