MCPInstall

dt-obs-gcp

by dynatraceDevOps & Cloud

GCP cloud resources including Compute Engine, GKE, Cloud Run, Pub/Sub, VPC networking, DNS, IAM, Secret Manager, and monitoring. Monitor GCP infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across projects and folders.

Installs
2K
Last 24h
+12
Trending rank
#7953
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-obs-gcp
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads dt-obs-gcp automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

GCP Cloud Infrastructure

Monitor and analyze GCP resources using Dynatrace Smartscape and DQL. Query GCP services, manage organizational hierarchy, audit security posture, and track resource ownership across your GCP infrastructure.

When to Use This Skill

Use this skill when the user needs to work with GCP resources in Dynatrace. Load the reference file for the task type:

TaskFile to load
Inventory and topology queries(no additional file — use core patterns above)
Compute Engine instances, machine types, IP addressesLoad references/compute-instances.md
GKE clusters, node pools, pods, deployments, services, RBACLoad references/kubernetes-gke.md
Cloud Run services, revisions, executionsLoad references/serverless-containers.md
VPC networks, subnets, routes, DNS recordsLoad references/networking-dns.md
Pub/Sub topicsLoad references/messaging-pubsub.md
IAM service accounts, roles, Secret ManagerLoad references/iam-security.md
Monitoring dashboards, logging, saved queriesLoad references/monitoring-logging.md
GCP projects, regions, organizational hierarchyLoad references/resource-management.md
Resource ownership, GCP labels, organizational structureLoad references/resource-ownership.md

Core Concepts

Entity Types

GCP resources use the GCP_* prefix and can be queried using the smartscapeNodes function. All GCP entities are automatically discovered and modeled in Dynatrace Smartscape.

Compute: GCP_COMPUTE_GOOGLEAPIS_COM_INSTANCE, GCP_COMPUTE_GOOGLEAPIS_COM_ADDRESS Networking: GCP_COMPUTE_GOOGLEAPIS_COM_NETWORK, GCP_COMPUTE_GOOGLEAPIS_COM_SUBNETWORK, GCP_COMPUTE_GOOGLEAPIS_COM_ROUTE, GCP_DNS_GOOGLEAPIS_COM_RESOURCERECORDSET Kubernetes (GKE): GCP_K8S_IO_POD, GCP_K8S_IO_NODE, GCP_K8S_IO_SERVICE, GCP_K8S_IO_SERVICEACCOUNT, GCP_K8S_IO_PERSISTENTVOLUMECLAIM, GCP_APPS_K8S_IO_DEPLOYMENT, GCP_APPS_K8S_IO_STATEFULSET, GCP_CONTAINER_GOOGLEAPIS_COM_NODEPOOL, GCP_RBAC_AUTHORIZATION_K8S_IO_CLUSTERROLEBINDING, GCP_RBAC_AUTHORIZATION_K8S_IO_ROLEBINDING Serverless: GCP_RUN_GOOGLEAPIS_COM_SERVICE, GCP_RUN_GOOGLEAPIS_COM_REVISION, GCP_RUN_GOOGLEAPIS_COM_EXECUTION IAM & Security: GCP_IAM_GOOGLEAPIS_COM_SERVICEACCOUNT, GCP_IAM_GOOGLEAPIS_COM_ROLE, GCP_SECRETMANAGER_GOOGLEAPIS_COM_SECRETVERSION Messaging: GCP_PUBSUB_GOOGLEAPIS_COM_TOPIC Monitoring: GCP_MONITORING_GOOGLEAPIS_COM_DASHBOARD, GCP_LOGGING_GOOGLEAPIS_COM_SAVEDQUERY Infrastructure: GCP_REGION

Common GCP Fields

All GCP entities include:

  • gcp.project.id — GCP project identifier
  • gcp.region — GCP region (e.g., us-central1)
  • gcp.zone — GCP zone (e.g., us-central1-a)
  • gcp.organization.id — GCP organization identifier
  • gcp.resource.name — Resource name
  • gcp.resource.type — Resource type identifier
  • gcp.asset.type — GCP asset type
  • gcp.object — JSON blob containing full resource configuration

GCP Organizational Hierarchy

GCP resources are organized in a hierarchy:

  • Organization — Top-level container (gcp.organization.id)
  • Folder — Logical grouping within an organization
  • Project — Resource container (gcp.project.id)
  • Region/Zone — Physical location (gcp.region, gcp.zone)

Entity Naming Convention

GCP entity types follow the pattern GCP_<SERVICE_API>_<RESOURCE>:

  • Service API maps to the Google API domain (e.g., compute.googleapis.com → COMPUTE_GOOGLEAPIS_COM)
  • Resource is the specific resource type (e.g., INSTANCE, NETWORK)

