logging-monitoring
Skill4 starsChanged 4 months agoMITView on GitHub
Configure observability on GCP using Cloud Logging, Cloud Monitoring, Cloud Trace, and Cloud Profiler. Covers log sinks, log-based metrics, alerting policies, dashboards, and uptime checks. Owns the operational readiness evidence for gcp-ops. Use when the user mentions: logging setup, monitoring setup, alerting policy, dashboard GCP, error reporting, SLO monitoring. Use this to configure the observability resources themselves; use gcp-ops instead for SLO targets, runbooks and release gating.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JeremyMorgan/code-review-skillstheir own version, first seen Jun 3, 2026
- YepAPI/skillstheir own version, first seen Apr 12, 2026
- harrissohail6/claude-code-configtheir own version, first seen Dec 22, 2025
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- JeremyMorgan/code-review-skills★ 15same name
- YepAPI/skills★ 8same name
- harrissohail6/claude-code-config★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-architectSkill
- bigquerySkill
- cloud-runSkill
- cloud-storageSkill
- gcloud-guardrailsSkill
- gcp-architectSkill
- gcp-opsSkill
- gcp-project-contextSkill
- gcp-qaSkill
- gcp-securitySkill
- gkeSkill
- google-skills-catalogSkill
- iamSkill
- mcp-serversSkill
- networkingSkill
- solution-designerSkill
- terraform-gcpSkill
- vertex-aiSkill
- well-architectedSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 77
Exclusion filters reduce ingestion cost: Use log exclusions to drop high-volume, low-value logs (e.g.
- Very specific: line 79
Retention has a cost curve: Default retention is free to a point.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Logging + Monitoring
Full observability stack for GCP workloads: Cloud Logging, Cloud Monitoring, Cloud Trace, and Cloud Profiler.
Core Patterns
Create a log sink (export to BigQuery for long-term retention)
gcloud logging sinks create SINK_NAME \
bigquery.googleapis.com/projects/PROJECT_ID/datasets/DATASET \
--log-filter='resource.type="cloud_run_revision"' \
--project=PROJECT_IDCreate a log-based metric (count errors)
gcloud logging metrics create error-rate \
--description="Count of ERROR log entries" \
--log-filter='severity=ERROR' \
--project=PROJECT_IDCreate an alerting policy (notify on error spike)
# Best done via Terraform or Console for complex conditions
# CLI example for uptime check failure:
gcloud alpha monitoring policies create \
--policy-from-file=alerting-policy.json \
--project=PROJECT_IDUptime check
gcloud monitoring uptime create \
--display-name="Service Health Check" \
--resource-type=uptime-url \
--hostname=SERVICE_URL \
--path=/ \
--project=PROJECT_IDGolden Signal Queries (Cloud Logging)
# 5xx errors on Cloud Run
resource.type="cloud_run_revision"
severity=ERROR
# Latency > 2s (requires structured logging with latency field)
resource.type="cloud_run_revision"
httpRequest.latency>"2s"
# GKE OOMKilled events
resource.type="k8s_container"
jsonPayload.reason="OOMKilling"Safety Rules
- Log sinks can incur cost. Exporting logs to BigQuery, Cloud Storage, or Pub/Sub bills for storage and, in BigQuery's case, for queries over the exported data. Scope every sink with a tight
--log-filter— never exportseverity>=DEFAULT(i.e. everything) to a billable destination without intent. - Scope log filters narrowly. Broad filters (no
resource.type, noseverity) match high-volume logs and drive both ingestion and export cost. Always pinresource.typeand the minimumseverityyou need. - Exclusion filters reduce ingestion cost. Use log exclusions to drop high-volume, low-value logs (e.g. health-check 200s) before they are ingested and billed.
- Never log secrets. Application logs routed to Cloud Logging are readable by anyone with
roles/logging.viewer. Redact tokens, keys, and PII at the source; do not rely on downstream filtering. - Retention has a cost curve. Default retention is free to a point; extended retention on
_Default/custom buckets bills per GB. Set retention deliberately per bucket.
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

