Eventarc는 모니터링 리소스의 측정항목 데이터를 Google Cloud Observability로 전송합니다. Monitoring의 모니터링 리소스는 가상 머신, 데이터베이스, 애플리케이션과 같은 논리적 또는 실제 항목을 나타냅니다. 모니터링 리소스에는 탐색하거나, 대시보드를 통해 보고하거나, 알림을 만드는 데 사용할 수 있는 고유한 측정항목 집합이 포함되어 있습니다. 각 리소스에는 리소스에 관한 추가 정보를 보유하는 키-값 쌍인 리소스 라벨 집합도 있습니다. 리소스 라벨은 리소스와 연결된 모든 측정항목에 사용할 수 있습니다.
Eventarc는 다음 모니터링 리소스의 측정항목 데이터를 Google Cloud Observability로 전송합니다.
이 표의 '측정항목 유형' 문자열 앞에 eventarc.googleapis.com/가 포함된 프리픽스를 붙여야 합니다. 표의 항목에서는 이 프리픽스가 생략되었습니다.
라벨을 쿼리할 때 metric.labels. 프리픽스를 사용합니다(예: metric.labels.LABEL="VALUE").
측정항목 유형 실행 단계(리소스 계층 구조 수준) 표시 이름
종류, 유형, 단위 모니터링 리소스
설명 라벨
quota/enrollments_per_message_bus/exceeded베타(프로젝트) 메시지 버스 할당량당 등록 횟수가 초과됨 오류
할당량 측정항목 eventarc.googleapis.com/enrollments_per_message_bus의 한도를 초과하려는 시도 횟수입니다. 샘플링되면 데이터는 최대 150초 동안 표시되지 않습니다. limit_name:
한도 이름입니다.
message_bus: 등록이 연결된 메시지 버스입니다.
quota/enrollments_per_message_bus/limit베타(프로젝트) 메시지 버스 할당량 한도당 등록 수
할당량 측정항목 eventarc.googleapis.com/enrollments_per_message_bus의 현재 한도입니다. 60초마다 샘플링됩니다. 샘플링되면 데이터는 최대 150초 동안 표시되지 않습니다. limit_name:
한도 이름입니다.
message_bus: 등록이 연결된 메시지 버스입니다.
quota/enrollments_per_message_bus/usage베타(프로젝트) 메시지 버스 할당량 사용량당 등록 수
할당량 측정항목 eventarc.googleapis.com/enrollments_per_message_bus의 현재 사용량입니다. 샘플링되면 데이터는 최대 150초 동안 표시되지 않습니다. limit_name:
한도 이름입니다.
message_bus: 등록이 연결된 메시지 버스입니다.
Cloud Monitoring API의 timeSeries.list 메서드를 사용하여 시계열 데이터라고도 하는 측정항목 데이터를 읽을 수 있습니다. 언어별 클라이언트 라이브러리를 사용하거나 측정항목 탐색기로 차트를 만드는 등 메서드를 호출하는 방법에는 여러 가지가 있습니다. 측정항목 및 시계열에 대한 소개는 측정항목, 시계열, 리소스를 참조하세요. 측정항목 데이터를 읽는 방법을 알아보려면 시계열 데이터 검색을 참조하세요.
Monitoring 대시보드 및 알림 사용
Monitoring 대시보드 및 관련 차트를 사용하여 Eventarc 측정항목에 대한 데이터를 시각화할 수 있습니다.
[[["이해하기 쉬움","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-09-04(UTC)"],[[["\u003cp\u003eEventarc utilizes Google Cloud Observability for monitoring, logging, and diagnostics, helping users analyze activity, understand application behavior, and assess performance.\u003c/p\u003e\n"],["\u003cp\u003eEventarc automatically sends data and system audit logs to Cloud Logging and system and resource metrics to Cloud Monitoring, which can be used for debugging, trend analysis, and performance monitoring.\u003c/p\u003e\n"],["\u003cp\u003eYou can use Logs Explorer and Log Analytics to query and view logs, with the ability to filter for Eventarc logs specifically.\u003c/p\u003e\n"],["\u003cp\u003eEventarc sends audit log data such as Admin Activity, Data Access, System Event, and Policy Denied to Cloud Logging, with Data Access audit logs disabled by default due to their potential size.\u003c/p\u003e\n"],["\u003cp\u003eEventarc sends metric data from monitored resources to Google Cloud Observability, and you can leverage Monitoring dashboards, charts, and alerts for visualizing and responding to this data.\u003c/p\u003e\n"]]],[],null,["[Advanced](/eventarc/advanced/docs/overview) [Standard](/eventarc/standard/docs/overview)\n\n[Google Cloud Observability](/stackdriver/docs) provides monitoring, logging, and diagnostic\ntools. These tools can help you monitor and analyze Eventarc\nactivity and growth, and understand the behavior, health, and performance of\nyour applications.\n\nBy default, Eventarc is configured to do the following:\n\n- Send data and system audit logs to Cloud Logging. You can use the collected logs to debug, troubleshoot, and gain insights about your applications.\n- Send system and resource metrics to Cloud Monitoring. You can use the collected metrics to monitor health and performance, identify trends and issues, and notify for changes in behavior.\n\nSend audit logs to Cloud Logging\n\nEventarc sends the following types of audit log data to\nCloud Logging:\n\n- [Admin Activity audit logs](/logging/docs/audit#admin-activity)\n- [Data Access audit logs](/logging/docs/audit#data-access)\n- [System Event audit logs](/logging/docs/audit#system-event)\n- [Policy Denied audit logs](/logging/docs/audit#policy_denied)\n\nData Access audit logs are\n[disabled by default](/logging/docs/audit/configure-data-access) because these\naudit logs can be quite large.\nFor more information, see [Eventarc audit logging](/eventarc/standard/docs/audit-logs) and [Eventarc publishing audit logging](/eventarc/standard/docs/audit-logs-publishing).\n\nQuery and view logs\n\nYou can use following tools to view and analyze your logs:\n\n- **Logs Explorer** is designed to help you troubleshoot and analyze the performance of your services and applications. To learn how to view logs in the Logs Explorer, follow the instructions in [View logs by using the Logs Explorer](/logging/docs/view/logs-explorer-interface).\n- **Log Analytics** is designed to run queries to analyze your logs, and then view or chart the results. To learn how to use Log Analytics, follow the instructions in [Query and analyze logs with Log Analytics](/logging/docs/analyze/query-and-view).\n\nYou can filter for Eventarc logs in the Logs Explorer by\nsearching for `eventarc` in the search field.\n\nFor more information about querying and analyzing logs, see\n[Query and view logs overview](/logging/docs/log-analytics).\n\nSend metrics to Cloud Monitoring\n\nEventarc sends metric data from monitored resources to\nGoogle Cloud Observability. A monitored resource in Monitoring represents a\nlogical or physical entity, such as a virtual machine, a database, or an\napplication. Monitored resources contain a unique set of metrics that can be\nexplored, reported through a dashboard, or used to create alerts. Each resource\nalso has a set of resource labels, which are key-value pairs that hold\nadditional information about the resource. Resource labels are available for all\nmetrics associated with the resource.\n\nEventarc sends metric data from the following monitored resource\nto Google Cloud Observability:\n\n- [`eventarc.googleapis.com/Location`](/monitoring/api/resources#tag_eventarc.googleapis.com/Location)\n\nResource metrics and labels\n\n\nThe \"metric type\" strings in this table must be prefixed\nwith `eventarc.googleapis.com/`. That prefix has been\nomitted from the entries in the table.\nWhen querying a label, use the `metric.labels.` prefix; for\nexample, `metric.labels.`\u003cvar translate=\"no\"\u003eLABEL\u003c/var\u003e`=\"`\u003cvar translate=\"no\"\u003eVALUE\u003c/var\u003e`\"`.\n\n| Metric type ^Launch stage^ *(Resource hierarchy levels)* Display name ||\n| Kind, Type, Unit Monitored resources | *Description* Labels |\n|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `quota/enrollments_per_message_bus/exceeded` ^BETA^ ***(project)*** Enrollments per message bus quota exceeded error ||\n| `DELTA`, `INT64`, `1` \u003cbr /\u003e **[eventarc.googleapis.com/Location](/monitoring/api/resources#tag_eventarc.googleapis.com/Location)** | *Number of attempts to exceed the limit on quota metric eventarc.googleapis.com/enrollments_per_message_bus. After sampling, data is not visible for up to 150 seconds.* \u003cbr /\u003e `limit_name`: The limit name. \u003cbr /\u003e `message_bus`: The message bus that the enrollments are attached to. |\n| `quota/enrollments_per_message_bus/limit` ^BETA^ ***(project)*** Enrollments per message bus quota limit ||\n| `GAUGE`, `INT64`, `1` \u003cbr /\u003e **[eventarc.googleapis.com/Location](/monitoring/api/resources#tag_eventarc.googleapis.com/Location)** | *Current limit on quota metric eventarc.googleapis.com/enrollments_per_message_bus. Sampled every 60 seconds. After sampling, data is not visible for up to 150 seconds.* \u003cbr /\u003e `limit_name`: The limit name. \u003cbr /\u003e `message_bus`: The message bus that the enrollments are attached to. |\n| `quota/enrollments_per_message_bus/usage` ^BETA^ ***(project)*** Enrollments per message bus quota usage ||\n| `GAUGE`, `INT64`, `1` \u003cbr /\u003e **[eventarc.googleapis.com/Location](/monitoring/api/resources#tag_eventarc.googleapis.com/Location)** | *Current usage on quota metric eventarc.googleapis.com/enrollments_per_message_bus. After sampling, data is not visible for up to 150 seconds.* \u003cbr /\u003e `limit_name`: The limit name. \u003cbr /\u003e `message_bus`: The message bus that the enrollments are attached to. |\n\nTable generated at 2025-08-28 21:10:54 UTC.\n\nTo view all resource types, see [Monitored resource types](/monitoring/api/resources).\nTo view all metric types, see [Google Cloud metrics](/monitoring/api/metrics_gcp).\n\nRead metric data\n\nYou can read metric data, also called time-series data, by using the\n`timeSeries.list` method in the Cloud Monitoring API. There are several ways to\ncall the method, including using a language-specific client library, or by\ncreating a chart with\n[Metrics Explorer](/monitoring/charts/metrics-explorer). For an introduction to metrics\nand time series, see\n[Metrics, time series, and resources](/monitoring/api/v3/metrics). To learn how\nto read your metric data, see\n[Retrieve time-series data](/monitoring/custom-metrics/reading-metrics).\n\nUse Monitoring dashboards and alerts\n\nYou can use Monitoring dashboards and their associated charts to\nvisualize the data for Eventarc metrics.\n\nTo monitor these metrics in Monitoring, you can\n[create custom dashboards](/monitoring/charts/dashboards#custom_dashboards).\nYou can also [add alerts](/monitoring/alerts/using-alerting-api) based on\nthese metrics.\n\nWhat's next\n\n- [Eventarc audit logging](/eventarc/standard/docs/audit-logs)\n- [Troubleshoot issues](/eventarc/docs/troubleshooting)"]]
