This document gives an overview of the debugging process to understand the usage of **APIs and Services** in the Google Cloud console and also their latency spike.

First, follow these steps to identify conversation IDs with high latency:

1. Open **[Google Cloud console](https://console.cloud.google.com)** and go to the **APIs \& Services**.
2. Click **Enabled APIs and Services**.
3. Go to **Metrics** and select the **API method** under **Methods**.

The latency traffic graph appears, labeled **Traffic by API method**.

![](https://docs.cloud.google.com/static/gemini-enterprise-cx/agent-assist/images/aa-troubleshoot-screenshot1.png)

Next, ensure that you enable audit logging.

1. Go to **Audit Logs**.
2. Check the options **Admin Read** , **Data Read** and **Data Write**.
3. Click **Save**.

![](https://docs.cloud.google.com/static/gemini-enterprise-cx/agent-assist/images/aa-troubleshoot-screenshot2.png)

Next, identify the conversation IDs with latency longer than a certain value in `Log analytics`. For example, in the following screenshot, you can see conversations longer than 10 seconds on a particular day.

1. Go to **Log analytics**.
2. Provide the time against **TIMESTAMP_DIFF**.

![](https://docs.cloud.google.com/static/gemini-enterprise-cx/agent-assist/images/aa-troubleshoot-screenshot4.png)

Alternatively, use the timestamp to identify specific conversations during a certain period in `Log explorer`.

1. Enter the name of the method in **protoPayload.methodName**.
2. Enter the time range in **Timestamp**.
3. View the results in **Log fields**.

![](https://docs.cloud.google.com/static/gemini-enterprise-cx/agent-assist/images/aa-troubleshoot-screenshot3.png)

You can access any Agent Assist APIs with Cloud Logging enabled by following all of the preceding steps.