Search and analyze Google Logging from Guild agents

Integrations · Google Logging

Guild agents list, tail, and write Google Cloud Logging entries, manage sinks, and create logs-based metrics on your team’s behalf. Guild stores the OAuth credential server-side and injects it into every request, so agent code never sees it. Every call passes through credential policies you define, and the full request history is available in audit logs.

Book a demo

See how teams govern agents that use Google Logging.

Start free

Connect Google Logging and scope your first agent.

What the Google Logging integration exposes

The tools cover log entries (list, tail, write, and copy), log buckets and views, sinks, exclusions, and logs-based metrics. Billing-account and folder scopes are included alongside project-level operations. Agents can also read CMEK and general settings and manage long-running operations tied to asynchronous bucket changes.

How it works

Open Credentials in Guild

Go to Access & setup > Credentials in Guild. The page lists services you can connect.

Authorize with Google

Click Google Logging and complete the OAuth flow with a Google account that has Logs Viewer permissions. Guild refreshes the token automatically.

Add tools to your agent

Import googleLoggingTools and spread it into your agent’s tools object. Use pick() with the google_logging_ prefix to include only the tools your agent needs.

Why Google Logging access needs governing

Google Cloud Logging holds operational data across projects, folders, billing accounts, and organizations. An agent with an unrestricted credential can list or write log entries, create or remove sinks, and update CMEK settings. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request reaches Google, limiting which operations each agent or workspace can run on which resources. Guild stores the OAuth token server-side and injects it only after the policy check passes. Agent code, prompts, and containers never see the credential. You can scope a credential to one workspace, one agent, or one team member using Guild’s credential scoping controls, so a shared Google account does not give every agent the same reach. Teams that need a full deny-by-default posture can delete the auto-created allow-all policy once scoped rules cover everything agents should reach.

About the Google Logging integration

The @guildai-services/guildai~google-logging package gives your agents access to Google Cloud Logging for ingesting, searching, and analyzing logs.

Authentication

Type: OAuth 2.0
Token management: Refreshed automatically

Setup

Open Credentials

Go to Credentials in Guild.

Connect Google Logging

Click Google Logging and authorize with a Google account that has Logs Viewer permissions.

Usage

import { googleLoggingTools } from "@guildai-services/guildai~google-logging"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  description: "An agent that searches and analyzes Google Cloud logs",
  tools: { ...googleLoggingTools },
})

Selecting specific tools

Tools are named with the google_logging_ prefix. Use pick() to include only what your agent needs.

import { googleLoggingTools } from "@guildai-services/guildai~google-logging"
import { llmAgent, pick } from "@guildai/agents-sdk"

export default llmAgent({
  description: "An agent that investigates log errors",
  tools: {
    ...pick(googleLoggingTools, [
      "google_logging_entries_list",
      "google_logging_entries_tail",
    ]),
  },
})

Tools

Tools in the latest published version of guildai~google-logging:

All 36 tools

