[DO NOT MERGE]docs: restructure AlloyDB integration with WIF metrics and all 4 resource types#24377
Draft
sparsi17 wants to merge 2 commits into
Draft
[DO NOT MERGE]docs: restructure AlloyDB integration with WIF metrics and all 4 resource types#24377sparsi17 wants to merge 2 commits into
sparsi17 wants to merge 2 commits into
Conversation
|
Hi @sparsi17 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local. If you really require a preview url, reach out to one of the writers and they will generate one for you. |
…urce types - Add Workload Identity Federation section with dimensional Metric event queries for all 4 resources: cluster, instance, database, instance node - Entities table: GCPALLOYDBCLUSTER, GCPALLOYDBINSTANCE, GCPALLOYDBDATABASE, GCPALLOYDBINSTANCENODE - Key metrics — Cluster: 2 gcp.alloydb.cluster.* metrics - Key metrics — Instance: 13 gcp.alloydb.instance.* metrics - Key metrics — Database: 20 gcp.alloydb.database.postgresql.* metrics - Key metrics — Instance Node: 13 gcp.alloydb.node.* metrics - Dimensions table (project_id, cluster_id, instance_id, database, node_id, location, gcp.resource.type) - Update Activate integration section with WIF + service account links - Add coming-soon Callout for WIF/service-account auth paths - Service account section preserves GcpAlloydbClusterSample, GcpAlloydbInstanceSample, GcpAlloydbDatabaseSample with Unit column added Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
3fe5b83 to
b2770e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Metricevent queries for all 4 AlloyDB resource typesGCPALLOYDBCLUSTER/GCPALLOYDBINSTANCE/GCPALLOYDBDATABASE/GCPALLOYDBINSTANCENODEgcp.alloydb.cluster.*metricsgcp.alloydb.instance.*metricsgcp.alloydb.database.postgresql.*metrics (aggregate / perquery / pertag)gcp.alloydb.node.*metrics<Callout variant="tip">coming-soon box for WIF/service-account auth pathsGcpAlloydbClusterSample,GcpAlloydbInstanceSample, andGcpAlloydbDatabaseSamplesample-event tables (Unit column added for clarity)Test plan
#wif,#service-account,#polling,#activate)🤖 Generated with Claude Code