Files
computer-playbook/roles/sys-svc-journalctl/README.md
kevinveenbirkenbachandClaude Opus 5 c55f508e05 feat(readme): draw mandatory and disabled service relations
The cosmos generator linked a consumer to its provider only through an
'<role>' in group_names reference or an explicit provides: name. A hard
dependency has neither -- pinning the provider on unconditionally is
exactly what removes the Jinja reference the generator was reading -- so
web-svc-asset's bond to web-svc-file vanished from the diagram the moment
it became binding. Match a service key against the provider's own primary
key from the registry, in both directions.

Services the role turns off drew a solid 1:1 edge, claiming a mandatory
relationship for something that carries nothing at deploy time. They now
render as a red 0..0 edge; edge merging gained a real precedence so a
provider consumed through two keys stays live when only one is off.

Named colour, not hex: a '#' opens an entity code in the mermaid lexer and
turns the whole diagram into a parse error on GitHub.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-17 18:02:31 +02:00

1.9 KiB

Journalctl

This Ansible role manages the configuration of systemd-journald on target hosts.

Description

  • Copies a customized journald.conf to /etc/systemd/journald.conf
  • Ensures log retention for one week
  • Restarts the systemd-journald service when configuration changes
  • Supports live log streaming via journalctl -f

Overview

  1. Template deployment
    The role places your journald.conf.j2 template into /etc/systemd/journald.conf.
  2. Service handler
    On change, it notifies a handler to restart systemd-journald.
  3. Monitoring
    You can follow logs in real time with journalctl -f.

Cosmos

The diagram places Journalctl in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph role [sys-svc-journalctl 💻]
        svc_svc_journalctl["svc-journalctl"]
    end

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Features

  • Customizable retention and runtime limits
  • Seamless restarts on config update
  • Integration with sys-ctl-hlth-journalctl for downstream monitoring

Usage

- hosts: all
  roles:
    - role: sys-svc-journalctl

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).