Tool	What it does
`google_logging_billing_accounts_get_cmek_settings`	Gets the Logging CMEK settings for the given resource.
`google_logging_billing_accounts_get_settings`	Gets the settings for the given resource.
`google_logging_billing_accounts_locations_buckets_create`	Creates a log bucket that can be used to store log entries.
`google_logging_billing_accounts_locations_buckets_create_async`	Creates a log bucket asynchronously that can be used to store log entries.
`google_logging_billing_accounts_locations_buckets_list`	Lists log buckets.
`google_logging_billing_accounts_locations_buckets_undelete`	Undeletes a log bucket.
`google_logging_billing_accounts_locations_buckets_update_async`	Updates a log bucket asynchronously.
`google_logging_billing_accounts_locations_buckets_views_create`	Creates a view over log entries in a log bucket.
`google_logging_billing_accounts_locations_buckets_views_list`	Lists views on a log bucket.
`google_logging_billing_accounts_locations_operations_cancel`	Starts asynchronous cancellation on a long-running operation.
`google_logging_billing_accounts_locations_operations_list`	Lists operations that match the specified filter in the request.
`google_logging_billing_accounts_locations_recent_queries_list`	Lists the RecentQueries that were created by the user making the request.
`google_logging_billing_accounts_locations_saved_queries_create`	Creates a new SavedQuery for the user making the request.
`google_logging_billing_accounts_locations_saved_queries_list`	Lists the SavedQueries that were created by the user making the request.
`google_logging_billing_accounts_sinks_create`	Creates a sink that exports specified log entries to a destination.
`google_logging_billing_accounts_sinks_delete`	Deletes a sink.
`google_logging_billing_accounts_sinks_get`	Gets a sink.
`google_logging_billing_accounts_sinks_list`	Lists sinks.
`google_logging_billing_accounts_sinks_patch`	Updates a sink.
`google_logging_billing_accounts_sinks_update`	Updates a sink.
`google_logging_entries_copy`	Copies a set of log entries from a log bucket to a Cloud Storage bucket.
`google_logging_entries_list`	Lists log entries.
`google_logging_entries_tail`	Streaming read of log entries as they are received.
`google_logging_entries_write`	Writes log entries to Logging.
`google_logging_exclusions_create`	Creates a new exclusion in the _Default sink in a specified parent resource.
`google_logging_exclusions_list`	Lists all the exclusions on the _Default sink in a parent resource.
`google_logging_folders_update_settings`	Updates the settings for the given resource.
`google_logging_logs_delete`	Deletes all the log entries in a log for the global _Default Log Bucket.
`google_logging_logs_list`	Lists the logs in projects, organizations, folders, or billing accounts.
`google_logging_monitored_resource_descriptors_list`	Lists the descriptors for monitored resource types used by Logging.
`google_logging_organizations_update_cmek_settings`	Updates the Log Router CMEK settings for the given resource.
`google_logging_projects_metrics_create`	Creates a logs-based metric.
`google_logging_projects_metrics_delete`	Deletes a logs-based metric.
`google_logging_projects_metrics_get`	Gets a logs-based metric.
`google_logging_projects_metrics_list`	Lists logs-based metrics.
`google_logging_projects_metrics_update`	Creates or updates a logs-based metric.

Frequently asked questions

Can my agent tail log entries in real time?

Yes. The google_logging_entries_tail tool performs a streaming read of log entries as they are received, so an agent can monitor a live log stream.

Does Guild support webhook events from Google Logging?

No. The catalog entry for this integration lists no webhook events, so agents cannot be triggered by push notifications from Google Cloud Logging. Use polling with google_logging_entries_list or google_logging_entries_tail instead.

Can I limit an agent to read-only access to Google Logging?

Yes. Write a credential policy that denies write and delete operations, or restricts allowed HTTP methods to GET. Guild’s credential proxy enforces the policy before any request reaches Google, regardless of what the agent requests.

Can one Google credential serve all my workspaces?

Yes. A credential connected at the account scope serves every workspace the account owns by default. You can also scope a credential to a single workspace, a single member, or a single agent if different teams need different Google accounts.

Put a governed agent on Google Logging this week

Book a demo

See how teams govern agents that use Google Logging.

Start free

Connect Google Logging and scope your first agent.

Also runs on Guild: New Relic · Splunk Read: Docs: Credential policies · Credentials · Tools in agents

Overview

Code & CI/CD

Communication

Project management

Testing

Productivity

Monitoring & observability

Data

Customer support

Sales & finance

Recruiting

Search and analyze Google Logging from Guild agents

Book a demo

Start free

What the Google Logging integration exposes

How it works

Why Google Logging access needs governing

About the Google Logging integration

Authentication

Setup

Usage

Selecting specific tools

Tools

Frequently asked questions

Put a governed agent on Google Logging this week

Book a demo

Start free

Book a demo

Start free

​What the Google Logging integration exposes

​How it works

​Why Google Logging access needs governing

​About the Google Logging integration

​Authentication

​Setup

​Usage

​Selecting specific tools

​Tools

​Frequently asked questions

​Put a governed agent on Google Logging this week

Book a demo

Start free

​Related

What the Google Logging integration exposes

How it works

Why Google Logging access needs governing

About the Google Logging integration

Authentication

Setup

Usage

Selecting specific tools

Tools

Frequently asked questions

Put a governed agent on Google Logging this week

Related