Demystifying event filters in Eventarc

Eventarc enables you to read events from Google Cloud sources (via its Audit Logs integration) and custom sources (via its Pub/Sub integration) and then route them to Cloud Run services. The event routing rules are defined with a trigger. In a trigger, you specify the right event filters such as service name, method name, resource (which effectively defines the event source) and the target of the events (which can only be a Cloud Run service as of today).

Let’s take a closer look at how to configure these triggers with the right event filters.

Triggers with Cloud Console The easiest way to create triggers with the right filters is from Cloud Console. If you go to Cloud Run > Trigger and attempt to create a trigger, you’ll see the list of services supported via Pub/Sub or Audit Logs integration:

See also