Peristiwa dikumpulkan dari penyedia peristiwa oleh bus Eventarc Advanced dan dirutekan melalui pipeline Eventarc Advanced ke tujuan yang ditentukan. Hanya satu tujuan yang dapat menjadi target pesan yang diteruskan oleh pipeline.
Penyedia yang didukung
Penyedia yang didukung mencakup penyedia Google dan penerbit langsung peristiwa (menggunakan Eventarc Publishing API).
Penyedia Google mengirimkan peristiwa Google
langsung dari sumber (misalnya, pembuatan fungsi
Cloud Run atau perubahan status pada tugas
Dataflow). Anda harus mengaktifkan dukungan untuk jenis acara Google terlebih dahulu. Untuk mengetahui informasi selengkapnya, lihat
Memublikasikan peristiwa dari sumber Google.
Pipeline Lanjutan Eventarc memungkinkan pengiriman peristiwa
antara bus dan tujuan. Tujuan berikut didukung:
Cloud Run—Gunakan URL yang ditetapkan otomatis run.app yang stabil dan disediakan saat deployment pertama layanan yang dihosting Cloud Run. Anda juga dapat
menargetkan
Cloud Run job
atau menentukan endpoint HTTP untuk fungsi Cloud Run
(generasi ke-1 dan
versi saat ini). Saat Anda menentukan pemicu HTTP untuk fungsi Cloud Run, fungsi tersebut akan diberi URL yang dapat digunakan untuk menerima permintaan.
Bus lanjutan Eventarc—Bus pesan harus di-deploy di project dan region yang sama dengan pipeline.
Topik Pub/Sub—Topik Pub/Sub harus dibuat terlebih dahulu sebelum pesan dapat dirutekan ke topik tersebut dan harus berada di project yang sama dengan pipeline. Jika menggunakan
skema topik, pastikan untuk
mengubah pesan acara Anda
dengan tepat.
Alur Kerja—Anda dapat memicu
eksekusi alur kerja yang merupakan
satu eksekusi logika yang terkandung dalam definisi alur kerja. Hal ini memungkinkan Anda menjalankan layanan dalam urutan yang Anda tentukan. Alur kerja harus di-deploy di
project yang sama dengan pipeline.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eEventarc Advanced is a pre-GA feature that collects events from various providers and routes them through a pipeline to a single specified destination.\u003c/p\u003e\n"],["\u003cp\u003eSupported event providers include Google services, which send Google events, and direct publishers that use the Eventarc Publishing API to send CloudEvents.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced pipelines can deliver events to several destinations, including Cloud Run services or jobs, other Eventarc Advanced buses, HTTP endpoints, Pub/Sub topics, and Workflows.\u003c/p\u003e\n"],["\u003cp\u003eNetwork attachments can be used to establish connections to Cloud Run, Eventarc Advanced buses, and HTTP endpoints hosted in a Virtual Private Cloud (VPC).\u003c/p\u003e\n"],["\u003cp\u003eDestinations such as Eventarc Advanced bus, Pub/Sub topics, and workflows must be located in the same Google Cloud project as the pipeline.\u003c/p\u003e\n"]]],[],null,["# Event providers and destinations\n\n[Advanced](/eventarc/advanced/docs/overview)\n\nEvents are collected from event providers by an Eventarc Advanced\nbus and routed through an Eventarc Advanced pipeline to a\nspecified destination. Only one destination can be the target of messages\nforwarded by a pipeline.\n\nSupported providers\n-------------------\n\nSupported providers include Google providers and direct publishers of events\n(using the Eventarc Publishing API).\n\n- Google providers send [Google events](/eventarc/advanced/docs/event-types)\n directly from the source (for example, the creation of a\n Cloud Run function or a status change to a Dataflow\n job). You must first enable support for Google event types. For more information,\n see\n [Publish events from Google sources](/eventarc/advanced/docs/publish-events/publish-events-google-sources).\n\n- Event publishers can publish a\n [CloudEvents event](/eventarc/advanced/docs/event-format) directly to a message\n bus in a supported format such as Avro or Protobuf. For more information, see\n [Publish events directly](/eventarc/advanced/docs/publish-events/publish-events-direct-format).\n\nSupported destinations\n----------------------\n\nAn Eventarc Advanced pipeline enables the delivery of events\nbetween a bus and a destination. The following destinations are\nsupported:\n\n- Cloud Run---Use the stable,\n [auto-assigned `run.app` URL](/run/docs/triggering/https-request) provided on\n the first deployment of the Cloud Run-hosted service. You can also\n target a\n [Cloud Run job](/run/docs/overview/what-is-cloud-run#cloud-run-jobs)\n or specify an HTTP endpoint for Cloud Run functions\n ([1st gen](/functions/1stgendocs/calling/http) and\n [current version](/functions/docs/calling/http)). When you specify an HTTP\n trigger for a Cloud Run function, the function is assigned a\n URL at which it can receive requests.\n\n- Eventarc Advanced bus---The\n [message bus](/eventarc/advanced/docs/publish-events/create-bus) must be\n deployed in the same project and region as the pipeline.\n\n- HTTP endpoint---A destination URI. The host can be either a static IP\n addressable from a [Virtual Private Cloud (VPC) network](/vpc/docs/vpc), or the\n internal [Domain Name System (DNS)](/dns/docs/dns-overview) hostname of a\n service resolvable using Cloud DNS. For example, you can target a\n [Cloud Run service URL](/run/docs/triggering/https-request#url)\n or a [BigQuery table](/bigquery/docs/reference/rest/v2/tabledata/insertAll)\n that will receive events as HTTP `POST` requests.\n\n- Pub/Sub topic---The\n [Pub/Sub topic](/pubsub/docs/publish-message-overview) must first\n be created before messages can be routed to it and must be located in the same\n project as the pipeline. If using a\n [topic schema](/pubsub/docs/create-topic#use_a_schema), make sure to\n [transform your event message](/eventarc/advanced/docs/receive-events/transform-events)\n appropriately.\n\n- Workflows---You can trigger the\n [execution of a workflow](/workflows/docs/executing-workflow) which is a\n single run of the logic contained in a workflow definition. This lets you run\n services in an order that you specify. The workflow must be deployed in the same\n project as the pipeline."]]
