An Eventarc trigger declares your interest in a certain event or set
of events. You can configure event routing by specifying filters for the trigger,
including the event source, and the target Cloud Run service.

Eventarc delivers events to the event receiver in a
[CloudEvents format](https://docs.cloud.google.com/eventarc/docs/cloudevents.md.txt) through an HTTP request.

These instructions show you how to configure routing to your Cloud Run
service that is triggered when an audit log is created that matches the
trigger's filter criteria. For a list of the audit log events supported by
Eventarc, including `serviceName` and `methodName` values, see
[Google event types supported by Eventarc](https://docs.cloud.google.com/eventarc/docs/reference/supported-events.md.txt#using-cloud-audit-logs).

For more information about capturing events that are triggered when an audit log
is created that matches the trigger's filter criteria, see
[Determine event filters for Cloud Audit Logs](https://docs.cloud.google.com/eventarc/docs/determining-filters-cal.md.txt).

> [!NOTE]
> **Note:** If both direct and audit log events are supported for a Google provider, we recommend that you create a trigger that filters for the direct event. Direct events offer a number of advantages over audit log events. For more information, see [Event routes](https://docs.cloud.google.com/eventarc/standard/docs/run/event-routing-options.md.txt).

## Prepare to create a trigger

Before you create a trigger, complete these prerequisites:

### Console

1. In the Google Cloud console, on the project selector page, select or
   [create a Google Cloud project](https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects.md.txt).

   > [!NOTE]
   > **Note:** If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.


   [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)

   <br />

2. Enable the Cloud Logging, Eventarc, and
   Eventarc Publishing APIs.

   [Enable the APIs](https://console.cloud.google.com/apis/enableflow?apiid=eventarc.googleapis.com,eventarcpublishing.googleapis.com,logging.googleapis.com)
3. If applicable, enable the API related to the Cloud Audit Logs events.
   For example, for Cloud Run functions audit logs, enable the Cloud Functions API.

4. If you don't already have one, create a user-managed service account,
   then grant it the roles and permissions necessary so that
   Eventarc can manage events for your target service.

   1. In the Google Cloud console, go to the **Create service account**
      page.


      [Go to Create service account](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts/create?supportedpurview=project)

      <br />

   2. Select your project.

   3. In the **Service account name** field, enter a name. The Google Cloud console
      fills in the **Service account ID** field based on this name.

      In the **Service account description** field, enter a description. For
      example, `Service account for event trigger`.
   4. Click **Create and continue**.

   5. To provide appropriate access, in the **Select a role** list, select
      the required Identity and Access Management (IAM) roles to grant to your service
      account for authenticated or unauthenticated invocations. For more
      information, see
      [Roles and permissions for Cloud Run targets](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt).

      For additional roles, click
      **Add another role** and add each additional role.

      > [!IMPORTANT]
      > **Important:** To accept authenticated invocations to your Cloud Run service, you must associate your trigger with a service account that has the `roles/run.invoker` role. When creating or updating your trigger, select that service account.

   6. Click **Continue**.

   7. To finish creating the account, click **Done**.

### gcloud

1.


   In the Google Cloud console, activate Cloud Shell.

   [Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)


   At the bottom of the Google Cloud console, a
   [Cloud Shell](https://docs.cloud.google.com/shell/docs/how-cloud-shell-works.md.txt)
   session starts and displays a command-line prompt. Cloud Shell is a shell environment
   with the Google Cloud CLI
   already installed and with values already set for
   your current project. It can take a few seconds for the session to initialize.

   <br />

2. Enable the Cloud Logging, Eventarc, and
   Eventarc Publishing APIs.

   ```bash
   gcloud services enable logging.googleapis.com \
     eventarc.googleapis.com \
     eventarcpublishing.googleapis.com
   ```
3. If applicable, enable the API related to the Cloud Audit Logs events.
   For example, for Cloud Run functions audit logs, enable
   `cloudfunctions.googleapis.com`.

4. If you don't already have one, create a user-managed service account,
   then grant it the roles and permissions necessary so that
   Eventarc can manage events for your target service.

   1. Create the service account:

      ```bash
      gcloud iam service-accounts create SERVICE_ACCOUNT_NAME
      ```

      Replace `SERVICE_ACCOUNT_NAME` with the name of
      the service account. It must be between 6 and 30 characters, and can
      contain lowercase alphanumeric characters and dashes. After you create
      a service account, you cannot change its name.
   2. Grant the required Identity and Access Management (IAM) roles or permissions
      for authenticated or unauthenticated invocations. For more information,
      see
      [Roles and permissions for Cloud Run targets](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt).

   > [!IMPORTANT]
   > **Important:** To accept authenticated invocations to your Cloud Run service, you must associate your trigger with a service account that has the `roles/run.invoker` role. When creating or editing your trigger, use the `--service-account` flag to associate that service account with the trigger.

## Create a trigger

You can create an Eventarc trigger using the Google Cloud CLI
or through the Google Cloud console.


> [!NOTE]
> **Note:** Filtering is done through an exact match and does not support wildcards or regular expressions. However, you can use the `--event-filters-path-pattern` flag in the following gcloud CLI command, or define a path pattern through the console. For more information, see [Understand path patterns](https://docs.cloud.google.com/eventarc/docs/path-patterns.md.txt).

<br />

### Console

1. In the Google Cloud console, go to the Eventarc **Triggers** page.

   [Go to Triggers](https://console.cloud.google.com/eventarc/triggers)
2. Click **Create trigger**.
3. Type a **Trigger name** .

   This is the ID of the trigger and it must start with a letter. It can
   contain up to 63 lowercase letters, numbers, or hyphens.
4. For the **Trigger type** , select **Google sources**.
5. Select an **Event provider** .

   This is the Google service that is the source of events through its audit
   logs. For example, select **BigQuery**.

   Note that the event provider name used in the associated
   [Google Cloud documentation](https://docs.cloud.google.com/docs) might not have a prefix
   of *Cloud* or *Google Cloud* . For example, on the console,
   *Memorystore for Redis* is referred to as
   **Google Cloud Memorystore for Redis**.
6. In the **Event type** list, from the *via Cloud Audit Logs* events, select an event type.
7. Select one of the following:
   - **Any resource**---This is the default and includes dynamically created resources that have identifiers generated at creation time.
   - **Specific resource**---You must provide the full resource name.
   - **Path pattern** ---You can [filter for resources using a path pattern](https://docs.cloud.google.com/eventarc/docs/path-patterns.md.txt). For example, type `projects/_/buckets/eventarc-bucket/objects/random.txt` or type `projects/_/buckets/**/r*.txt`.
8. To specify the encoding of the event payload, in the **Event data
   content type** list, select **application/json** or **application/protobuf** .

   Note that an event payload formatted in JSON is larger than one formatted
   in Protobuf. This might impact reliability depending on your event
   destination and its limits on event size. For more information, see
   [Known issues](https://docs.cloud.google.com/eventarc/docs/issues.md.txt).
9. In the **Region** list, select a region.

   Cloud Audit Logs triggers for Eventarc are available in
   specific regions and in the global region, but are not available in
   dual-region and multi-region locations. To avoid any performance and data
   residency issues caused by a global trigger, Google recommends that the
   location match that of the Google Cloud service that is generating
   events. For more information, see
   [Eventarc locations](https://docs.cloud.google.com/eventarc/docs/locations.md.txt).

   If you specify the global location, you will receive events from all
   locations yielding matches for the event filters. For example, by creating a
   global Eventarc trigger, you can receive events from
   resources in the EU and US multi-regions.

   Note that there is a known issue with
   [Cloud Audit Logs
   triggers for Compute Engine](https://docs.cloud.google.com/eventarc/docs/reference/supported-events#compute-engine) that results in events originating from
   a single region: `us-central1`. This is regardless of where the
   virtual machine instance is actually located. When creating your trigger,
   set the trigger location to either `us-central1` or
   `global`.
10. Select the **Service account** that will invoke your service or workflow.

    Or, you can create a new service account.

    This specifies the Identity and Access Management (IAM) service account email
    associated with the trigger and to which you previously granted
    [specific roles](https://docs.cloud.google.com/eventarc/standard/docs/access-control.md.txt) required
    by Eventarc.
11. In the **Event destination** list, select **Cloud Run**.
12. Select a service.  

    This is the name of the service that receives the events for the trigger.
    The service must be in the same project as the trigger and will receive
    events as HTTP POST requests sent to its root URL path (`/`),
    whenever the event is generated.
13. Optionally, you can specify the **Service URL path** to send the incoming request to.

    This is the relative path on the destination service to which the events
    for the trigger should be sent. For example: `/`, `/route`,
    `route`, `route/subroute`.
14. Optionally, to specify a single delivery attempt with no retries, clear the **Enable retry on failure** checkbox; otherwise, the default behavior is retries if the delivery attempt fails. For more information, see [Retry events](https://docs.cloud.google.com/eventarc/docs/retry-events.md.txt).
15. Optionally, to add a label, you can click **Add label** . Labels are key-value pairs that help you organize your Google Cloud resources. For more information, see [What are labels?](https://docs.cloud.google.com/resource-manager/docs/labels-overview.md.txt#what-are-labels)
16. Click **Create**.
17. After a trigger is created, the event source filters can't be modified. Instead, create a new trigger and delete the old one. For more information, see [Manage triggers](https://docs.cloud.google.com/eventarc/docs/managing-triggers.md.txt).

### gcloud

You can create a trigger by running
[`gcloud eventarc triggers create`](https://docs.cloud.google.com/sdk/gcloud/reference/eventarc/triggers/create)
along with required and optional flags.

```bash
gcloud eventarc triggers create TRIGGER \
    --location=LOCATION \
    --destination-run-service=DESTINATION_RUN_SERVICE \
    --destination-run-region=DESTINATION_RUN_REGION \
    --event-filters="type=google.cloud.audit.log.v1.written" \
    --event-filters="serviceName=SERVICE_NAME" \
    --event-filters="methodName=METHOD_NAME" \
    --event-data-content-type="EVENT_DATA_CONTENT_TYPE" \
    --max-retry-attempts=1 \
    --service-account=SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com
```

Replace the following:

- `TRIGGER`: the ID of the trigger or a fully qualified identifier.
- `LOCATION`: the location of the Eventarc trigger. Alternatively, you can set the `eventarc/location` property; for example `gcloud config set eventarc/location us-central1`.

  Cloud Audit Logs triggers for Eventarc are available
  in specific regions and in the global region, but are not available in
  dual-region and multi-region locations. To avoid any performance and data
  residency issues caused by a global trigger, Google recommends that the
  location match that of the Google Cloud service that is generating
  events. For more information, see
  [Eventarc locations](https://docs.cloud.google.com/eventarc/docs/locations.md.txt).

  If you specify the global location, you will receive events from all
  locations yielding matches for the event filters. For example, by creating
  a global Eventarc trigger, you can receive events from
  resources in the EU and US multi-regions.

  Note that there is a known issue with
  [Cloud Audit Logs
  triggers for Compute Engine](https://docs.cloud.google.com/eventarc/docs/reference/supported-events#compute-engine) that results in events originating
  from a single region: `us-central1`. This is regardless of
  where the virtual machine instance is actually located. When creating your
  trigger, set the trigger location to either `us-central1` or
  `global`.
- `DESTINATION_RUN_SERVICE`: the name of the Cloud Run service that receives the events for the trigger. The service can be in any of the Cloud Run supported locations and doesn't need to be in the same location as the trigger. However, the service must be in the same project as the trigger and will receive events as HTTP POST requests sent to its root URL path (`/`), whenever the event is generated.
- `DESTINATION_RUN_REGION`: (optional) the [Cloud Run location](https://docs.cloud.google.com/run/docs/locations.md.txt) in which the destination Cloud Run service can be found. If not specified, it is assumed that the service is in the same region as the trigger.

<!-- -->

- `SERVICE_NAME`: the identifier of the Google Cloud service
- `METHOD_NAME`: the identifier of the operation

<!-- -->

- `EVENT_DATA_CONTENT_TYPE`: (optional) the [encoding of the event payload](https://docs.cloud.google.com/eventarc/standard/docs/overview.md.txt#event-format). This can be `application/json` or `application/protobuf`. The default encoding is `application/json`.

  Note that an event payload formatted in JSON is larger than one formatted
  in Protobuf. This might impact reliability depending on your event
  destination and its limits on event size. For more information, see
  [Known issues](https://docs.cloud.google.com/eventarc/docs/issues.md.txt).
- `SERVICE_ACCOUNT_NAME`: the name of your user-managed service account.
- `PROJECT_ID`: your Google Cloud project ID.

Notes:

- These flags are required:

  - `--event-filters="type=google.cloud.audit.log.v1.written"`
  - `--event-filters="serviceName=VALUE"`
  - `--event-filters="methodName=VALUE"`
- Optionally, filter events for a specific resource by using the
  `--event-filters="resourceName=VALUE"` flag and
  specifying the complete path to the resource. Omit the flag for
  dynamically created resources that have identifiers generated at creation
  time. Or, filter events for a set of resources by using the
  `--event-filters-path-pattern="resourceName=VALUE"`
  flag and specifying the [resource path pattern](https://docs.cloud.google.com/eventarc/docs/path-patterns.md.txt).

<!-- -->

- Each trigger can have multiple event filters, comma delimited in one `--event-filters`=\[`ATTRIBUTE`=`VALUE`,...\] flag, or you can repeat the flag to add more filters. Only events that match all the filters are sent to the destination. Wildcards and regular expressions are not supported.
- After a trigger is created, the event filter type can't be changed. For a different event type, you must create a new trigger.
- Optionally, to specify a single event delivery attempt with no retries, use the `--max-retry-attempts` flag. The only valid value is `1`. If you omit the flag, the standard retry behavior applies. For more information, see [Retry events](https://docs.cloud.google.com/eventarc/docs/retry-events.md.txt).
- The `--service-account` flag is used to specify the Identity and Access Management (IAM) service account email associated with the trigger.
- Optionally, to specify a relative path on the destination Cloud Run service to which the events for the trigger should be sent, use the `--destination-run-path` flag.

Example:

      gcloud eventarc triggers create helloworld-trigger \
          --location=us-central1 \
          --destination-run-service=helloworld-events \
          --destination-run-region=us-central1 \
          --event-filters="type=google.cloud.audit.log.v1.written" \
          --event-filters="serviceName=bigquery.googleapis.com" \
          --event-filters="methodName=google.cloud.bigquery.v2.JobService.InsertJob" \
          --service-account=${SERVICE_ACCOUNT_NAME}@${PROJECT_ID}.iam.gserviceaccount.com

This creates a trigger called `helloworld-trigger` for audit logs that are
written by `bigquery.googleapis.com` and for the operation identified as
`google.cloud.bigquery.v2.JobService.InsertJob`.

### Terraform


You can create a trigger for a Cloud Run destination using
Terraform. For details, see
[Create a trigger using Terraform](https://docs.cloud.google.com/eventarc/docs/creating-triggers-terraform.md.txt).

> [!NOTE]
> **Note:** Although your trigger is created immediately, it can take up to two minutes for a trigger to propagate and filter events.

## List a trigger

You can confirm the creation of a trigger by listing Eventarc
triggers using the Google Cloud CLI or through the Google Cloud console.

### Console

1. In the Google Cloud console, go to the Eventarc
   **Triggers** page.


   [Go to Triggers](https://console.cloud.google.com/eventarc/triggers)

   <br />

   This page lists your triggers in all locations, and includes details such
   as names, regions, event providers, destinations, and more.
2. To filter your triggers:

   1. Click **Filter** or the **Filter triggers** field.
   2. In the **Properties** list, select an option to filter the triggers by.

   You can select a single property or use the logical operator `OR` to add
   more properties.
3. To sort your triggers, beside any supported column heading, click
   **Sort**.

### gcloud

Run the following command to list your triggers:

```bash
gcloud eventarc triggers list --location=-
```

This command lists your triggers in all locations, and includes details such
as names, types, destinations, and statuses.

## What's next

- [Learn more about Eventarc](https://docs.cloud.google.com/eventarc/standard/docs/overview.md.txt).
- [Learn how to manage triggers](https://docs.cloud.google.com/eventarc/docs/managing-triggers.md.txt).