이 문서에서는 Google Cloud 콘솔을 사용하여 지정한 조건을 충족하는 가상 머신(VM)에서 실행되는 프로세스 수를 모니터링하는 알림 정책을 만드는 방법을 설명합니다. 이 유형의 알림 정책을 프로세스 상태 알림 정책이라고도 합니다.
예를 들어 루트 사용자가 시작한 프로세스 수를 계산할 수 있습니다.
또한 특정 문자열이 포함된 호출 명령어의 프로세스 수를 계산할 수 있습니다. 알림 정책은 프로세스 수가 특정 기준보다 많거나 적을 때 알림을 표시할 수 있습니다.
모니터링할 수 있는 프로세스에 대한 자세한 내용은 모니터링되는 프로세스를 참조하세요.
이 콘텐츠는 로그 기준 알림 정책에 적용되지 않습니다.
특정 메시지가 로그에 표시될 때 알림을 표시하는 로그 기준 알림 정책에 대한 자세한 내용은 로그 모니터링을 참조하세요.
시작하기 전에
Google Cloud 콘솔을 사용하여 알림 정책을 만들고 수정하는 데 필요한 권한을 얻으려면 관리자에게 프로젝트에 대한 모니터링 편집자(roles/monitoring.editor) IAM 역할을 부여해 달라고 요청하세요.
역할 부여에 대한 자세한 내용은 프로젝트, 폴더, 조직에 대한 액세스 관리를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-28(UTC)"],[],[],null,["# Monitor count of processess on a VM\n\nThis document describes how to use the Google Cloud console to create an alerting\npolicy that monitors the number of processes running on your\nvirtual machines (VMs) that meet conditions you specify. This type of\nalerting policy is sometimes called a *process-health* alerting policy.\nFor example, you can count the number of processes started by the root user.\nYou can also count the number of processes whose invocation command contained\na specific string. An alerting policy can notify you when\nthe number of processes is more than, or less than, a threshold.\nFor information about which processes can be monitored,\nsee [Processes that are monitored](#process-health-processes).\n\n\nThis content does not apply to log-based alerting policies.\nFor information about log-based alerting policies, which notify you when a\nparticular message appears in your logs, see\n[Monitoring your logs](/logging/docs/alerting/monitoring-logs).\n\nBefore you begin\n----------------\n\n1.\n\n To get the permissions that\n you need to create and modify alerting policies by using the Google Cloud console,\n\n ask your administrator to grant you the\n\n\n [Monitoring Editor](/iam/docs/roles-permissions/monitoring#monitoring.editor) (`roles/monitoring.editor`)\n IAM role on your project.\n\n\n For more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\n You might also be able to get\n the required permissions through [custom\n roles](/iam/docs/creating-custom-roles) or other [predefined\n roles](/iam/docs/roles-overview#predefined).\n\n For more information about Cloud Monitoring roles,\n see [Control access with Identity and Access Management](/monitoring/access-control).\n2. Ensure that you're familiar with the general concepts of alerting policies.\n For information about these topics, see\n [Alerting overview](/monitoring/alerts).\n\n3. Configure the notification channels that you want to use to receive any\n alerts. For redundancy purposes, we also recommend that you create\n multiple types of notification channels. For information about these steps,\n see [Create and manage notification channels](/monitoring/support/notification-options).\n\n4. Ensure that you've installed the Ops Agent on the VMs that you want\n to monitor. For more information, see\n [Google Cloud Observability agents](/monitoring/agent).\n\nCreate alerting policy\n----------------------\n\nTo create an alerting policy that monitors the count of processes running on\na VM by using the Cloud Monitoring API, the filter expression must specify\na time series selector. For an example of a JSON file that specifies this\nselector, see [Process-health policy](/monitoring/alerts/policies-in-json#json-process-health).\n\nTo create an alerting policy that monitors the count of processes running on\na VM, do the following:\n\n1. In the Google Cloud console, go to the\n *notifications* **Alerting** page:\n\n [Go to **Alerting**](https://console.cloud.google.com/monitoring/alerting)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. Select **Create policy**.\n3. Select **?** on the **Select metric** section header and then select\n **Direct filter mode** in the tooltip.\n\n4. Enter a Monitoring filter.\n\n For example, to count the number of processes that are running on\n Compute Engine VM instances whose name includes `nginx`, enter the\n following: \n\n select_process_count(\"monitoring.regex.full_match(\\\".*nginx.*\\\")\")\n resource.type=\"gce_instance\"\n\n For syntax information see the following resources:\n - For filters used to count processes running on virtual machines, see [Process-health filters](/monitoring/api/v3/process-health-filters).\n - For general syntax, see [Monitoring filters](/monitoring/api/v3/filters).\n5. Complete the alerting policy. You must configure the condition trigger,\n notifications, documentation, and policy name,\n and then click **Create policy**.\n\n For more information, see\n [Create metric-threshold alerting policies](/monitoring/alerts/using-alerting-ui).\n\nProcesses that are monitored\n----------------------------\n\nNot all processes running in your system can be monitored by a process-health\ncondition. This condition selects processes to be monitored by using a regular\nexpression that is applied to the command line that invoked the process. When\nthe command line field isn't available, the process can't be monitored.\n\nOne way to determine if a process can be monitored by a process-health condition\nis to look at the active processes. For example, on a Linux system, you\ncan use the `ps` command: \n\n ps aux | grep nfs\n USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND\n root 1598 0.0 0.0 0 0 ? S\u003c Oct25 0:00 [nfsd4]\n root 1639 0.0 0.0 0 0 ? S Oct25 2:33 [nfsd]\n root 1640 0.0 0.0 0 0 ? S Oct25 2:36 [nfsd]\n\nWhen a `COMMAND` entry is wrapped with square brackets, for example `[nfsd]`,\nthe command-line information for the process isn't available. In this situation,\nyou can't use Cloud Monitoring to monitor the process."]]
