[DOCS-13132] Clarify Google Cloud metric ingestion latency#36313
Open
[DOCS-13132] Clarify Google Cloud metric ingestion latency#36313
Conversation
Contributor
Preview links (active after the
|
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
1 participant
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.
What does this PR do? What is the motivation?
Fixes DOCS-13132
Clarifies the Google Cloud metric ingestion latency in two places to deflect "why am I waiting" support tickets analyzed under DOCS-13132. The existing "Metrics appear in Datadog approximately 15 minutes after setup" wording conflated initial-setup latency (time before the first metric arrives after configuring the integration) with steady-state latency (ongoing delay between Google Cloud emitting a metric and it appearing in Datadog).
Changes:
content/en/getting_started/integrations/google_cloud.md: distinguishes the ~15-minute initial-setup latency from the ~7-8-minute steady-state delay, with a reference link to the existing Cloud Metric Delay guide for the full breakdown.content/en/integrations/guide/gcp-metric-discrepancy.md: adds a new## Latencysection before## Further reading, covering the same two numbers plus a "wait at least 10-15 minutes before assuming a metric is missing" troubleshooting guard.The 7-8 minute number is sourced from the existing
cloud-metric-delayguide, which has been the canonical Datadog-wide cloud latency reference. This PR surfaces that data point in the GCP-specific docs where customers actually search.A companion change in
integrations-internal-coreapplies the same disambiguation to the integration tile page (google_cloud_platform/README.md); that PR will be opened after this one merges.Follow-up work tracked in DOCS-14214: log latency, billing latency, and backfill behavior across pipelines (SME-blocked).
Merge instructions
Merge readiness:
Additional notes