Eventarc Advanced lets you use buses to collect event messages from
diverse providers and route them to supported destinations. You can use
pipelines to filter, transform, and deliver events to target services such as
Cloud Run and Workflows.

## Supported providers

Supported providers include Google providers and direct publishers of events
(using the Eventarc Publishing API).

- Google providers send [Google events](https://docs.cloud.google.com/eventarc/advanced/docs/event-types.md.txt)
  directly from the source (for example, the creation of a
  Cloud Run function or a status change to a Dataflow
  job). You must first enable support for Google event types. For more information,
  see
  [Publish events from Google sources](https://docs.cloud.google.com/eventarc/advanced/docs/publish-events/publish-events-google-sources.md.txt).

- Event publishers can publish a
  [CloudEvents event](https://docs.cloud.google.com/eventarc/advanced/docs/event-format.md.txt) directly to a message
  bus in a supported format such as Avro or Protobuf. For more information, see
  [Publish events directly](https://docs.cloud.google.com/eventarc/advanced/docs/publish-events/publish-events-direct-format.md.txt).

## Supported destinations

An Eventarc Advanced pipeline delivers events between a bus and
a destination. Each pipeline forwards messages to a single destination. The
following destinations are supported:

- Cloud Run---Use the stable,
  [auto-assigned `run.app` URL](https://docs.cloud.google.com/run/docs/triggering/https-request.md.txt) provided on
  the first deployment of the Cloud Run-hosted service. You can also
  target a
  [Cloud Run job](https://docs.cloud.google.com/run/docs/overview/what-is-cloud-run.md.txt#cloud-run-jobs)
  or specify an HTTP endpoint for Cloud Run functions
  ([1st gen](https://docs.cloud.google.com/functions/1stgendocs/calling/http.md.txt) and
  [current version](https://docs.cloud.google.com/functions/docs/calling/http)). When you specify an HTTP
  trigger for a Cloud Run function, the function is assigned a
  URL at which it can receive requests.

- Eventarc Advanced bus---The
  [message bus](https://docs.cloud.google.com/eventarc/advanced/docs/publish-events/create-bus.md.txt) must be
  deployed in the same project and region as the pipeline.

- HTTP endpoint---A destination URI. The host can be either a static IP
  addressable from a [Virtual Private Cloud (VPC) network](https://docs.cloud.google.com/vpc/docs/vpc.md.txt), or the
  internal [Domain Name System (DNS)](https://docs.cloud.google.com/dns/docs/dns-overview.md.txt) hostname of a
  service resolvable using Cloud DNS. For example, you can target a
  [Cloud Run service URL](https://docs.cloud.google.com/run/docs/triggering/https-request.md.txt#url)
  or a [BigQuery table](https://docs.cloud.google.com/bigquery/docs/reference/rest/v2/tabledata/insertAll.md.txt)
  that will receive events as HTTP `POST` requests.

- Pub/Sub topic---The
  [Pub/Sub topic](https://docs.cloud.google.com/pubsub/docs/publish-message-overview.md.txt) must first
  be created before messages can be routed to it and must be located in the same
  project as the pipeline. If using a
  [topic schema](https://docs.cloud.google.com/pubsub/docs/create-topic.md.txt#use_a_schema), make sure to
  [transform your event message](https://docs.cloud.google.com/eventarc/advanced/docs/receive-events/transform-events.md.txt)
  appropriately.

- Workflows---You can trigger the
  [execution of a workflow](https://docs.cloud.google.com/workflows/docs/executing-workflow.md.txt) which is a
  single run of the logic contained in a workflow definition. This lets you run
  services in an order that you specify. The workflow must be deployed in the same
  project as the pipeline.