[DOCS-15368] Update cost monitor types in Cloud Cost Management overview - #39306
Draft
maxvp wants to merge 3 commits into
Draft
[DOCS-15368] Update cost monitor types in Cloud Cost Management overview#39306maxvp wants to merge 3 commits into
maxvp wants to merge 3 commits into
Conversation
- List all five monitor types (Cost Changes, Cost Anomalies, Cost Threshold, Cost Forecast, Budget) instead of the outdated two - Link to the full monitor types page for details - Flag the monitor creation screenshot for recapture (still shows only two types)
Tag Explorer moved from Cloud Cost > Settings to Cloud Cost > Analyze > Tags.
This reverts commit 95c2151.
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?
Addresses DOCS-15368
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code for diagnosis, drafting, and editorial review.
Additional notes