Cloudprober provides a reliable and easy-to-use solution to monitor the availability and performance of your systems. Employing an “active” monitoring approach, Cloudprober executes probes on or against these systems to verify their proper functioning.
For example, you could use Cloudprober to run a probe to verify that your users can access your website and your APIs, your microservices can talk to each other, your kubernetes clusters can schedule pods, your CI/CD pipelines are functioning as expected, or VPN connectivity with your partners is working as expected, and much more.
This kind of monitoring makes it possible to monitor your systems’ interfaces regardless of the implementation, and helps you quickly pin down what’s broken in your systems.
Out of the box, config based, integration with many popular monitoring systems:
Multiple options for checks:
Automated targets discovery to make Cloud deployments as painless as possible:
- Written entirely in Go, and compiles into a static binary.
- Deploy as a standalone binary, or through docker containers.
- Continuous, automated target discovery, to ensure that most infrastructure changes don’t require re-deployment.
- Low footprint. Cloudprober takes advantage of the Go’s concurrency paradigms, and makes most of the available processing power.
- Configurable metrics labels, based on the resource labels.
- Latency histograms for percentile calculations.
- Extensible architecture. Cloudprober can be easily extended along most of the dimensions. Adding support for other Cloud targets, monitoring systems and even a new probe type, is straight-forward and fairly easy.
Visit Getting Started page to get started with Cloudprober.
We’d love to hear your feedback. If you’re using Cloudprober, would you please mind sharing how you use it by adding a comment here. It will be a great help in planning Cloudprober’s future progression.