Sadhbh a/gcp guide - WIP #25708
Sadhbh a/gcp guide - WIP #25708
Conversation
github-actions
bot
added
Architecture
Preview links (active after the
|
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
Co-authored-by: Ursula Chen <[email protected]>
There was a problem hiding this comment.
We'll be changing this later this week, may want an updated snapshot
|
|
||
| ### Limit metric collection filters | ||
|
|
||
| Limit the GCE/GKE instances and Cloud Run revisions that are pulled into Datadog by entering tags in the **Limit Metric Collection Filters** text boxes under the **General** tab of the Google Cloud Integration tile. |
There was a problem hiding this comment.
@sriramkraman per our recent Metric Collection configuration convo we may want to update this, also this has been moved to the Metric Collection tab
There was a problem hiding this comment.
This has been moved to the Metric Collection lets update the naming accordingly.
| Limit the GCE/GKE instances and Cloud Run revisions that are pulled into Datadog by entering tags in the **Limit Metric Collection Filters** text boxes under the **General** tab of the Google Cloud Integration tile. | |
| Limit the GCE/GKE instances and Cloud Run revisions that are pulled into Datadog by entering tags in the **Limit Metric Collection Filters** text boxes under the **Metric Collection** tab of the Google Cloud Integration tile. |
| 3) Review these Google Cloud Prerequisites: | ||
|
|
||
| {{% site-region region="us,us3,us5,eu,ap1" %}} | ||
| - If your organization restricts identities by domain, you must add Datadog's customer identity `C0147pk0i` as an allowed value in your policy. |
There was a problem hiding this comment.
nit: can we update these dashes to be bullets?
| {{% site-region region="us,us3,us5,eu,ap1" %}} | ||
| - If your organization restricts identities by domain, you must add Datadog's customer identity `C0147pk0i` as an allowed value in your policy. | ||
| {{% /site-region %}} | ||
| - Datadog does not support [scoping projects][42] that pull in metrics from multiple other projects. |
There was a problem hiding this comment.
This is not a "prerequisite". We should instead note it as a warning.
|
|
||
| For the most comprehensive level of monitoring in your Google Cloud environment, integrate Datadog with [Google Cloud][4] using [service account impersonation][5] at the organization or folder level. | ||
|
|
||
| After reviewing the above [Prerequisites][3], follow these step-by-step instructions to set up the Google Cloud integration: |
There was a problem hiding this comment.
Sorry do you mean this section or this sentence?
| - Compute Viewer | ||
| - Monitoring Viewer | ||
| - Cloud Asset Viewer | ||
| - Browser |
There was a problem hiding this comment.
Are you suggesting adding a justification for each role assignment for the customer, would that be better served in our general docs instead of this getting started guide that's meant to be a quick onboarding?
static/images/integrations/google_cloud_platform/gcp_resource_collection.png
Outdated
Show resolved
Hide resolved
static/images/integrations/google_cloud_platform/security_findings.png
Outdated
Show resolved
Hide resolved
static/images/integrations/google_cloud_platform/limit_metric_collection.mp4
Outdated
Show resolved
Hide resolved
Co-authored-by: Dan T <[email protected]>
There was a problem hiding this comment.
Hey @buraizu I've taken a pass at the getting started page. Thanks for being so patient to wait for my input. I will take another pass once you are done making the changes.
|
|
||
| ## Overview | ||
|
|
||
| Use this guide to maximize the value of the Google Cloud integration by setting it up at the Organization or Folder level with optimized configurations and permissions. |
There was a problem hiding this comment.
let's start with the why - so customers can get started monitoring their Google Cloud environment quickly.
|
|
||
| ## Overview | ||
|
|
||
| Use this guide to maximize the value of the Google Cloud integration by setting it up at the Organization or Folder level with optimized configurations and permissions. |
There was a problem hiding this comment.
consider rephrasing the "maximize the value" to something simple like "monitor your".
| ◆ The Google Cloud integration requires the below APIs to be enabled **for each of the projects** you want to monitor: | ||
|
|
There was a problem hiding this comment.
I see we are bolding "each of the projects" but I believe this can be done at the folder level? (or maybe org level too?)
| [Google Cloud Billing API][8] | ||
| : Enables accurate billing for API calls. | ||
|
|
There was a problem hiding this comment.
I don't believe this is accurate based on what I see in the API. Why do we actually require it?
There was a problem hiding this comment.
"Allows developers to manage billing for their Google Cloud Platform projects programmatically." - Are we requesting this for CCM?
| [Google Cloud Billing API][8] | ||
| : Enables accurate billing for API calls. | ||
|
|
||
| <div class="alert alert-info">You can confirm if these APIs are enabled by heading to <a href="https://console.cloud.google.com/apis/dashboard"><b>Enabled APIs & Services</a></b> under each project in your Google Cloud workspace.</div> |
There was a problem hiding this comment.
There's the "under each project" again that I think we should remove. Consider the user's predicament when they have 100s of projects.
| ## Resource changes collection | ||
|
|
||
| Resource changes collection allows you to monitor changes in your Google Cloud environment. You receive resource events in Datadog when Google's Cloud Asset Inventory detects changes in your cloud resources. These events are forwarded to Datadog through a Cloud Pub/Sub topic and subscription. | ||
|
|
||
| For detailed setup instructions, see the [resource changes collection section][18] of the Google Cloud integration documentation. | ||
|
|
||
| **Note**: The Google Cloud service account used by the integration needs the `pubsub.subscriptions.consume` permission for the Cloud Pub/Sub topic and subscription created for this purpose. |
There was a problem hiding this comment.
why are we including the notes here when we are hyperlinking to the setup instructions in the other page? Either embed both in collapsible boxes or leave out the notes also.
| ## Log collection | ||
|
|
||
| Use the [Pub/Sub to Datadog template][14] to batch and compresses your log events before forwarding them to Datadog through [Google Cloud Dataflow][15]. This is the most network-efficient way to forward your logs. |
There was a problem hiding this comment.
An opening sentence on "why" collecting logs is important and also a way to specify what type of logs (i.e non-Agent logs) should be collected this way is important for the customer's understanding.
| ## Google Cloud integrations | ||
|
|
||
| You can send monitoring data to Datadog from 35+ integrations for Google Cloud services. The [Integrations page][19] provides a full listing of the available integrations. Many of these integrations are installed by default when Datadog recognizes data being ingested in from your Google Cloud account. | ||
|
|
||
| See the blog links below for deep dives into monitoring many of the more popular services. |
There was a problem hiding this comment.
This is the most important section, let's add more details here to inform the customer how we help them get started quickly monitoring Google Cloud service.
If we have time, a single line summary for each of the integrations would be amazing -- I can help or please work with our PMM, Trammell, to help cover this section.
Tying an earlier comment - I'd like for this to be what the customer does when they wait 15 minutes for the metrics to start flowing.
| The Agent also supports a wide range of [integrations][34], enabling you to extend visibility into specific services and databases running on your hosts. | ||
|
|
||
| [Traces][35] collected through the Trace Agent enable comprehensive Application Performance Monitoring (APM), helping you understand end-to-end service performance. |
| Use the [Google Cloud Private Service Connect integration][201] to visualize connections, data transferred, and dropped packets through Private Service Connect. This gives you visibility into important metrics from your Private Service Connect connections, both for producers as well as consumers. | ||
| [Private Service Connect (PSC)][202] is a Google Cloud networking product that enables you to access [Google Cloud services][203], [third-party partner services][204], and company-owned applications directly from your Virtual Private Cloud (VPC). | ||
|
|
There was a problem hiding this comment.
Please link to the blog. I am fine if we prefer to keep this for all regions and mention in the note this is available only for US5/EU1 regions.
rationale: Customers sometimes care enough to migrate data centers (esp when just getting started)
What does this PR do? What is the motivation?
Merge instructions
Additional notes