[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eEventarc routes events to destinations through configured filters on triggers, with configurations varying by event type.\u003c/p\u003e\n"],["\u003cp\u003eEventarc supports direct events from integrated Google providers, Cloud Audit Logs, and Pub/Sub messages, enabling actions based on specific events.\u003c/p\u003e\n"],["\u003cp\u003eDirect events are generally preferred over audit log events due to improved responsiveness, typed event formats, filtering support, and no additional Cloud Audit Log costs.\u003c/p\u003e\n"],["\u003cp\u003eWhen selecting an event route, users should assess whether direct events, Cloud Audit Logs, or Pub/Sub are supported and which method best provides the necessary information.\u003c/p\u003e\n"],["\u003cp\u003eUsing Eventarc with Pub/Sub offers the benefit of standardized event delivery and formatting through CloudEvents, potentially offering efficiency for multiple event sources.\u003c/p\u003e\n"]]],[],null,["# Event routes\n\n[Standard](/eventarc/standard/docs/overview)\n\nYou can route events to your destination by configuring filters for an\nEventarc trigger. The trigger configuration varies depending on the\ntype of event. The event route you select also depends on the event type.\n\nEvent types\n-----------\n\n- **Direct events from an integrated Google provider** --- Eventarc\n can route direct events such as an update to an object in a Cloud Storage\n bucket or an update to a Firebase Remote Config template. See the list of\n [supported direct events](/eventarc/docs/reference/supported-events#directly-from-a-google-cloud-source).\n\n- **Cloud Audit Logs and Eventarc** --- When an audit log\n is produced that matches the Eventarc trigger's filter criteria,\n events are routed, allowing you to capture and act on specific events. See the\n list of\n [supported audit log events](/eventarc/docs/reference/supported-events#using-cloud-audit-logs).\n\n- **Pub/Sub and Eventarc** --- When a message is\n published to a Pub/Sub topic specified by the\n Eventarc trigger's filter criteria\n (`\"type=google.cloud.pubsub.topic.v1.messagePublished\"`), events are routed. You\n can integrate Eventarc with any service that can publish\n messages using Pub/Sub.\n\n- **Direct Pub/Sub push** --- Instead of using Eventarc,\n you can use Pub/Sub to directly push messages to your service.\n This applies to applications or services that have a direct Pub/Sub\n integration. For more information, see\n [Trigger from Pub/Sub push](/run/docs/triggering/pubsub-push).\n\nSelect an event route\n---------------------\n\nTo determine how best to route your events to a destination, ask yourself the\nfollowing questions:\n\n1. Does Eventarc support direct events for the event that you\n want to route? If yes, create an Eventarc trigger to route that\n direct event. If no, consider the next question (#2).\n\n For the event that you want to route, if both direct and audit log options are\n supported, we recommend that you create a trigger to route the direct event.\n Direct events offer the following advantages over audit log events:\n - Improved trigger responsiveness and event delivery latency\n - Strongly typed event formats that are more predictable and discoverable\n - Support for filtering on collection IDs ([resource name](/apis/design/resource_names) components)\n - No additional costs incurred from enabling Cloud Audit Logs\n2. Does your Google service or application support Cloud Audit Logs,\n Pub/Sub, or both?\n\n3. If both Cloud Audit Logs and Pub/Sub are supported,\n which of the two provides the required information? For example, Cloud Build\n can generate both audit logs and Pub/Sub messages; however,\n Pub/Sub can provide build status notifications (success or\n failure) while the Cloud Build audit logs can provide information\n about build creation and deletion operations. In some cases, the content and\n latency impact of both the audit logs and Pub/Sub messages is\n comparable, and you can choose either. You should then consider the next\n question (#4).\n\n4. If using Pub/Sub, is there any advantage to receiving events\n through Eventarc and a common\n [CloudEvents](/eventarc/docs/cloudevents) format? For example, are there\n multiple event sources? Although you might be more familiar with pushing\n Pub/Sub messages directly, you might want the efficiency and\n convenience of a standard delivery mechanism and format.\n\nWhat's next\n-----------\n\n- [Learn how to create an Eventarc trigger](/eventarc/standard/docs/event-providers-targets#triggers).\n- [Determine event filters for Cloud Audit Logs](/eventarc/docs/determining-filters-cal).\n- [Learn how to receive Cloud Storage events using Cloud Audit Logs](/eventarc/standard/docs/run/create-trigger-cloud-audit-logs-gcloud)."]]
