Added callout to Metric Name Pricing Customers on Volume Management Page#37431
Open
ouracheal wants to merge 1 commit into
Open
Added callout to Metric Name Pricing Customers on Volume Management Page#37431ouracheal wants to merge 1 commit into
ouracheal wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
Contributor
|
OliviaShoup
requested changes
Jun 11, 2026
OliviaShoup
left a comment
OliviaShoup
left a comment
Contributor
There was a problem hiding this comment.
thanks for the PR! i'm suggesting to change this to a Note callout instead of a Caution callout. i changed the language to match our style guide, and i changed the formatting of the links (callouts are tricky. the formatting inside them are HTML instead of Markdown).
let me know if you have any questions!
|
|
||
| Cloud-based applications generate massive amounts of data, which can be overwhelming for your organization as it scales. Observability costs become a significant budget item but core observability teams lack visibility into what is truly valuable to each individual engineering team. Individual teams are less incentivized to be proactive in helping manage this growth because they have limited insights into the costs of the metrics and tags they're submitting. | ||
|
|
||
| <div class="alert alert-danger">For customers on the [Metric Name Pricing model][7], please refer to this [guide][8] to better optimize your metric usage.</div> |
Contributor
There was a problem hiding this comment.
Suggested change
| <div class="alert alert-danger">For customers on the [Metric Name Pricing model][7], please refer to this [guide][8] to better optimize your metric usage.</div> | |
| <div class="alert alert-info">For customers on the <a href="https://docs.datadoghq.com/account_management/billing/metric_name_pricing/">Metric Name Pricing model</a>, see the <a href="https://docs.datadoghq.com/metrics/guide/metric_name_pricing_experience/">guide</a> to optimize your metric usage.</div> |
Comment on lines
+129
to
+130
| [7]: https://docs.datadoghq.com/account_management/billing/metric_name_pricing/ | ||
| [8]: https://docs.datadoghq.com/metrics/guide/metric_name_pricing_experience/ No newline at end of file |
Contributor
There was a problem hiding this comment.
Suggested change
| [7]: https://docs.datadoghq.com/account_management/billing/metric_name_pricing/ | |
| [8]: https://docs.datadoghq.com/metrics/guide/metric_name_pricing_experience/ |
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
2 participants
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.
Please merge after approving! Thanks :)