Stay organized with collections
Save and categorize content based on your preferences.
Google Agentspace provides Cloud Logging for
customers to monitor errors and warnings when importing documents or working
with data connectors.
This document describes how to access Cloud Logging for Google Agentspace
using Logs Explorer.
Before you begin
To access Cloud Logging, make sure that your project administrator has
granted you the Logs Viewer IAM role (roles/logging.viewer).
Access Google Agentspace logs using Logs Explorer
To access Google Agentspace logs, do the following:
In the Google Cloud console, go to the Logs Explorer.
Select a Google Cloud project to check its logs.
By default, the Logs Explorer page searches the resources listed in the
default log scope for log entries. To filter to
Google Agentspace logs, do one of the following:
Select All Resources > Consumed API > Discovery Engine API, and then
click Apply.
Enter the following into the query bar, and click
Run Query:
Further query the logs using the filters provided. For example,
change the time range.
By default, the Logs Explorer only shows logs from the past hour.
Refine your query scope by filtering on JSON metadata. For example,
to query ImportDocuments method logs, do one of the following:
For most warnings and errors, find details in jsonPayload.message and
jsonPayload.status.
For deeper log analysis, dump the logs to a long sink such as
BigQuery. For information, see
Route logs to supported destinations in the Google Cloud Observability documentation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[],[],null,["# View Google Agentspace logs with Cloud Logging\n\nGoogle Agentspace provides Cloud Logging for\ncustomers to monitor errors and warnings when importing documents or working\nwith data connectors.\n\nThis document describes how to access Cloud Logging for Google Agentspace\nusing Logs Explorer.\n\nBefore you begin\n----------------\n\nTo access Cloud Logging, make sure that your project administrator has\ngranted you the [Logs Viewer](/iam/docs/understanding-roles#logging.viewer) IAM role (`roles/logging.viewer`).\n\nAccess Google Agentspace logs using Logs Explorer\n-------------------------------------------------\n\nTo access Google Agentspace logs, do the following:\n\n1. In the Google Cloud console, go to the [Logs Explorer](https://console.cloud.google.com/logs/query).\n2. Select a Google Cloud project to check its logs.\n3. By default, the Logs Explorer page searches the resources listed in the\n default [log scope](/logging/docs/log-scope/create-and-manage) for log entries. To filter to\n Google Agentspace logs, do one of the following:\n\n - Select **All Resources \\\u003e Consumed API \\\u003e Discovery Engine API** , and then click **Apply**.\n - Enter the following into the query bar, and click\n **Run Query**:\n\n resource.type=\"consumed_api\"\n resource.labels.service=\"discoveryengine.googleapis.com\"\n\n4. Further query the logs using the filters provided. For example,\n change the time range.\n By default, the Logs Explorer only shows logs from the past hour.\n\n5. Refine your query scope by filtering on JSON metadata. For example,\n to query `ImportDocuments` method logs, do one of the following:\n\n - Enter the following into the query bar:\n\n jsonPayload.context.reportLocation.functionName=~\"ImportDocuments\"\n\n - Expand the JSON metadata, and click to filter:\n\n **Figure 1.** Filter by clicking on JSON metadata\n6. For most warnings and errors, find details in `jsonPayload.message` and\n `jsonPayload.status`.\n\n7. For deeper log analysis, dump the logs to a long sink such as\n BigQuery. For information, see\n [Route logs to supported destinations](/logging/docs/export/configure_export_v2) in the Google Cloud Observability documentation."]]