Releases: criteo/blackbox-prober
Releases · criteo/blackbox-prober
blackbox-prober-0.1.39
What's Changed
Full Changelog: blackbox-prober-0.1.38...blackbox-prober-0.1.39
blackbox-prober-0.1.38
What's Changed
Full Changelog: blackbox-prober-0.1.37...blackbox-prober-0.1.38
blackbox-prober-0.1.37
What's Changed
Full Changelog: blackbox-prober-0.1.36...blackbox-prober-0.1.37
blackbox-prober-0.1.36
What's Changed
- Milvus: Authorize connection without auth by @damsallem in #52
- Fix "aeropsike" typo by @eappere in #50
Full Changelog: blackbox-prober-0.1.35...blackbox-prober-0.1.36
blackbox-prober-0.1.35
What's Changed
- Add probe to Milvus by @damsallem in #51
Full Changelog: blackbox-prober-0.1.34...blackbox-prober-0.1.35
blackbox-prober-0.1.34
What's Changed
Full Changelog: blackbox-prober-0.1.33...blackbox-prober-0.1.34
blackbox-prober-0.1.33
What's Changed
Full Changelog: blackbox-prober-0.1.32...blackbox-prober-0.1.33
blackbox-prober-0.1.32
What's Changed
Full Changelog: blackbox-prober-0.1.31...blackbox-prober-0.1.32
blackbox-prober-0.1.31
blackbox-prober-0.1.30: Add configurable total timeout parameter
- Since we bumped from v5 to v7 of the Aerospike
client the default timeout went from 0 (no timeout)
to 1 second.
- This change adds a configuration option to specify
this value (total_timeout, e.g. "30s" in the yaml
config). The default value is 30s
- We also use explicitly (for readability) 2 retries
for the durability checks (read and write policies):
this is the default for read (aka. base) policy,
while the default for write policiy is 0