Examples:

  • GCP_COMPUTE_GOOGLEAPIS_COM_INSTANCE — Compute Engine VM
  • GCP_K8S_IO_POD — GKE pod
  • GCP_RUN_GOOGLEAPIS_COM_SERVICE — Cloud Run service

Query Patterns

All GCP queries build on four core patterns. Master these and adapt them to any entity type.

Pattern 1: Resource Discovery

List resources by type, filter by project/region/zone, summarize counts:

smartscapeNodes "GCP_COMPUTE_GOOGLEAPIS_COM_INSTANCE"
| fields name, gcp.project.id, gcp.region, gcp.zone, gcp.resource.name

To list all GCP resource types, replace with "GCP_*" and add | summarize count = count(), by: {type} | sort count desc. Add filters like | filter gcp.project.id == "<PROJECT_ID>" or | filter gcp.region == "<REGION>" to scope results.

Pattern 2: Configuration Parsing

Parse gcp.object JSON for detailed configuration fields:

smartscapeNodes "GCP_COMPUTE_GOOGLEAPIS_COM_INSTANCE"
| parse gcp.object, "JSON:gcpjson"
| fieldsAdd machineType = gcpjson[configuration][resource][machineType],
            status = gcpjson[configuration][resource][status]
| fields name, gcp.project.id, machineType, status

GCP configuration fields are nested under gcpjson[configuration][resource][...] for primary resource attributes and gcpjson[configuration][additionalAttributes][...] for extended properties.

Pattern 3: Relationship Traversal

Follow relationships between resources:

smartscapeNodes "GCP_COMPUTE_GOOGLEAPIS_COM_INSTANCE"
| traverse "*", "GCP_COMPUTE_GOOGLEAPIS_COM_SUBNETWORK"
| fields name, gcp.project.id

GCP entities use "*" as the relationship name in traversals because GCP entities do not have named relationship types. Use fieldsKeep to carry fields through traversals and dt.traverse.history[-N] to access ancestor fields.

Pattern 4: Label-Based Ownership

Group resources by GCP labels for ownership and organizational tracking:

smartscapeNodes "GCP_*"
| filter isNotNull(`tags:gcp_labels`)
| fields name, gcp.project.id, `tags:gcp_labels`

GCP labels are exposed via the tags:gcp_labels field and must be accessed using backtick syntax. Replace "GCP_*" with a specific type to scope to one service.

Reference Guide

Load reference files for detailed queries when the core patterns above need service-specific adaptation.

ReferenceWhen to loadKey content
compute-instances.mdCompute Engine VMs, machine types, IP addresses, disksInstance inventory, machine type distribution, status checks
kubernetes-gke.mdGKE clusters, node pools, pods, deployments, services, RBACCluster topology, workload distribution, RBAC bindings
serverless-containers.mdCloud Run services, revisions, executionsService inventory, revision tracking, execution analysis
networking-dns.mdVPC networks, subnets, routes, DNS recordsNetwork topology, subnet analysis, route tables, DNS record sets
messaging-pubsub.mdPub/Sub topicsTopic inventory, messaging topology
iam-security.mdIAM service accounts, roles, Secret ManagerService account audit, role analysis, secret version tracking
monitoring-logging.mdMonitoring dashboards, logging, saved queriesDashboard inventory, saved query analysis
resource-management.mdGCP projects, regions, organizational hierarchyProject inventory, region distribution, hierarchy mapping
resource-ownership.mdResource ownership, GCP labels, organizational structureLabel-based grouping, project-level summaries, chargeback

Best Practices

Configuration Parsing

  1. Always parse gcp.object with JSON parser: parse gcp.object, "JSON:gcpjson"
  2. Access primary resource attributes via gcpjson[configuration][resource][...]
  3. Access extended properties via gcpjson[configuration][additionalAttributes][...]
  4. Check for null values after parsing with isNotNull()

GCP Hierarchy

  1. Organization → Folder → Project → Region/Zone
  2. Use gcp.project.id as the primary scoping filter
  3. Use gcp.organization.id for cross-project queries
  4. Use gcp.region and gcp.zone for location-based analysis

Entity Naming

  1. Entity types follow the GCP_<SERVICE_API>_<RESOURCE> format
  2. Service API maps to the Google API domain with underscores replacing dots and hyphens
  3. Use specific entity types (avoid "GCP_*" wildcards when possible)

Labels

  1. GCP labels must be accessed via backtick syntax: `tags:gcp_labels`
  2. Use isNotNull(tags:gcp_labels) for label-based filtering
  3. Track label coverage with summarize operations

