KEM-Agent
KEM Agent collects Kubernetes cluster events, filters them with CEL expressions, and forwards them to observability backends or exposes them as Prometheus…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
48/100 Fair
- Maintained
- 80last commit 41 days ago
- Popular
- 144 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 4
- Open issues
- 5
- Last commit
- 2026-10-11
- License
- MIT
- Activity
- stale
Checked yesterday - source: GitHub (shibernetes/kem-agent)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Installation & Status Install via the Helm chart or prebuilt release artifacts. The project is in alpha; the configuration format may change before version 1.0. source
Fetched 49 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can KEM-Agent be installed?
It can be installed via the Helm chart or prebuilt release artifacts.
Will the configuration format remain stable across releases?
No, the project is in alpha and the configuration format may change before version 1.0. Release notes describe each change.
Where does KEM-Agent store its progress so it can resume after a restart or upgrade?
Checkpoints are saved in a ConfigMap or a file.
Can KEM-Agent filters be updated without restarting the agent?
Yes, hot reload updates filters without restarting the agent.
Does a slow observability backend delay the other sinks?
No, every sink has its own queue. The metrics sink has no queue and counts events as they arrive.
Answers sourced from github.com
Community
- KEM Message Board (forum)
Collected 49 days ago - public community threads