mysqld_exporter, A Real MariaDB Seen Down Then Up

mysqld_exporter on EL 10 from the upstream release (sha256-verified), as a hardened systemd service on loopback; the live test brings up MariaDB as a fixture, reads mysql_up 0 before the exporter's user exists, creates it with the monitoring grants, and reads mysql_up 1 with the status counters. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticDatabasesv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

ClickHouse, An Analytics Database Proven By A MergeTree Round Trip Dragonfly, A Redis-Compatible Store Proven Over RESP InfluxDB 3 Core, Proven By A Write And An SQL Query MariaDB That Ran Its Own Secure Installation Meilisearch, A Search Engine Proven By An Indexed Search PocketBase On Loopback, A Collection Round-Tripped PostgreSQL Server (EL)Qdrant, A Vector Search Engine Proven By A Nearest Neighbour

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_mysqld_exporter" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-mysqld-exporter/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.