Splunk Technology Add-on
TA-service
systemd health
Free for personal use ยท commercial license required
System
systemctl + journalctl (always present)
Why TA-service exists
A crash-looping unit can hide for weeks. TA-service surfaces failures, restart storms and timeouts, and tracks degraded targets so the box says when it is not healthy.
What it collects
- Unit state transitions and failures
- Restart-loop detection
- Start timeouts and degraded targets
Runs on stock tools
No daemons, no agents, no exotic collectors - it shells out to well-known CLIs or reads sysfs, and parses the result into Splunk events.
External tools used: systemctl + journalctl (always present).