Skip to content

Cloud Monitoring Time Series Requests

Builds valid Google Cloud Monitoring ListTimeSeries API requests and aggregation settings from metric details

Repository
google/skills
Stars
21,782
Licence
Apache-2.0
Files
3 files

What it does

Once installed, the agent can turn a Google Cloud Monitoring metric description and resource details into a correctly formatted ListTimeSeries request, including the filter expression, time interval, and aligner/reducer aggregation settings used to build charts. It follows rules for label prefixes, instance name versus numeric ID handling, and Ops Agent memory and disk state labels, and it asks for a Project ID rather than guessing one. It does not pick which metric to use; that is handled by a separate skill.

Great for

  • Engineers building dashboards or scripts that query Cloud Monitoring metrics via the REST API
  • SRE or cloud operators who need correctly structured filters and aggregations for a known metric type
  • Developers who want to avoid common filter syntax errors in Cloud Monitoring

Skip it if

  • Finding or choosing which metric to monitor; the SKILL.md says to use the cloud-monitoring-metric-selection skill instead, so this skill alone is insufficient for vague requests
  • Non-cloud users or anyone without a Google Cloud project, since the Project ID is mandatory and the output targets GCP resources
  • Production use without review: generated queries are not run against a live project in the files, so they should be validated before relying on them

Try asking

  • “Build a ListTimeSeries request for compute.googleapis.com/instance/cpu/utilization on my VM named instance-1 in project my-prod-project for the last 6 hours”
  • “Generate the aggregation block with perSeriesAligner and crossSeriesReducer to chart Cloud SQL database CPU per database”
  • “Write a filter expression for Ops Agent memory percent_used that excludes free memory”
  • “Format a JSON payload for a Monitoring API call to list BigQuery dataset metrics grouped by dataset_id”
Step-by-step guide: how to use Cloud Monitoring Time Series RequestsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the Apache-2.0 licence and an attribution note.

    cloud-monitoring-list-time-series-request.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip cloud-monitoring-list-time-series-request.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip cloud-monitoring-list-time-series-request.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Provide the exact metric.type, metricKind, valueType, and resource type up front so the agent can skip discovery steps
  • Always give the Project ID and resource identifiers explicitly; the skill forbids placeholders and will ask if they are missing
  • Review generated requests before running them against production projects, since the skill does not execute them itself

What's inside

  • references/attribution.md
  • references/basic_aggregations.md
  • SKILL.md

Redistributed unmodified from google/skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.