# Installer cloudprober avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de cloudprober pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:cloudprober
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install cloudprober
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#cloudprober
```

  Preuve: nixpkgs package indexes: pkgs/by-name/cl/cloudprober/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Faits du paquet

- **Clé du paquet:** brew:cloudprober
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.14.4
- **Résumé source:** Active monitoring software to detect failures before your customers do
- **Page d'accueil:** <https://cloudprober.org>
- **Dépôt:** <https://github.com/cloudprober/cloudprober>
- **Dernière mise à jour:** 2026-07-27T18:04:30Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- cloudprober (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.14.4
## Historique du projet et usages

Cloudprober is an open-source active monitoring and probing system originally built at Google. It runs scheduled probes against services and infrastructure, exports metrics, and helps operators detect user-visible failures before customers report them.

### Historique du projet

Google's Open Source Blog described Cloudprober in March 2018 as black-box monitoring software that Google had open sourced the previous year. The project focused on probing systems and services from the outside and producing metrics from those probe results rather than relying only on internal application telemetry.

Cloudprober's own about page says its original goal was discovering and alerting on Cloud Networking availability and performance problems, but that it was developed as a generic prober for many kinds of systems and services. The current project site carries that lineage forward with the tagline that it is open-source active monitoring built at Google and able to run from small devices to large fleets.

### Historique d'adoption

Cloudprober's adoption is strongest among operators who want self-hosted active or synthetic monitoring with Prometheus-style metrics and low deployment assumptions. Official materials mention production use and the Cloudprober Helm chart documents Kubernetes installation through GitHub Container Registry, while Homebrew and Nix packaging make the standalone binary convenient on developer and operator machines.

### Modes d'utilisation

Users configure Cloudprober to run HTTP, DNS, ping, TCP, UDP, browser, external, and other probes on a schedule, then consume the emitted metrics and alerts in their monitoring stack. The getting-started docs also note that running cloudprober with no arguments on Linux exposes a built-in sys_metrics probe at a local metrics endpoint.

### Pourquoi les passionnés de paquets s'y intéressent

Cloudprober is package-nerd interesting because it is infrastructure software that stays useful as a single CLI/server binary: one package can serve laptop experiments, Raspberry Pi checks, Kubernetes deployments, and fleet monitoring. Its packaging also bridges old-school daemon-style monitoring and modern cloud-native distribution, with Homebrew/Nix formulae and an official Helm chart.

### Chronologie

- 2017: Google open sourced Cloudprober, according to Google's 2018 announcement.
- 2018: Google Open Source Blog introduced Cloudprober publicly as black-box monitoring software.
- 2023: Cloudprober docs described the project's origins in Cloud Networking availability and performance monitoring.
- 2026: Cloudprober 0.14.x releases added web UI logging and run-once support across probe types.

### Related projects

- Cloudprober overlaps with black-box and synthetic monitoring tools, especially Prometheus Blackbox Exporter-style checks, hosted uptime services, and Kubernetes monitoring stacks. Its official Helm chart is the closest related packaging project, while its metrics output is commonly consumed by broader observability systems.

### Sources

- <https://cloudprober.org/>
- <https://opensource.googleblog.com/2018/03/cloudprober-open-source-black-box.html>
- <https://cloudprober.org/docs/about/>
- <https://cloudprober.org/docs/overview/probe/>
- <https://cloudprober.org/docs/overview/getting-started/>
- <https://github.com/cloudprober/helm-charts>
- <https://github.com/cloudprober/cloudprober/releases>


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal

## Autres enregistrements de gestionnaires de paquets

- Nix - cloudprober: normalized package name match | nixpkgs package indexes: pkgs/by-name/cl/cloudprober/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/cloudprober.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cloudprober.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph