Skip to main content
The third tier. By the time this runs, the host is ready and the apps just need to land on it.
Language: Python  ·  Status: active  ·  Last active: this week  ·  Source on GitHub
ansible-proxmox-apps deploys the app stack onto VMs and LXC containers that tofu-proxmox provisioned and ansible-proxmox configured. This is where the data-plane services that move traffic between sources and Splunk actually appear on disk.

​
What it does

  • Deploys HAProxy as the front door for syslog and NetFlow traffic
  • Deploys Cribl Edge for collection and edge-side reshaping
  • Deploys Cribl Stream for routing, transformation, and volume reduction at intake
  • Applies pinned Cribl packs to the environment; see observability content ownership
  • Wires every service so traffic flows from gear → HAProxy → Cribl Edge → Cribl Stream → Splunk

​
How it fits

This is the deploy tier. Anything that’s stateful and long-running on a homelab guest lands here.

​
Getting started

1

Confirm the hosts are configured

Run ansible-proxmox first. Hosts need their ZFS, networking, and monitoring agents in place before apps land on them.
2

Clone and enter the dev shell

git clone https://github.com/dryvist/ansible-proxmox-apps && cd ansible-proxmox-apps && nix develop
3

Required environment

The playbooks read the Cribl tokens, HAProxy stats password, and Splunk HEC tokens as environment variables.
4

Run the playbook

ansible-playbook -i inventory site.yml. Re-runs converge drift only. Safe to run on a schedule.

ansible-proxmox

Host config. Must run first.

Observability

Where the data this stack delivers ends up.

Data pipelines

End-to-end view of the log and NetFlow paths.

Source on GitHub

Roles, packs, full README.