GCP Logging
Query, search, and analyze log entries across Google Cloud resources
The GCP Logging integration lets your agents search and filter log entries using the Cloud Logging query language, list available logs, and enumerate monitored resource types — against a specific Google Cloud project.
Prerequisites
- A Google Cloud project with Cloud Logging enabled (it is by default on any GCP project).
- A Project ID from the Google Cloud Console.
- Credentials. Either:
- A service account key (JSON) — create it under IAM & Admin → Service Accounts → Keys and grant the Logging Viewer role.
- Or grant the Fruxon-managed service account
gcp-logs-integration-reader@fruxon.iam.gserviceaccount.comthe Logging Viewer role on your project, then select the "Grant Fruxon Service Account Access" auth method — no key handling required on your side.
Setup
- Open your agent in Agent Studio.
- In the Integrations panel, click Add Integration Config.
- Select GCP Logging from the integration list.
- Give the config a display name (e.g., "GCP Logging — Prod project").
- Enter the Project ID.
- Pick the auth method: paste a service account key, or select the Fruxon service account path.
- Save the agent revision.
Using in Your Agent
- In an Agent Step, attach GCP Logging tools from the tools panel.
- Tools are referenced as
gcp_logging.list_log_entries,gcp_logging.list_logs,gcp_logging.list_monitored_resources.
list_log_entries takes Cloud Logging query language — e.g., severity>=ERROR AND resource.type="cloud_run_revision" — so the agent should know the syntax or be prompted with examples.
Available Tools
| Tool | Description | Action Type |
|---|---|---|
list_log_entries | Search and filter log entries using the Cloud Logging query language | ReadOnly |
list_logs | List the names of all logs available in the project | ReadOnly |
list_monitored_resources | List monitored resource descriptors (e.g., gce_instance, cloud_run_revision, gke_container) | ReadOnly |