kubearmor-client/profile
mrrishi 3433e4b58f probe: fix namespace field to the policies list
Signed-off-by: mrrishi <mrrishi373@gmail.com>
Signed-off-by: jokestax <mrrishi373@gmail.com>
Signed-off-by: mrrishi <mrrishi373@gmail.com>

Signed-off-by: rksharma95 <ramakant@accuknox.com>
2026-01-02 10:21:04 +05:30
..
Client probe: fix namespace field to the policies list 2026-01-02 10:21:04 +05:30
pathAggregator.go probe: fix namespace field to the policies list 2026-01-02 10:21:04 +05:30
profile.go probe: fix namespace field to the policies list 2026-01-02 10:21:04 +05:30
README.md Add profile docs for filtering 2025-06-09 14:10:04 +05:30
types.go Karmor support for windows and removal of cilium (#471) 2025-01-16 17:03:45 +05:30

Profiling of Kubearmor Logs using karmor

karmor profile provides a real-time terminal UI that visualizes security-relevant activity observed by KubeArmor, including Process, File, and Network events. It fetches live data from the KubeArmor logs API, displays counters and key details for each event type, and supports easy navigation and filtering.

Profile

🔍 Filtering Logs with karmor profile

The karmor profile command allows you to filter logs or alerts using a set of useful flags. These filters help narrow down the output to specific Kubernetes objects like containers, pods, and namespaces.

🧰 Available Filters

Flag Description
-c, --container Filters logs by container name.
-n, --namespace Filters logs by Kubernetes namespace.
--pod Filters logs by pod name.

📌 Usage Examples

Filter by Container Name

karmor profile -c nginx

Outputs logs only from the container named nginx.


Filter by Namespace

karmor profile -n nginx1

Outputs logs only from the namespace nginx1.


Filter by Pod

karmor profile --pod nginx-pod-1

Outputs logs only from the pod named nginx-pod-1.


🔗 Combine Multiple Filters

You can combine filters to narrow down the logs even further.

karmor profile -n nginx1 -c nginx

Outputs logs only from the nginx container in the nginx1 namespace.


💡 Tip

Use these filters during profiling sessions to quickly isolate behavior or security events related to a specific pod, container, or namespace.