e04ed9c211
CF: Deploy Dev Docs / deploy (push) Waiting to run
Sync Labels / build (push) Waiting to run
tests / unit tests (macos-latest) (push) Waiting to run
tests / unit tests (ubuntu-latest) (push) Waiting to run
tests / unit tests (windows-latest) (push) Waiting to run
3.0 KiB
3.0 KiB
title, type, linkTitle, weight, description, no_list
| title | type | linkTitle | weight | description | no_list |
|---|---|---|---|---|---|
| Cloud Logging Admin Source | docs | Source | 1 | The Cloud Logging Admin source enables tools to interact with the Cloud Logging API, allowing for the retrieval of log names, monitored resource types, and the querying of log data. | true |
About
The Cloud Logging Admin source provides a client to interact with the Google Cloud Logging API. This allows tools to list log names, monitored resource types, and query log entries.
Authentication can be handled in two ways:
- Application Default Credentials (ADC): By default, the source uses ADC to authenticate with the API.
- Client-side OAuth: If
useClientOAuthis set totrue, the source will expect an OAuth 2.0 access token to be provided by the client (e.g., a web browser) for each request.
Available Tools
{{< list-tools >}}
Example
Initialize a Cloud Logging Admin source that uses ADC:
kind: source
name: my-cloud-logging
type: cloud-logging-admin
project: my-project-id
Initialize a Cloud Logging Admin source that uses client-side OAuth:
kind: source
name: my-oauth-cloud-logging
type: cloud-logging-admin
project: my-project-id
useClientOAuth: true
Initialize a Cloud Logging Admin source that uses service account impersonation:
kind: source
name: my-impersonated-cloud-logging
type: cloud-logging-admin
project: my-project-id
impersonateServiceAccount: "my-service-account@my-project.iam.gserviceaccount.com"
Reference
| field | type | required | description |
|---|---|---|---|
| type | string | true | Must be "cloud-logging-admin". |
| project | string | true | ID of the GCP project. |
| useClientOAuth | boolean | false | If true, the source will use client-side OAuth for authorization. Otherwise, it will use Application Default Credentials. Defaults to false. Cannot be used with impersonateServiceAccount. |
| impersonateServiceAccount | string | false | The service account to impersonate for API calls. Cannot be used with useClientOAuth. |