BackendsExternal Backends
Google Cloud Logging
Query Google Cloud Logging directly from Sazabi without moving data.
Google Cloud Logging as an external backend is coming soon. You can currently use Google Cloud Logging as a data source to forward logs to Sazabi.
Overview
Google Cloud Logging is the default log aggregation service for Google Cloud Platform. With Sazabi's Google Cloud Logging backend, you can query your GCP logs directly from Chat without forwarding data to Sazabi's storage.
What you can query
When Google Cloud Logging is configured as a backend, Chat can access:
- Log entries: Query logs from any GCP project
- Log buckets: Access logs in Cloud Logging buckets
- Log-based metrics: Query metrics derived from log entries
Authentication
Sazabi authenticates with Google Cloud using:
- Service Account: A GCP service account with Logs Viewer permissions
- Workload Identity Federation: Recommended for production deployments
The service account requires the following IAM roles:
roles/logging.viewer- View logsroles/logging.privateLogViewer- View private logs (if applicable)
Google Cloud Logging as data source vs backend
Google Cloud Logging can be used as both a data source and a backend:
| Mode | Data flow | Use case |
|---|---|---|
| Data Source | GCP logs are forwarded to Sazabi | Fast queries, unified storage |
| Backend | Sazabi queries GCP directly | Keep data in GCP, no duplication |
Coming soon
This page will include:
- Step-by-step setup instructions
- Service account configuration
- Project and folder selection
- Troubleshooting common issues