kubeaudit VS cadvisor

kubeaudit: audit kubernetes or specific manifests for issues https://github.com/shopify/kubeaudit

Here's a link to KubeAudit on Github

kubeaudit - Audit Kubernetes clusters against common security concerns

Workload configuration should be audited regularly (Kics, Kubeaudit, Kubescape, Conftest, Kubesec, Checkov)

Kubeaudit

cAdvisor

For CPU and memory metrics, you can use cAdvisor to collect container level data.

We could have used a much more focussed tool like Prometheus or Cadvisor to gather system stats, but that is not the main objective of this article.

If you're running things under systemd, you can enable process accounting and use cAdvisor.

Container Advisor (cAdvisor) is an open-source metrics collection agent specifically built for containers. This solution runs at a node level, since it comes integrated with the kubelet service as one of the binaries. cAdvisor gathers data on CPU usage, memory usage, network status, and storage for every live container, helping administrators gain insight into machine-level performance metrics.

That said, cadvisor should work great. You'd want to have prometheus scrape those metrics. In particular you'd probably be interested in container_network_receive_bytes_total and container_network_transmit_bytes_total. Reference: https://github.com/google/cadvisor/blob/master/docs/storage/prometheus.md

cAdvisor é um agente de monitoramento para containers e tem suporte nativo ao Docker.

cAdvisor, an observability tool, has made monitoring containers easy. It gives users insight into the resource consumption and performance aspects of their running containers. cAdvisor is an open-source running daemon that aggregates processes and exports information about containers that are running. It saves resource isolation settings, historical resource consumption, histograms of total historical resource usage, and network data for each container. This information is exported by container as well as machine-wide.

cAdvisor: container_oom_events_total