rsyslog, A Receiver For Other Hosts' Logs, Over TLS

rsyslog from AppStream as a remote receiver on EL 10: a plaintext port, RFC 5425's TLS port, and one file per sending host. The live test sends a message to each and finds both in the right file at 0640, pushes plaintext at the TLS port and finds nothing written, and checks that no remote message reached this host's own log. 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-agnosticObservabilityv1.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.

Alertmanager On Loopback, Gossip Off Alloy On Loopback, Reporting Off, Validated Blackbox Exporter, Probed With A Control Grafana With Its Own Secret Key Grafana, Datasources Provisioned And A Dashboard Proven Jaeger v2 With Badger On Loopback, A Span Written And Read Back Logs That Leave Over TLS, With The Collector Checked Loki Single Binary, Retention On, Reporting Off

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_rsyslog_remote" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-rsyslog-remote/any"
  version = "1.0.0"
}

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