구분설명system.cpu.norm.pct전체 cpu 사용량(%) = system.cpu.total.pct/ system.cpu.coressystem.cpu.total.pctcpu core 사용량(%)의 합system.cpu.corescpu core 수system.memory.actual.used.pct메모리 사용량(%)

ServiceAccount 생성apiVersion: v1kind: ServiceAccountmetadata: name: metricbeat namespace: kube-systemRBAC 생성: 없도 작동함(영향도를 확인 못함)apiVersion: rbac.authorization.k8s.io/v1kind: ClusterRolemetadata: name: metricbeatrules: - apiGroups: [""] resources: ["nodes", "nodes/stats", "pods", "services", "endpoints", "events"] verbs: ["get", "list", "watch"] - apiGroups: [""] resources: ["configm..

spec: serviceAccountName: metricbeat hostPID: true # ✅ Allow access to host process IDs containers: - name: metricbeat image: docker.elastic.co/beats/metricbeat:8.4.3 securityContext: privileged: true # ✅ Full access to system resources capabilities: add: - SYS_PTRACE # ✅ Allow process inspection ..

metricbeat.yml: | .. metricbeat.modules: # Monitor Elasticsearch - module: elasticsearch xpack.enabled: true period: 10s hosts: ["http://elastic-headless.elastic.svc.cluster.local:9200"] api_key: {id}:{passwd} # Monitor Kibana - module: kibana xpack.enabled: true period: 10s hosts: ["http://kibana.elastic.svc.cluster.local..

metricbeat.yml: | .. metricbeat.modules: - module: kibana xpack.enabled: true period: 10s hosts: ["http://kibana:5601"] api_key: {id}:{passwd} ..hosts정보가 잘못되었음service의 도메인 정보를 잘 기술하면 됨

metricbeat pod에 접속sudo metricbeat setup --dashboards에러 및 조치# 에러Loading dashboards (Kibana must be running and reachable)Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://localhost:5601/api/status fails: fail to execute the HTTP GET request: Get "http://localhost:5601/api/status": dial tcp 127.0.0.1:5601: connect: connection refused (status=0). Respon..