Metoro Kubernetes Profiling vs pwru

Metoro Kubernetes Profiling continuously profiles Kubernetes workloads with an eBPF sampler running at the kernel level. It creates interactive flame graphs that can be grouped by service, pod, or container and filtered by cluster, namespace, deployment, or Kubernetes label. Metoro lists Go, Python, C++, C, Rust, Node.js, and Java support, with host-level frames for other runtimes. Profiling does not require SDKs, code changes, language agents, restarts, or rebuilds, and can cover third-party containers and vendor workloads. Profiles connect to Metoro APM traces, logs, metrics, pod state, and deployment context. Installation uses Helm, with Cloud, BYOC, and on-premises deployment options. The free Hobby plan includes one cluster, one user, and two nodes with 28-day retention. Scale costs $20 USD per node per month, plus $0.20 per GB above 100GB per node. Enterprise pricing is contract-based and offers custom retention and SLAs. eBPF requires Linux kernel 4.18 or newer.

pwru has no write-up on Specifiction yet; its figures are above.