Relationship Traversal

  1. Use "*" as the relationship name — GCP entities do not have named relationship types
  2. Use fieldsKeep to maintain important fields through traversal
  3. Access traversal history with dt.traverse.history[-N]
  4. Complex topologies may require multiple traverse operations

Limitations and Notes

Smartscape Limitations

  • Smartscape data reflects the most recent scan; there may be a delay between GCP changes and Dynatrace visibility
  • Not all GCP services are represented as entity types
  • Some configuration fields may be null depending on resource setup
  • Resource discovery depends on GCP integration configuration

GCP-Specific Notes

  • GCP labels must be accessed via backtick syntax: `tags:gcp_labels`
  • GCP entities use "*" for relationship traversal (no named relationship types)
  • GCP object configuration requires parsing with parse gcp.object, "JSON:gcpjson"
  • Configuration fields nest under gcpjson[configuration][resource][...] (differs from AWS pattern)

General Tips

  • Filter early by project and region for better performance
  • Use isNotNull() and isNull() for graceful null handling
  • Combine project and region filters for large environments
  • Use countDistinct() for unique resource counts
  • Limit results with | limit N during exploration

FAQ

What does the dt-obs-gcp skill do?

GCP cloud resources including Compute Engine, GKE, Cloud Run, Pub/Sub, VPC networking, DNS, IAM, Secret Manager, and monitoring. Monitor GCP infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across projects and folders.

How do I install dt-obs-gcp?

Run npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-obs-gcp in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/dt-obs-gcp/ (personal) or .claude/skills/dt-obs-gcp/ (project).

Which AI agents can use dt-obs-gcp?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is dt-obs-gcp safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains dt-obs-gcp?

It is published by dynatrace in dynatrace/dynatrace-for-ai. It has 1,971 recorded installs.

More from dynatrace/dynatrace-for-ai

View all →

dt-dql-essentials

dynatrace/dynatrace-for-ai

Core DQL syntax, pitfalls, query patterns, and query optimization. Load to write, build, fix, or OPTIMIZE a DQL query — prevents syntax errors and makes queries faster, more efficient, and cheaper (less data scanned = lower query consumption/cost per run). Covers fetch commands, data models, field namespaces, time alignment, entity/smartscape patterns, metric discovery, and performance/cost optimization (filter early, bucket filters, short time ranges, field selection, sampling, cardinality). Trigger: "write/build/fix a DQL query", "DQL syntax", "query logs/spans/metrics", "create a timeseries", "optimize my DQL", "make my query faster/cheaper", "reduce DQL cost/consumption/scanned data", "keep DQL cost under control". Do NOT use to explain an existing query or answer product questions. For MONITORING a tenant's ACTUAL query consumption/billing (how much queries cost, who scanned most, cost trends) use dt-platform-costs — this tunes the query text, not billing data.

DevOps & Cloud2.8K installs

dt-app-dashboards

dynatrace/dynatrace-for-ai

Work with Dynatrace dashboards - create, modify, query, and analyze dashboard JSON including tiles, layouts, DQL queries, variables, and visualizations.

Data & Databases2.8K installs

dt-obs-logs

dynatrace/dynatrace-for-ai

Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product documentation questions, distributed tracing or span analysis (use dt-obs-tracing).

DevOps & Cloud2.7K installs

dt-obs-problems

dynatrace/dynatrace-for-ai

DAVIS problem analysis including root cause identification, impact assessment, and correlation with other telemetry. Use when querying or investigating detected problems. Trigger: "active problems", "root cause analysis", "problem impact", "affected users", "list problems", "P-12345 details", "recurring problems", "problem history", "problem trending", "blast radius", "which entity caused the problem", "problems affecting Kubernetes", "problems by service". Do NOT use for explaining existing queries, product documentation questions, generic log searching, distributed tracing, or host-level resource monitoring.

DevOps & Cloud2.7K installs

dt-app-notebooks

dynatrace/dynatrace-for-ai

Work with Dynatrace notebooks - create, modify, query, and analyze notebook JSON including sections, DQL queries, and visualizations.

2.7K installs

dt-obs-tracing

dynatrace/dynatrace-for-ai

Distributed traces, spans, service dependencies, and request flow analysis. Use when investigating span-level details, failures, performance bottlenecks, or trace correlation. Trigger: "trace analysis", "slow requests", "failed spans", "service dependencies", "distributed trace", "span details", "HTTP status codes in traces", "database query spans", "messaging spans", "gRPC calls", "Lambda cold starts", "trace ID lookup", "exception analysis", "correlate logs and traces", "request attributes". Do NOT use for explaining existing queries, product documentation or configuration questions, service-level RED metrics (use dt-obs-services), log searching (use dt-obs-logs), or problem analysis (use dt-obs-problems).

Backend & APIs2.6K installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs