Google Cloud Observabilityprovides monitoring, logging, and diagnostic
tools. These tools can help you monitor and analyze Eventarc
activity and growth, and understand the behavior, health, and performance of
your applications.
By default, Eventarc is configured to do the following:
Send data and system audit logs to Cloud Logging. You can use the collected
logs to debug, troubleshoot, and gain insights about your applications.
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.
Send audit logs to Cloud Logging
Eventarc sends the following types of audit log data to
Cloud Logging:
You can use following tools to view and analyze your logs:
Logs Exploreris 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 inView logs by using the Logs Explorer.
Log Analyticsis 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 inQuery and analyze logs with Log Analytics.
You can filter for Eventarc logs in the Logs Explorer by
searching foreventarcin the search field.
Eventarc sends metric data from monitored resources to
Google Cloud Observability. A monitored resource in Monitoring represents a
logical or physical entity, such as a virtual machine, a database, or an
application. Monitored resources contain a unique set of metrics that can be
explored, reported through a dashboard, or used to create alerts. Each resource
also has a set of resource labels, which are key-value pairs that hold
additional information about the resource. Resource labels are available for all
metrics associated with the resource.
Eventarc sends metric data from the following monitored resource
to Google Cloud Observability:
The "metric type" strings in this table must be prefixed
witheventarc.googleapis.com/. That prefix has been
omitted from the entries in the table.
When querying a label, use themetric.labels.prefix; for
example,metric.labels.LABEL="VALUE".
Metric type Launch stage(Resource hierarchy levels) Display name
Kind, Type, Unit Monitored resources
Description Labels
quota/enrollments_per_message_bus/exceededBETA(project) Enrollments per message bus quota exceeded error
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. limit_name:
The limit name. message_bus:
The message bus that the enrollments are attached to.
quota/enrollments_per_message_bus/limitBETA(project) Enrollments per message bus quota limit
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. limit_name:
The limit name. message_bus:
The message bus that the enrollments are attached to.
quota/enrollments_per_message_bus/usageBETA(project) Enrollments per message bus quota usage
Current usage on quota metric eventarc.googleapis.com/enrollments_per_message_bus. After sampling, data is not visible for up to 150 seconds. limit_name:
The limit name. message_bus:
The message bus that the enrollments are attached to.
You can read metric data, also called time-series data, by using thetimeSeries.listmethod in the Cloud Monitoring API. There are several ways to
call the method, including using a language-specific client library, or by
creating a chart withMetrics Explorer. For an introduction to metrics
and time series, seeMetrics, time series, and resources. To learn how
to read your metric data, seeRetrieve time-series data.
Use Monitoring dashboards and alerts
You can use Monitoring dashboards and their associated charts to
visualize the data for Eventarc metrics.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-05 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)"]]
