[DOCS-12135] Update setup options #32078
Conversation
Preview links (active after the
|
|
|
||
| 1. In the [Google Cloud integration page][500], select **+ Add GCP Account**. | ||
| 2. Select **Terraform**. | ||
| 3. Under **Provide GCP Resources**, add any project and folder IDs to be monitored. |
There was a problem hiding this comment.
can we update project to project IDs
There was a problem hiding this comment.
Would omit you can see projects and folders that you have required access and permission for in the terraform flow; unlike the Quickstart option they won't see their folders or projects in the datadog UI
| 2. Click **Copy** in the setup script section. | ||
| 3. Click **Open Google Cloud Shell**. | ||
| 4. Paste the script into the shell prompt and run it. | ||
| **Note**: Datadog recommends running this script locally through the [gcloud CLI][201], as it may be faster. This requires having your Google Cloud credentials available locally, and the gcloud CLI installed on your machine. |
There was a problem hiding this comment.
Should we move this NOTE below step 2 before the customer opens up the Gcloud Shell
| 1. In the [Google Cloud integration page][200], select **+ Add GCP Account**. | ||
| 2. Click **Quick Start**. | ||
| 2. Click **Copy** in the setup script section. | ||
| 3. Click **Open Google Cloud Shell**. |
There was a problem hiding this comment.
Should we add a link here for the customer https://ssh.cloud.google.com/cloudshell
There was a problem hiding this comment.
Probably not critical, since a user would theoretically have the tile open---but it couldn't hurt, so I've added this in 74b574b
|
|
||
| 1. In the [Google Cloud integration page][200], select **+ Add GCP Account**. | ||
| 2. Click **Quick Start**. | ||
| 2. Click **Copy** in the setup script section. |
There was a problem hiding this comment.
Thanks for flagging!
| 6. Under **Provide Service Account Details**: | ||
| 1. Give the service account a name. | ||
| 2. Select the project to contain the service account. | ||
| 7. Optionally, configure **Metric Collection**. |
There was a problem hiding this comment.
nit: Kind of prefer moving the optionality to the end
| 7. Optionally, configure **Metric Collection**. | |
| 7. Configure **Metric Collection** [OPTIONAL] |
| 3. Choose whether to disable metric collection for specific Google Cloud services to help control Google Cloud Monitoring costs. | ||
| 4. Choose whether to filter metrics by tags for GCP resource types `Cloud Run Revision`, `VM Intance`, or `Cloud Function` to help control Datadog costs. | ||
| 7. Optionally, choose to disable **Resource Collection** (attributes and configuration information of the resources in your Google Cloud environment). | ||
| 8. Copy the provided **Terraform Code**. If confirmed, the script: |
There was a problem hiding this comment.
Think the second sentence here is off, not sure what we're trying to convey
There was a problem hiding this comment.
Not sure what specifically is off, these are the options displayed in the UI:
Did you mean something else?
What does this PR do? What is the motivation?
Update setup instructions with new options and structure.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes