Releases: criteo/blackbox-prober
Releases · criteo/blackbox-prober
blackbox-prober-0.1.26
Clean the old 'aerospike-namespaces' consul metadata that is no longer supported
blackbox-prober-0.1.25
this release fix the issue regarding the 0.1.24 that failed to parse the new MetaKey added (aerospike-monitoring-)
blackbox-prober-0.1.24: Support new MetaData aerospike-monitoring-*
Following a consul limitation reached when using the metadata "aerospike-namespaces" (max for metadata value is 512 bytes), we needed to split into multiple metadata (1 per namespace) to activate the monitoring.
blackbox-prober-0.1.23: Allow configuring ExitFastOnExhaustedConnectionPool
The default behavior of the aerospike client is to loop forever trying to openconnections when a node is down. Now, if it tried to open too many connections it will stop right aways
blackbox-prober-0.1.22: Remove warmup of the aerospike client
It spawns a very high number of go routine. Instead minConnection is prefered.
blackbox-prober-0.1.21: Change the namespacing model for Aerospike
Previously we were starting one probe worker for each cluster. With one driver per worker. Now we spawn one worker per namespace per cluster. The main benefit is that namespace are handled independantly by the probe, it won't get stuck if one namespace is failing to start.
blackbox-prober-0.1.20: Avoid unwrapping Aerospike errors
Aerospike errors implement the std error interface so we can use them as is Unwrapping is bad because if the error didn't wrap another error in the first place it will return nil It was make the probe panic
blackbox-prober-0.1.19: Disable compression when building blackbox prober
It doesn't bring much value and it makes it a bit harder to build images
blackbox-prober-0.1.18: Fix handling of error key not found
Previous fix was incorrect
blackbox-prober-0.1.17: Fix "Key not found" not handled properly
With new version of aerospike we shouldn't compare the string of errors but the errors directly