Home Explore Blog CI



3eb3ca97508874430913038aa98a969c00812c6cefe8dd510000000200008ba5.png

Extracted Text
root@ubuntu:~/sysdig/build/release/userspace/sysdig 175x14 Viewing: KBs Controllers For: whole machine Source: to.scap (257142 evts, 3.90s) Filter: k8s.rc.id != "" CPU VIRT RES FILE NET ID 29.00 4M 254K SK 87.96K dcb78315-7e8c-11e5-8f05-000c297da085 wordpress 10.50 839K 453K 648K 17.94K dc87420c-7e8c-11e5-8f05-000c297da005 mysql 0.25 505K 22K 135K 70.02K dcele186-768c-1165-8105-000c297da085 client Filele F2 Views Filter Echo Fopig F7Les Fotos CTRL+Fearch Pause NAME NAMESPACE LABELS loris app:demo, name:wordpress, role: frontend loris app:deno, name:mysql, role:mysqldb loris app:deno, name:client, role:clients 1/3(33.3%)
Explanation
This image depicts a terminal window showing information about Kubernetes controllers running on a machine. The output displays CPU usage, virtual memory (VIRT), resident set size (RES), file usage, and network ID, along with the name, namespace, and labels associated with each controller (wordpress, mysql, client). The data appears to be filtered based on 'k8s.rc.id' not being empty, and the source is 'lo.scap' with a specified number of events.