cloudprober.org | Start Monitoring Now
Cloudprober: Reliable System Monitoring, Simplified!
Cloudprober supercharges your monitoring with active probes (a.k.a. synthetic monitoring) to ensure your systems—homelabs, microservices, APIs, websites, or cloud-to-on-prem connections—run smoothly. See this post for why probers provide one of the most reliable monitoring signals.
Trusted by Leading Organizations
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Why Cloudprober?
-
Versatile Probes: Built-in HTTP, PING, TCP, DNS, gRPC, and UDP probes, plus custom checks via external probes.
-
Auto-Discover Targets: Effortlessly monitor Kubernetes, GCP, or file-based resources without constant redeployment.
-
Integrate with Existing Systems: Out-of-the-box integration with Prometheus, Grafana, DataDog, AWS CloudWatch, PostgreSQL, and Google Cloud Monitoring.
-
Easy Alerts: Stay informed via email, Slack, PagerDuty, OpsGenie, or any other HTTP based system.
-
Lightweight & Scalable: Written in Go, compiles to a single binary, and runs efficiently as a standalone app or Docker container.
-
Custom Metrics: Flexible latency histograms and configurable labels for precise insights.
-
Extensible: Easily add new probe types, targets, or monitoring systems.
Learn More
-
If you're familiar with Prometheus Blackbox Exporter, see how Cloudprober stacks against it: Prometheus Blackbox Exporter vs Cloudprober.
-
If you're not very familiar with the blackbox/synthetic monitoring paradigm, take a look at why you need probers.
-
Cloudprober's origin story.
Get Started
Jump in with our Getting Started guide and start monitoring your systems in minutes.
Join the Community
Join our Slack, or discuss on Github. Help shape Cloudprober's future by commenting here.
NOTE: Cloudprober's active development moved from
google/cloudprober to
cloudprober/cloudprober in
Nov, 2021. We lost a bunch of Github stars (1400) in the process. See
story of cloudprober
to learn more about the history of Cloudprober.
1 maintainer
Metadata
1 maintainer
Release files for cloudprober-serverutils 0.14.1.post36
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cloudprober_serverutils-0.14.1.post36.tar.gz | 6.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloudprober_serverutils-0.14.1.post36-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / cloudprober_serverutils-0.14.1.post36.tar.gz
| Download URL | cloudprober_serverutils-0.14.1.post36.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cce000f7277c2eed165e2fddf9ac59348f1d64b886b565824cd4cd9f24e95e1
|
|
BLAKE2b-256 checksum How to use checksums |
88ec911376b42d14648441957998b99be8e3632df3fde68e5abf0376af75a616
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2026.
Transparency logRelease files / cloudprober_serverutils-0.14.1.post36-py3-none-any.whl
| Download URL | cloudprober_serverutils-0.14.1.post36-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca742f7cbdb31562d09118c8c169f92ba9e94a4b23954c5fa9f51ab24e8dd7c0
|
|
BLAKE2b-256 checksum How to use checksums |
94e83238efacd10dee3fab5460de6ba2c791bd7eae8c7d66e3632e00b49be234
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2026.
Transparency log
