An active monitoring software to detect failures before your customers do.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by manugarg over 2 years ago
ssl_earliest_cert_expiry_sec
(#119 by @robpickerill)./probestatus
. If you suspect a problem because of this (high memory usage for example1), you can disable this UI by adding the following stanza to your config:
surfacer {
probestatus_surfacer {
disable: true
}
}
[1] -- There is a protection in place to avoid too much memory consumption if you run a lot of probes. By default, we keep only 3 days (configurable) worth of data, and only for up to 20 targets per probe. Also, the page served at /probestatus is cached with a TTL of 2s, to avoid DoSing Cloudprober functionality just by accessing /probestatus.
Full Changelog: https://github.com/cloudprober/cloudprober/compare/v0.11.7...v0.11.8
- Manu Garg (@manugarg)
Published by manugarg over 2 years ago
Cloudprober gets its own probe status UI \o/ (screenshot). Until now, we only exported metrics in the formats understood by other monitoring systems like Prometheus; there was no way to decipher the probe status using Cloudprober alone. This release changes that. It adds an option to show probe status in the Cloudprober UI itself. To enable this UI, add the following stanza to your config:
surfacer {
type: PROBESTATUS
}
By default, probe status UI will be available at the /probestatus
URL[1]. This, and other parameters like retention size, can be changed in the config. Note that all the data stays in memory, so if Cloudprober is restarted, data will be gone.
[1] Eventually probe status UI will be enabled by default, and will show up at the /status URL.
Full Changelog: https://github.com/cloudprober/cloudprober/compare/v0.11.6...v0.11.7
Published by manugarg over 2 years ago
HTTP Probe: Provide a way to improve coverage for load balanced targets. (#79)
keep_alive
mode, and increase connection diversity (final endpoint coverage) by configuring requests_per_probe
to a large number, say 100.
probe {
type: HTTP
targets {
host_names: "some-loadbalanced-target"
}
...
http_probe {
keep_alive: true
requests_per_probe: 100
}
}
Add a new probe type: TCP. For now, it simply tries to connect to the given host and port, and increments success and records latency if connection is successful. This is useful for probing non-HTTP, TCP endpoints. (#96)
External probe: Support aggregating labeled metrics. (#90)
aggregate_in_cloudprober
option was enabled. See redis_probe.go for an example probe outputting labels in the output, and cloudprober_aggregate.cfg for the corresponding config aggregating that output into distributions (histograms).Introduce the concept of negative tests. If a probe has the negative_test
option enabled, it reports success if the check fails, for example if you configure a ping probe with negative_test: true
, probe will succeed only if it doesn't receive any replies back. (#98).
Add the ability to add target IP to the labels (#82, #83, #84, #86, #87).
resolve_first
option.resolve_first
was not configured, we were not refreshing OAuth token in the outgoing HTTP requests. We've added tests to verify this behavior now. (#95)Full Changelog: https://github.com/cloudprober/cloudprober/compare/v0.11.4...v0.11.6
Published by manugarg over 2 years ago
This release was merged in to v0.11.6.
Full Changelog: https://github.com/cloudprober/cloudprober/compare/v0.11.4...v0.11.5
Published by manugarg over 2 years ago
This release cycle has been more about documentation updates, and build tooling improvements. Here are some of the functionality changes since the last release (v0.11.3):
timeout
and interval
in time.Duration parseable string format: 2ms, 4s, 5m, etc (https://github.com/cloudprober/cloudprober/pull/29).Complete list of commits since the last release: https://github.com/cloudprober/cloudprober/compare/v0.11.3...v0.11.4
Published by manugarg almost 3 years ago
More accurate "ping" latency measurements
Cloudprober now uses SO_TIMESTAMP socket option (on non-windows OS) to make latency measurements much more accurate. (#546)
Better isolation in HTTP probes for multiple targets
HTTP probes for multiple targets execute in independent goroutines now. This allows for better isolation between probes.
Add HTTP header validator for HTTP probe
You can now add a header validator to an HTTP probe (example).
#537 Datagram socket ping (unprivileged ping) over IPv4 is broken for MacOS.
#554 Error initializing cloudprober on GKE.
#584 Goroutine leaking bug in external probe.
Complete list of commits since the last release: https://github.com/google/cloudprober/compare/v0.11.1...v0.11.2
Bugs/PR in this release: Milestone v0.11.2.
Published by manugarg almost 3 years ago
Metrics export enhancements
Labeling
Targets Discovery
Bug Fixes
Complete list of commits since the last release: https://github.com/cloudprober/cloudprober/compare/v0.11.2...v0.11.3
Bugs/PR in this release: Milestone v0.11.3.