From gcloud-tools
Provides GCP observability best practices: structured JSON logging, query filters, metrics/logs/traces guidance, alert policies, and log cost optimization.
npx claudepluginhub fcakyon/claude-codex-settings --plugin gcloud-toolsThis skill uses the workspace's default tool permissions.
Use structured JSON logging for better queryability:
Handles GCP Cloud Monitoring alerts with step-by-step guidance, production-ready configurations, and best practices for monitoring systems and services.
Provides observability patterns for metrics, logging, tracing, alerting, dashboards, and infrastructure monitoring in production systems with Prometheus, Grafana, OpenTelemetry.
Provides patterns for observability strategies covering logs, metrics, traces, and signal correlation. Use when designing monitoring systems or implementing the three pillars.
Share bugs, ideas, or general feedback.
Use structured JSON logging for better queryability:
{
"severity": "ERROR",
"message": "Payment failed",
"httpRequest": { "requestMethod": "POST", "requestUrl": "/api/payment" },
"labels": { "user_id": "123", "transaction_id": "abc" },
"timestamp": "2025-01-15T10:30:00Z"
}
Use appropriate severity for filtering:
# By severity
severity >= WARNING
# By resource
resource.type="cloud_run_revision"
resource.labels.service_name="my-service"
# By time
timestamp >= "2025-01-15T00:00:00Z"
# By text content
textPayload =~ "error.*timeout"
# By JSON field
jsonPayload.user_id = "123"
# Combined
severity >= ERROR AND resource.labels.service_name="api"
# Regex matching
textPayload =~ "status=[45][0-9]{2}"
# Substring search
textPayload : "connection refused"
# Multiple values
severity = (ERROR OR CRITICAL)
Metrics: Aggregated numeric data over time
Logs: Detailed event records
Traces: Request flow across services
Error rate:
Latency:
Resource exhaustion:
# Exclude health checks
resource.type="cloud_run_revision" AND httpRequest.requestUrl="/health"
# Exclude debug logs in production
severity = DEBUG