> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/alerts/google-cloud-pub-sub.md).

# Google Cloud Pub/Sub

[Google Cloud Pub/Sub](https://cloud.google.com/pubsub/) is a durable, scalable event ingestion and delivery system. It provides asynchronous messaging that decouples senders from receivers, and enables highly available communication between independently written applications.

Prisma Cloud can send alerts to Google Cloud Pub/Sub [topics](https://cloud.google.com/pubsub/architecture), where a topic is a message feed.

## Configuring alert frequency

You can configure the rate at which alerts are emitted. This is a global setting that controls the spamminess of the alert service. Alerts received during the specified period are aggregated into a single alert. For each alert profile, an alert is sent as soon as the first matching event is received. All subsequent alerts are sent once per period.

1. Open Console, and go to **Manage > Alerts**.
2. In **General settings**, select the default frequency for all alerts.

   You can specify the following frequencies.

   * **10 Minutes**
   * **1 Hour**
   * **1 Day**.

## Sending alerts to Google Cloud Pub/Sub

Alert profiles specify which events should trigger the alert machinery, and to which channel alerts are sent. You can send alerts to any combination of channels by creating multiple alert profiles.

Alert profiles consist of two parts:

**(1) Alert settings — Who should get the alerts, and on what channel?** Configure Prisma Cloud to integrate with your messaging service and specify the people or places where alerts should be sent. For example, configure the email channel and specify a list of all the email addresses where alerts should be sent. Or for JIRA, configure the project where the issue should be created, along with the type of issue, priority, assignee, and so on.

**(2) Alert triggers — Which events should trigger an alert to be sent?** Specify which of the rules that make up your overall policy should trigger alerts.

<figure><img src="/files/Rp0HcW5zDnWOrhIDqSf4" alt="google cloud pub sub config"><figcaption></figcaption></figure>

If you use multi-factor authentication, you must create an exception or app-specific password to allow Console to authenticate to the service.

## Create new alert profile

Create a new alert profile.

**Prerequisite:** You’ve set up a Cloud Pub/Sub topic.

1. In **Manage > Alerts**, click **Add profile**.
2. Enter a name for your alert profile.
3. In **Provider**, select **GCP Pub/Sub**.

## Configure the channel

Configure the channel.

1. In **Credential**, click **Add new** or select an existing service account.

   Create a new xref:\~/authentication/credentials-store/gcp-credentials.adoc\[GCP credential] as needed.
2. Enter a Cloud Pub/Sub topic.
3. Click **Send Test Alert** to test the connection.

## Configure the triggers

1. In **Select triggers**, select the events that should trigger an alert to be sent.
2. To specify specific rules that should trigger an alert, deselect **All rules**, and then select any individual rules.

   <figure><img src="/files/xvwOg8oBZd4P88JgCZwY" alt="frag config triggers"><figcaption></figcaption></figure>
3. Click **Next**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/alerts/google-cloud-pub-sub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.