1. 17 Aug, 2018 1 commit
  2. 10 Aug, 2018 1 commit
  3. 01 Aug, 2018 1 commit
  4. 25 Jul, 2018 1 commit
  5. 18 Jul, 2018 2 commits
  6. 15 Jul, 2018 1 commit
  7. 05 Jul, 2018 1 commit
  8. 09 May, 2018 1 commit
  9. 08 May, 2018 1 commit
  10. 30 Apr, 2018 1 commit
  11. 26 Apr, 2018 1 commit
  12. 25 Apr, 2018 1 commit
  13. 05 Apr, 2018 1 commit
    • Philippe Laflamme's avatar
      Use common HTTPClientConfig for marathon_sd configuration (#4009) · 2aba238f
      Philippe Laflamme authored
      This adds support for basic authentication which closes #3090
      The support for specifying the client timeout was removed as discussed in https://github.com/prometheus/common/pull/123. Marathon was the only sd mechanism doing this and configuring the timeout is done through `Context`.
      DC/OS uses a custom `Authorization` header for authenticating. This adds 2 new configuration properties to reflect this.
      Existing configuration files that use the bearer token will no longer work. More work is required to make this backwards compatible.
  14. 31 Mar, 2018 2 commits
  15. 23 Mar, 2018 1 commit
    • Corentin Chary's avatar
      consul: improve consul service discovery (#3814) · 60dafd42
      Corentin Chary authored
      * consul: improve consul service discovery
      Related to #3711
      - Add the ability to filter by tag and node-meta in an efficient way (`/catalog/services`
        allow filtering by node-meta, and returns a `map[string]string` or `service`->`tags`).
        Tags and nore-meta are also used in `/catalog/service` requests.
      - Do not require a call to the catalog if services are specified by name. This is important
        because on large cluster `/catalog/services` changes all the time.
      - Add `allow_stale` configuration option to do stale reads. Non-stale
        reads can be costly, even more when you are doing them to a remote
        datacenter with 10k+ targets over WAN (which is common for federation).
      - Add `refresh_interval` to minimize the strain on the catalog and on the
        service endpoint. This is needed because of that kind of behavior from
        consul: https://github.com/hashicorp/consul/issues/3712 and because a catalog
        on a large cluster would basically change *all* the time. No need to discover
        targets in 1sec if we scrape them every minute.
      - Added plenty of unit tests.
      - job_name: prometheus
        scrape_interval: 60s
          - targets: [""]
      - job_name: "observability-by-tag"
        scrape_interval: "60s"
        metrics_path: "/metrics"
          - server: consul.service.par.consul.prod.crto.in:8500
            tag: marathon-user-observability  # Used in After
            refresh_interval: 30s             # Used in After+delay
          - source_labels: [__meta_consul_tags]
            regex: ^(.*,)?marathon-user-observability(,.*)?$
            action: keep
      - job_name: "observability-by-name"
        scrape_interval: "60s"
        metrics_path: "/metrics"
          - server: consul.service.par.consul.prod.crto.in:8500
              - observability-cerebro
              - observability-portal-web
      - job_name: "fake-fake-fake"
        scrape_interval: "15s"
        metrics_path: "/metrics"
          - server: consul.service.par.consul.prod.crto.in:8500
              - fake-fake-fake
      Note: tested with ~1200 services, ~5000 nodes.
      | Resource | Empty | Before | After | After + delay |
      | -------- |:-----:|:------:|:-----:|:-------------:|
      |/service-discovery size|5K|85MiB|27k|27k|27k|
      |Network bandwidth|~10kbps|~2.8Mbps|~1.6Mbps|~10kbps|
      Filtering by tag using relabel_configs uses **100kiB and 23kiB/s per service per job** and quite a lot of CPU. Also sends and additional *1Mbps* of traffic to consul.
      Being a little bit smarter about this reduces the overhead quite a lot.
      Limiting the number of `/catalog/services` queries per second almost removes the overhead of service discovery.
      * consul: tweak `refresh_interval` behavior
      `refresh_interval` now does what is advertised in the documentation,
      there won't be more that one update per `refresh_interval`. It now
      defaults to 30s (which was also the current waitTime in the consul query).
      This also make sure we don't wait another 30s if we already waited 29s
      in the blocking call by substracting the number of elapsed seconds.
      Hopefully this will do what people expect it does and will be safer
      for existing consul infrastructures.
  16. 09 Mar, 2018 1 commit
  17. 24 Feb, 2018 1 commit
  18. 19 Feb, 2018 1 commit
    • Pedro Araújo's avatar
      Add OS type meta label to Azure SD (#3863) · 575f6659
      Pedro Araújo authored
      There is currently no way to differentiate Windows instances from Linux
      ones. This is needed when you have a mix of node_exporters /
      wmi_exporters for OS-level metrics and you want to have them in separate
      scrape jobs.
      This change allows you to do just that. Example:
        - job_name: 'node'
            - <azure_sd_config>
            - source_labels: [__meta_azure_machine_os_type]
              regex: Linux
              action: keep
      The way the vendor'd AzureSDK provides to get the OsType is a bit
      awkward - as far as I can tell, this information can only be gotten from
      the startup disk. Newer versions of the SDK appear to improve this a
      bit (by having OS information in the InstanceView), but the current way
      still works.
  19. 12 Feb, 2018 1 commit
  20. 24 Jan, 2018 1 commit
  21. 08 Jan, 2018 1 commit
  22. 23 Dec, 2017 1 commit
  23. 19 Dec, 2017 1 commit
    • James Turnbull's avatar
      Updated alert templating docs (#3596) · c3f92387
      James Turnbull authored
      The docs suggest that alert templating only works in the summary and
      description annotation fields. Some testing and a review of the code
      suggests this is no longer true and that you can template any
      annotation field.
  24. 14 Dec, 2017 6 commits
  25. 07 Dec, 2017 1 commit
  26. 06 Dec, 2017 1 commit
  27. 27 Nov, 2017 1 commit
  28. 24 Nov, 2017 1 commit
  29. 13 Nov, 2017 1 commit
    • Tobias Schmidt's avatar
      Add remote read filter option · 7098c564
      Tobias Schmidt authored
      For special remote read endpoints which have only data for specific
      queries, it is desired to limit the number of queries sent to the
      configured remote read endpoint to reduce latency and performance
  30. 02 Nov, 2017 1 commit
  31. 01 Nov, 2017 2 commits
  32. 31 Oct, 2017 1 commit