[reorg fix] Add guide for estimating and managing Feature Flags costs - #38889
Merged
Conversation
Adds a new guide covering how to estimate Feature Flags usage and costs before rollout, and concrete levers to manage and reduce costs after going live. Links the guide from the Feature Flags guides index.
Clarifies that the 10x multiplier applies to a server-side request's raw count, matching the precise definition in the new Monthly Flag Configuration Requests concepts page.
- Clarify that client applications/end users drive client-side usage and backend services drive server-side usage in the overview - Drop the RUM-backed qualifier from the client-side usage bullet - Remove the environments factor from the estimation section, since it implied environments themselves are billed rather than the running SDK instances deployed to them
jhgilbert
added
WORK IN PROGRESS
1 task
Contributor
|
🔗 Commit SHA: a4b069c | Docs | View more details | Give us feedback! |
Contributor
Preview links (active after the
|
janine-c
approved these changes
Aug 14, 2026
janine-c
left a comment
janine-c
left a comment
Collaborator
There was a problem hiding this comment.
This looks awesome! I have some really minor writing suggestions I noticed while reading through it. Take a look and publish whenever the checks are done! Otherwise, let us know if we can do anything else to help 🙂
Use bullet formatting in the overview, clarify the client-side estimate options, and replace colloquial "after you're live" wording with "after deployment". Co-authored-by: Cursor <cursoragent@cursor.com>
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
4 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.
🤖 Auto-generated fix for #38666.
@A-Rindone — the docs repo reorg created merge conflicts in your PR #38666. This is an auto-generated replacement with the file paths fixed; please use it instead of the original.
This PR replays the commits from #38666 with file paths translated to the post-reorg
hugo/layout. The original commits are preserved — same messages and authorship.The original PR (#38666) will be closed in favor of this one.
Next steps:
WORK IN PROGRESSlabel from this PR.Original PR description:
What does this PR do? What is the motivation?
Adds a new Feature Flags guide covering how to estimate usage and costs before rollout, and concrete levers to manage and reduce costs after going live. Links the guide from the Feature Flags guides index.
Merge readiness
For Datadog employees:
AI assistance
Drafted with Claude Code based on existing Feature Flags product documentation and internal technical references; reviewed and lint-checked (Vale) before submission.
Additional notes
This guide links to
/feature_flags/concepts/monthly_flag_configuration_requests/, which is being added in a separate, parallel PR.