github.com/google/cloudprober@v0.11.3/docs/content/_readme.md (about) 1  2 [](https://ci.appveyor.com/project/manugarg/cloudprober-wwcpu) 3 [](https://hub.docker.com/v2/repositories/cloudprober/cloudprober/) 4 5 Cloudprober is a monitoring software that makes it super-easy to monitor 6 availability and performance of various components of your system. Cloudprober 7 employs the "active" monitoring model. It runs probes against (or on) your 8 components to verify that they are working as expected. For example, it can run 9 a probe to verify that your frontends can reach your backends. Similarly it can 10 run a probe to verify that your in-Cloud VMs can actually reach your on-premise 11 systems. This kind of monitoring makes it possible to monitor your systems' 12 interfaces regardless of the implementation and helps you quickly pin down 13 what's broken in your system. 14 15  16 17 ## Features 18 19 * Automated target discovery for Cloud targets. __GCE__ and __Kubernetes__ 20 are supported out-of-the-box, other Cloud providers can be added easily. 21 * Integration with open source monitoring stack of 22 [Prometheus](http://prometheus.io) and [Grafana](http://grafana.com). 23 Cloudprober exports probe results as counter based metrics that work well 24 with Prometheus and Grafana. 25 * Integration with [StackDriver](https://cloud.google.com/stackdriver/). If 26 configured, Cloudprober exports probe results to StackDriver as custom 27 metrics. 28 * Fast and efficient built-in implementations for the most common types of 29 checks: PING (ICMP), HTTP, UDP, DNS. Especially PING and UDP probes are 30 implemented in such a way that thousands of hosts can be probed with 31 minimal resources. 32 * Arbitrary, complex probes can be run through the external probe type. For 33 example, you could write a simple script to insert and delete a row in your 34 database, and execute this script through the 'EXTERNAL' probe type. 35 * Standard metrics - _total_, _success_, _latency_. Latency can be configured 36 to be a distribution (histogram) metric, allowing calculations of 37 percentiles. 38 * Strong focus on ease of deployment. Cloudprober is written entirely in Go 39 and compiles into a static binary. It can be easily deployed, either as a 40 standalone binary or through docker containers. Thanks to the automated, 41 continuous, target discovery, there is usually no need to re-deploy or 42 re-configure cloudprober in response to the most of the changes. 43 * Low footprint. Cloudprober docker image is small, containing just the 44 statically compiled binary and it takes very little CPU and RAM to run even 45 a large number of probes. 46 * Extensible architecture. Cloudprober can be easily extended along most of 47 the dimensions. Adding support for other Cloud targets, monitoring systems 48 and even a new probe type, is straight-forward and fairly easy. 49 50 ## Getting Started 51 52 Visit [Getting Started](http://cloudprober.org/getting-started) page to get 53 started with Cloudprober. 54 55 ## Feedback 56 57 We'd love to hear your feedback. If you're using Cloudprober, would you please 58 mind sharing how you use it by adding a comment [here]( 59 https://github.com/google/cloudprober/issues/123). It will be a great help in 60 planning Cloudprober's future progression. 61 62 Join [Cloudprober Slack](https://join.slack.com/t/cloudprober/shared_invite/enQtNjA1OTkyOTk3ODc3LWQzZDM2ZWUyNTI0M2E4NmM4NTIyMjM5M2E0MDdjMmU1NGQ3NWNiMjU4NTViMWMyMjg0M2QwMDhkZGZjZmFlNGE) or [Github discussions]( 63 https://github.com/google/cloudprober/discussions) for questions and discussion 64 about Cloudprober.