1. 18 2月, 2020 2 次提交
  2. 12 2月, 2020 1 次提交
  3. 30 1月, 2020 1 次提交
  4. 29 1月, 2020 2 次提交
  5. 08 1月, 2020 1 次提交
  6. 11 12月, 2019 2 次提交
  7. 10 12月, 2019 3 次提交
  8. 05 12月, 2019 2 次提交
    • G
      api: tests for /target/metadata API endpoint · 428089f8
      gotjosh 提交于
      This commit introduces several test cases for the current /targets/metadata API endpoint.
      
      To achieve so, we use a mock of the metadataStore and inject it to the targets under test.
      
      Currently, three success cases are covered: with a metric name, with a target matcher, and with both. As for the failure scenario, the one where we couldn't match against a particular metric is covered.
      Signed-off-by: Ngotjosh <josue@grafana.com>
      428089f8
    • G
      Allow targets to be injected as arguments when creating a testTargetRetriever · 4bf9c6bb
      gotjosh 提交于
      Previously, the struct `testTargetRetriever` had hardcoded active and dropped targets. This made it difficult to change the target information depending on the test case.
      
      This change introduces a way to define them as arguments and pass it to a constructor for building. It lays a foundation for dynamically defining targets with various set of arguments to test different scenarios.
      Signed-off-by: Ngotjosh <josue@grafana.com>
      4bf9c6bb
  9. 19 11月, 2019 1 次提交
  10. 12 11月, 2019 2 次提交
  11. 18 9月, 2019 1 次提交
  12. 29 8月, 2019 1 次提交
  13. 20 8月, 2019 1 次提交
  14. 13 8月, 2019 1 次提交
  15. 09 8月, 2019 1 次提交
  16. 30 7月, 2019 1 次提交
  17. 08 7月, 2019 1 次提交
  18. 03 5月, 2019 1 次提交
  19. 17 4月, 2019 1 次提交
  20. 03 4月, 2019 1 次提交
  21. 26 3月, 2019 1 次提交
  22. 19 3月, 2019 1 次提交
  23. 12 2月, 2019 1 次提交
    • C
      Tail the TSDB WAL for remote_write · 6f69e313
      Callum Styan 提交于
      This change switches the remote_write API to use the TSDB WAL.  This should reduce memory usage and prevent sample loss when the remote end point is down.
      
      We use the new LiveReader from TSDB to tail WAL segments.  Logic for finding the tracking segment is included in this PR.  The WAL is tailed once for each remote_write endpoint specified. Reading from the segment is based on a ticker rather than relying on fsnotify write events, which were found to be complicated and unreliable in early prototypes.
      
      Enqueuing a sample for sending via remote_write can now block, to provide back pressure.  Queues are still required to acheive parallelism and batching.  We have updated the queue config based on new defaults for queue capacity and pending samples values - much smaller values are now possible.  The remote_write resharding code has been updated to prevent deadlocks, and extra tests have been added for these cases.
      
      As part of this change, we attempt to guarantee that samples are not lost; however this initial version doesn't guarantee this across Prometheus restarts or non-retryable errors from the remote end (eg 400s).
      
      This changes also includes the following optimisations:
      - only marshal the proto request once, not once per retry
      - maintain a single copy of the labels for given series to reduce GC pressure
      
      Other minor tweaks:
      - only reshard if we've also successfully sent recently
      - add pending samples, latest sent timestamp, WAL events processed metrics
      
      Co-authored-by: Chris Marchbanks <csmarchbanks.com> (initial prototype)
      Co-authored-by: Tom Wilkie <tom.wilkie@gmail.com> (sharding changes)
      Signed-off-by: NCallum Styan <callumstyan@gmail.com>
      6f69e313
  24. 17 1月, 2019 2 次提交
  25. 16 1月, 2019 1 次提交
  26. 02 1月, 2019 1 次提交
  27. 03 12月, 2018 1 次提交
  28. 30 11月, 2018 1 次提交
  29. 23 11月, 2018 1 次提交
  30. 19 11月, 2018 1 次提交
  31. 15 11月, 2018 1 次提交
  32. 26 10月, 2018 1 次提交