gcp-observability

Google Cloud adapter for observability-core: the queries that produce the number.

v0.1.0Source ↗#gcp#observability#incident#logging#triage

Install

  1. 01Add the marketplace (once)

    /plugin marketplace add https://catylai.com/marketplace.json
  2. 02Install gcp-observability

    /plugin install gcp-observability@catylai

Install observability-core alongside this. The core writes every incident procedure against capabilities rather than products and ends by asking you to map those capabilities once per environment. This plugin is that mapping for Google Cloud, plus the commands. The judgement stays in the core — when to declare, how severity is read off measured impact, what ranks above what in a triage sweep. This layer only answers how do I get that number out of GCP.

Reach for it when production is degraded in a GCP project and you need to confirm impact fast, when severity is being argued about and nobody has produced a number, when you need to know what shipped in the last 24 hours across Cloud Build, Cloud Deploy and the audit logs, or when a Cloud Logging filter is returning nothing and you cannot tell whether the system is clean or the filter is wrong.

Prerequisite is an installed gcloud, authenticated against a project you can read — verify both before querying, because an expired credential and a genuinely quiet system return the same empty output. A read-only responder needs roles/logging.viewer, roles/monitoring.viewer and roles/errorreporting.viewer, plus roles/logging.privateLogViewer for Data Access audit logs.

Nothing here changes anything. Where an action is implied, the skill recommends it and stops.