Ross ROSS = Recommend OSS · open-source software intelligence for agents

google/cloudprober

[Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do. observed · 2026-08-28

github.com/google/cloudprober · homepage · Go · Apache-2.0 (permissive) · archived observed · 2026-08-28

Health v2 · maintenance only

10/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100

Flags: archived

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 3380
  • days_rel: n/a
  • days_push: 1770
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1395 stars · 147 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Cloudprober is an open-source active (synthetic) monitoring tool built at Google that runs continuous probes—HTTP, gRPC, DNS, PING, TCP, UDP, browser, and script-based—against your services to detect failures before users notice. It compiles to a single Go binary, supports dynamic target discovery from Kubernetes and GCP, and exports metrics to Prometheus, Datadog, CloudWatch, Stackdriver, and other backends with optional alerting.

Use cases

  • run blackbox synthetic monitoring for websites and APIs
  • probe HTTP endpoints and alert on failures before customers notice
  • monitor DNS resolution, TCP reachability, and packet loss
  • auto-discover and probe Kubernetes or GCP targets
  • export probe latency and success metrics to Prometheus or Grafana
  • replace Prometheus Blackbox Exporter with a more extensible prober
  • run lightweight uptime checks from a Raspberry Pi or homelab

When to choose

  • you need outside-in synthetic monitoring that measures what users actually experience
  • you want a single self-contained binary with no agents to deploy
  • you need built-in probes across many protocols (HTTP, gRPC, DNS, PING, TCP, UDP, browser) in one config
  • your targets change dynamically and you want auto-discovery from Kubernetes or GCP
  • you need to export metrics to multiple monitoring systems simultaneously

When to avoid

  • you only need passive monitoring of logs and application-internal metrics
  • you want a full metrics scraping and storage system rather than a prober
  • you require a GUI-driven monitoring product rather than config-file-driven probing
  • you need Windows-native installation via the install script (script supports Linux/macOS only, though binaries exist)

Facets

service · maturity stable

monitoring alerting http-client monitoring networking cloud-computing self-hosted windows go cli self-hosted synthetic-monitoring blackbox-probing active-monitoring prometheus single-binary sre observability kubernetes-targets grpc-probe dns-probe devops linux macos docker kubernetes

10 sources

Member repositories

RepositoryRoleHealth v2
google/cloudprobermain10

For agents

markdown · JSON · MCP: product_card(name="google/cloudprober")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem