Google Cloud Observability provides 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:
Data Access audit logs are disabled by default because these audit logs can be quite large.
For more information, see Eventarc audit logging and Eventarc publishing audit logging.Query and view logs
You can use following tools to view and analyze your logs:
- 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.
- 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.
You can filter for Eventarc logs in the Logs Explorer by
searching for eventarc in the search field.
For more information about querying and analyzing logs, see Query and view logs overview.
View Eventarc Advanced logs
In addition to Cloud Logging tools, you can view Eventarc Advanced logs using the Google Cloud console.
In the Google Cloud console, go to the Eventarc > Bus page:
Or, go to the Eventarc > Pipelines page:
To go to the Pipeline details page, click a pipeline's name.
From either the Bus details or Pipeline details page, click the Logs tab.
The Logs tab displays the following types of logs:
Platform logs written by Eventarc and sent to Logging. These logs can help you debug and troubleshoot issues, and help you better understand the Google Cloud services you're using.
Audit logs of any operations performed, such as an update to the configuration of a pipeline.
To filter the logs by severity, in the Default list, select the type of log to display. By default, logs of all severity levels are shown.
The severity of an event described in a log entry is expressed as one of several standard severity levels. If you are writing log entries, you can specify the minimum severity for events described in log entries and you can map other severity encodings to one of the standard levels. For more information, see
LogSeverity.You can search for entries across all log fields. To the right of Filter, in the Search all fields and values field, type your text.
You can specify an exact match to a value—for example,
payload = "jsonPayload". Or, you can use regular expressions to match against specific fields. The full Logging query language is supported.
Send metrics to Cloud Monitoring
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:
Resource metrics and labels
The "metric type" strings in this table must be prefixed
with eventarc.googleapis.com/. That prefix has been
omitted from the entries in the table.
When querying a label, use the metric.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/exceeded
BETA
(project)
Enrollments per message bus quota exceeded error |
|
DELTA, INT64, 1
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.
limit_name:
The limit name.
message_bus:
The message bus that the enrollments are attached to.
|
quota/enrollments_per_message_bus/limit
BETA
(project)
Enrollments per message bus quota limit |
|
GAUGE, INT64, 1
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.
limit_name:
The limit name.
message_bus:
The message bus that the enrollments are attached to.
|
quota/enrollments_per_message_bus/usage
BETA
(project)
Enrollments per message bus quota usage |
|
GAUGE, INT64, 1
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.
limit_name:
The limit name.
message_bus:
The message bus that the enrollments are attached to.
|
Table generated at 2025-01-24 16:56:52 UTC.
To view all resource types, see Monitored resource types. To view all metric types, see Google Cloud metrics.
Read metric data
You can read metric data, also called time-series data, by using the
timeSeries.list method 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 with
Metrics Explorer. For an introduction to metrics
and time series, see
Metrics, time series, and resources. To learn how
to read your metric data, see
Retrieve time-series data.
Use Monitoring dashboards and alerts
You can use Monitoring dashboards and their associated charts to visualize the data for Eventarc metrics.
To monitor these metrics in Monitoring, you can create custom dashboards. You can also add alerts based on these metrics.