feat(gcp): add Google Distributed Cloud Edge monitoring integration docs - #26006
Conversation
Documents the new gcp_edge_container DM-only, no-entity-synthesis integration (Machine and EdgeCluster hardware/health metrics), following the same pattern as the Google Cloud Service Mesh (Istio) integration page. Adds the nav entry and a permissions-table row confirming no additional IAM permissions are required. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Hi @sarvetiNr 👋 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. |
tejaswaroop-nr
added
content
|
Netlify build fork |
|
✅ Your PR has been mirrored to our repository as PR #26027. |
… Edge docs Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Netlify build fork |
|
✅ Your updates have been mirrored to our repository in PR #26027. |
3 participants
Give us some context
gcp_edge_containerintegration (Google Distributed Cloud Edge) — a Dimensional-Metrics-only, no-entity-synthesis GCP integration coveringMachineandEdgeClusterhardware/health metrics, following the same pattern used for the existing Google Cloud Service Mesh (Istio) integration page.newrelic-client-goPR #1501 andterraform-provider-newrelicPR #3245.Changes
gcp-integrations-list/google-distributed-cloud-edge-monitoring-integration.mdx— Features, Activate (WIF-only), Polling frequency (5 min / 1 min resolution, same as Istio), and a metrics table (29Machine+ 6EdgeClustermetrics, GA/BETA only). Metric names and thegcp.*naming convention were verified against Google's public Cloud Monitoring metrics reference and the polling service's metric-naming code, not guessed.src/nav/infrastructure.yml: added the nav entry under "GCP integrations list", next to the Istio entry.integrations-custom-roles.mdx: added a permissions-table row — verified from thegcp-polling-v2datasource mapping that this integration usesMONITORING_APIdiscovery only (same as Istio), so no additional IAM permissions beyond the baseline Viewer role are required.Testing notes
polling-intervals-gcp-integrations.mdxper explicit instruction (left as-is, matching an existing gap for the Istio integration).🤖 Generated with Claude Code