ICMP Latency For Prometheus With One Capability
smokeping_prober from the upstream release, pinging the targets you list and exporting latency, TTL and loss on loopback. The unit grants CAP_NET_RAW as an ambient capability and narrows the bounding set to it, so the service account holds that and nothing else. The live test waits for answered pings with loopback's TTL. Original role, live-tested on Rocky Linux 10.
Verification
Live-testedReally deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.
Conformance
- Static validation (yamllint · ansible-lint)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-10-02 · podman 4.9.3 · ansible 2.21.4 · how we verify
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/ansible-smokeping-prober?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [ICMP Latency For Prometheus With One Capability](https://www.iac-bazaar.com/catalog/ansible-smokeping-prober?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# ICMP Latency For Prometheus With One Capability: https://www.iac-bazaar.com/catalog/ansible-smokeping-prober (download from your IaC Bazaar account)
```Preview:
Documentation
smokeping-prober
smokeping_prober from the upstream release (sha256-verified), as a hardened system service with its metrics on loopback, pinging the targets you list and exporting latency histograms, TTLs and loss for Prometheus. Original role for EL 10, live-tested with podman on Rocky Linux 10.
No package, so the checksum is the whole story. EL 10 carries no
smokeping_prober; SuperQ ships a release with a checksum file beside it. The
role downloads both and has Ansible's get_url refuse the asset unless its
SHA-256 is the one in the vendor's file, then installs the binaries as
root's in /usr/local/bin, pinned by smokeping_prober_version.
A service account, a hardened unit, a loopback listener. smokeping
is a system user with no shell that owns the data directory and nothing
else; the unit runs with NoNewPrivileges, PrivateTmp, ProtectHome and
ProtectSystem=strict. The listener is 127.0.0.1:9374 by default,
for a proxy that authenticates or a client on the same host; the live test
reads the listening sockets and expects loopback only.
One capability, and only that one. A raw ICMP socket needs
CAP_NET_RAW. The unit grants it as an ambient capability to the unprivileged
service account and narrows the bounding set to it, so the process holds that
capability and no other. Measured in the lane before the role was written:
without it, privileged mode is refused ("operation not permitted"); the
unprivileged ICMP mode is refused too wherever net.ipv4.ping_group_range
excludes the service's group (podman's containers default to 0 0). EL 10
hosts get 0 2147483647 from systemd, where unprivileged mode would work -
the role uses the one-capability mode because it works whatever that sysctl
says. The live test therefore runs with --cap-add=NET_RAW, which podman's
default set does not include.
It tells reachable from unreachable. With the capability, the prober
answered 5 of 7 pings to 127.0.0.1 with TTL 64 and 0 of 7 to 192.0.2.1
(TEST-NET-1) in the probe that preceded this role; the live test asserts the
loopback half against the role's own default target: at least three answered
pings, TTL 64, no receive errors. Note the switch is --[no-]privileged:
written as --privileged=false, the word false becomes a host to ping.
License
Commercial - IaC Bazaar EULA. (c) IaC Bazaar.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Variables
- Test
Related modules
ansible-alertmanager
Prometheus Alertmanager from the upstream release (sha256-verified) as a hardened system service on loopback, its cluster gossip listener switched off and its configuration checked by amtool before it lands. The live test posts an alert through the API and reads it back active, held by the default receiver, and expects no 9094 listener at all. Original role, live-tested on Rocky Linux 10.
ansible-alloy
Grafana Alloy from the upstream release (sha256-verified) as a hardened system service on loopback with --disable-reporting, a self-scrape pipeline that proves the collector runs, and its configuration checked by alloy validate before it lands. The live test reads Alloy's own metrics and asks the component API for the scrape component's health. Original role, live-tested on Rocky Linux 10.
ansible-blackbox-exporter
Prometheus Blackbox exporter from the upstream release (sha256-verified) as a hardened system service on loopback with HTTP and TCP modules, checked by --config.check before the file lands. The live test has it probe itself over HTTP and TCP (probe_success 1) and a port with nothing behind it (probe_success 0): it measures, not only answers. Original role, live-tested on Rocky Linux 10.
ansible-grafana-server
Grafana on loopback with a secret key of yours: every install that never set one shares the package's, which encrypts the data-source credentials in its database. Secure cookies and HSTS for the TLS proxy in front; public snapshots, plugin update checks, feedback links and Gravatar switched off. Settings verified through the API, not the file. Original role, live-tested on Rocky Linux 10.
ansible-grafana
Grafana (sha256-verified) on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test reads back the datasource this role provisioned, creates a dashboard and finds it by search, sees anonymous and wrong-password requests refused, and reads the build metric naming the version installed. Original role, live-tested on Rocky Linux 10.
ansible-jaeger
Jaeger v2, the tracing backend built on the OpenTelemetry Collector, from the upstream release (sha256-verified against the right checksum file) as a hardened system service on loopback with badger storage and the query API on loopback. The live test pushes a span over OTLP and reads the trace back by id with its name and service. Original role, live-tested on Rocky Linux 10.