Mimir Monolithic On Loopback, A Metric Written And Read Back
Grafana Mimir from the upstream release binary (sha256-verified) in monolithic mode as a hardened system service on loopback with filesystem storage, every ring member on loopback, usage reporting off. The live test pushes a gauge over OTLP, queries it back through the Prometheus API with its labels and sees an unknown metric answered empty. 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-09-20 · 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-mimir?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [Mimir Monolithic On Loopback, A Metric Written And Read Back](https://www.iac-bazaar.com/catalog/ansible-mimir?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# Mimir Monolithic On Loopback, A Metric Written And Read Back: https://www.iac-bazaar.com/catalog/ansible-mimir (download from your IaC Bazaar account)
```Preview:
Documentation
mimir
Grafana Mimir from the upstream release binary (sha256-verified), in monolithic mode as a hardened system service on loopback with filesystem storage, for a Prometheus remote-write or OTLP source on the same host or behind a proxy. 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
mimir; Grafana ships a release with a checksum file beside it. The
role downloads both and has Ansible's get_url refuse the binary unless its
SHA-256 is the one in the vendor's file, then installs it as
root's in /usr/local/bin, pinned by mimir_version.
A service account, a hardened unit, a loopback listener. mimir
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:9009 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.
Every ring member says loopback. Mimir's components find each other
through rings and advertise the address of the first interface they
find, which on a host is not loopback: the query frontend then waits for
queriers at an address nothing listens on and every query hangs. The
role gives each ring (instance_addr), the query frontend (address) and
memberlist (bind_addr, advertise_addr) 127.0.0.1 explicitly, and the
live test reads the listening sockets and expects 9009, 9095 and 7946 on
loopback only. Filesystem blocks, ruler and alertmanager stores must be
distinct directories (Mimir refuses overlapping ones at start), and the
activity tracker's file is pointed into the data directory, since
ProtectSystem=strict makes the working directory read-only.
Proven by a metric. The live test pushes one gauge sample through the
OTLP/HTTP receiver, queries it back through the Prometheus API with its
resource and point labels, sees a metric nobody wrote answered with an
empty result, and reads the pinned version from the build information.
Filesystem storage is what Grafana calls development-grade; an object
store is mimir_extra_config away, and usage reporting is off.
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-victoria-logs
VictoriaLogs from the upstream release as a hardened service on loopback. Its JSON-lines endpoint answers 200 and stores nothing when the content type is wrong, so the README names the one it needs. The live test ingests two lines, gets the right one back from LogsQL, and sees an unwritten stream come back empty and bad LogsQL refused. Original role, live-tested on Rocky Linux 10.
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-cockpit
Cockpit from BaseOS bound to loopback, with logins limited to an admin group through PAM and root refused outright. The live test sees an administrator log in while an ordinary account, a wrong password and root, placed in the admin group to isolate its own rule, are refused, and reads the login banner. Original role, live-tested on Rocky Linux 10.
ansible-fluent-bit
fluent-bit from EPEL, following a log-file glob it re-reads every few seconds and shipping over the Forward protocol, with retries unlimited instead of the default single retry. Its config is checked with --dry-run before it lands. The live test writes a line to a new file and watches it arrive at an aggregator it started. Original role, live-tested on Rocky Linux 10.