[pull] master from DataDog:master - #1127
Merged
Merged
Conversation
…#39589) * [WEB-9081] Move i18n to top-level shared directory for Hugo and Astro Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * TEMPORARY: pin cdocs-hugo-integration to branch build v4.4.4 to test shared i18n in CI Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Point cdocs-hugo-integration at the released v4.4.4 tarball on master Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Updating date-specific language since tomorrow is Sep 1!
* Add blog links to further_reading (week of 2026-08-25) * Remove blog links that did not clear the affinity bar Manual affinity pass over the 52 pairings in the PR description. Removes 26 entries where a more specific page is the better home, the post only mentions the product in passing, or the target page is already saturated with blog links. * Update hugo/content/en/database_monitoring/_index.md * Apply batched suggestions from code review Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Move Further reading section above reference link definitions --------- Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com> Co-authored-by: jeff.morgan <jeff.morgan@datadoghq.com>
* Add APM Edge Devices billing section Documents the APM Edge Devices billing option for Edge/IoT devices, including the Datadog Agent configuration required to run in APM Edge mode. * Note minimum Agent version 7.75.0 for APM Edge Devices --------- Co-authored-by: Duncan Hewett <8017759+duncanhewett@users.noreply.github.com>
Add the API/application key requirement, cluster name behavior (required before Datadog Operator v1.30.0, optional after), and a copyable Helm install snippet to the "Prerequisites for Kubernetes view" section. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
…ion version (#39623) * Clarify DD_LAMBDA_DURABLE_FUNCTION_LOG_BUFFER_SIZE defaults by extension version Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Reword v100+ default as "already 5" Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs(test_parallelization): reflect pytest --command support since 1.7.0 ddtest PR DataDog/ddtest#123 made PyTest.RunTests and DiscoverTests honor commandOverride (--command / DD_TEST_OPTIMIZATION_RUNNER_COMMAND) instead of hardcoding 'python -m pytest'. Update the configuration and best_practices pages to describe the override and retain PYTEST_ADDOPTS guidance for passing extra flags. * Replace "Since ..." with "For versions ... and later" Co-authored-by: Heston Hoffman <hestonhoffman@gmail.com> --------- Co-authored-by: Heston Hoffman <hestonhoffman@gmail.com>
* Add data handling and AI providers section to MCP Server docs * Apply suggestions from automated review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: webops-guacbot[bot] <214537265+webops-guacbot[bot]@users.noreply.github.com>
#38581) * Add Multi-Tenant Usage Metering and Billing partner docs (PSAOKR-5462) New section under content/en/partners/multi_tenant_billing/ covering the Admin Org: what it is and its capabilities (including preview features), requesting one, Trial Org provisioning, cost/usage visibility, and troubleshooting. * Specify Customer Contracts Management as a Plan & Usage tab * Replace capabilities table with a section-per-capability layout with screenshots * Rewrite partner docs to match Datadog documentation style Merge Overview/capability-list redundancy into concise, action-oriented sections modeled on cloud_cost_management/_index.md and plan_and_usage/_index.md. Replace ad-hoc HTML alert divs with the site's bold-prefixed Note/Important convention, use {{< ui >}} consistently for in-app element names, and tighten prose. * Rename Usage metrics roll-up to Centralized Usage Metrics, expand API endpoint list * Restructure landing page to match canonical Datadog doc pattern (Overview / Getting started / Use cases / Troubleshooting) * Note GovCloud visibility boundary for cost and usage data * Add Multi-Tenant Usage Metering and Billing section to partners left nav * Rephrase org-connection wording: third person, 'connects' instead of 'links' * Remove second-person 'you/your' throughout partner docs per style guide's overuse guidance * Thorough review pass against repo's Vale/style rules and PR-review checklist - Fix Vale violation: 'ensures' -> rephrase - Wrap remaining bold-only UI element names in {{< ui >}} for consistency (Trial Org Provisioning dashboard, Customer Pricing, Customer Contracts tabs) - Match heading/link-text capitalization to actual page titles (Cost and Usage Visibility, Trial Org Provisioning) per the title-consistency check - Remove orphaned further_reading front matter on cost-and-usage-visibility.md (never rendered - no whats-next partial call on that page - and duplicated its own inline reference links) * Fix grammar/style in Overview edit; add placeholder screenshot files Placeholder 1x1 PNGs at static/images/partners/multi_tenant_billing/ for each {{< img >}} reference in _index.md - replace with real screenshots before merging. * Add dedicated Centralized Usage Metrics page; mark capability GA - New content/en/partners/multi_tenant_billing/centralized-usage-metrics.md, based on the internal EUM/UM/Admin Org roll-up doc, filtered to what's partner-facing (drops internal Mosaic/consul-config flags, Slack channel, and C&A team ownership note - replaced with the standard partner-support@datadoghq.com contact for enabling UM roll-up) - No longer marked (Preview) - capability is GA - _index.md: shortened teaser section, added nav/whatsnext links to the new page, updated Use Cases table - cost-and-usage-visibility.md: removed now-duplicated Centralized Usage Metrics section, cross-links to the new page instead - Added the new page to config/_default/menus/partners.en.yaml * Drop EUM/UM abbreviations - not public terminology Datadog's own billing nav links to the 'Estimated Usage Metrics' page with the text 'Usage Metrics', treating 'estimated' as a plain descriptive word rather than a branded acronym pair. EUM/UM are internal-only shorthand. * Add real screenshots for Admin Org hierarchy and Trial Org Provisioning dashboard * Usage Metering API endpoint table, Trial Org homepage fix, real screenshots - List the 6 real Usage Metering API endpoints with links and the correct include_connected_accounts / filter[include_connected_accounts] flag per endpoint, on both _index.md and cost-and-usage-visibility.md - Correct Trial Org Provisioning: it's the Admin Org homepage, not a Dashboards-menu item (troubleshooting.md, trial-org-provisioning.md, _index.md) - Remove plan_and_usage_admin_org.png screenshot/reference - redundant with the linked Plan and Usage Experience for Partners page - Add real screenshots: admin_org_hierarchy, customer_contracts, customer_pricing, usage_metrics_rollup * Add Onboarding a New Customer guide; reduce _index.md redundancy - New customer-onboarding.md, based on the internal Customer Onboarding Process for Partner doc: register deal -> create Trial Org -> share Trial Org ID with the PSM. Corrects the source's outdated 'navigate to Dashboards' instruction and drops dated 'as of <date>' framing. - Wired into _index.md (Overview pointer, first whatsnext link) and the left nav (weight 5, ahead of Requesting an Admin Org). - Removed the three _index.md H3 sections that duplicated their own dedicated pages (Cost and Usage Visibility, Trial Org Provisioning, Centralized Usage Metrics) - those topics now live only in the Use Cases table + their dedicated page, matching how tracing/_index.md only keeps full sections for topics without a separate deep page. - Moved the Trial Org Provisioning and Centralized Usage Metrics screenshots onto their dedicated pages along with the removed sections. - trial-org-provisioning.md: removed the inaccurate 'PSM is notified automatically' claim, fixed a leftover step-numbering gap. - centralized-usage-metrics.md: dropped the tag descriptions to match the source's literal parent/child framing; removed the preview/enable section now that the capability is GA. * Correct Trial Org visibility claim; fix billing-access contradiction - Trial Org usage is not visible from the Admin Org until the customer org has an active contract tied to the partnership (confirmed) - fixed trial-org-provisioning.md and customer-onboarding.md, which both implied automatic rollup on Trial Org creation. - _index.md: fixed 'manage billing' contradicting the read-only-access alert two lines below - changed to 'view billing'. - Updated admin_org_hierarchy.png screenshot. * Qualify read-only access vs Preview capabilities; note Trial Org Creator in request - _index.md: clarify the read-only/no-billing-changes alert applies by default, and the Preview capabilities below add supported pricing and contract-management workflows (was a flat contradiction otherwise). - requesting-an-admin-org.md: note that partners planning to provision trials should include the Trial Org Creator capability in the initial request, since it's a separate opt-in capability, not bundled by default. * Clarify Customer Pricing Management: costs are based on partner-set pricing, not Datadog's own estimate * Reorder getting-started docs by workflow; simplify Use Cases table - whatsnext/nav order: Requesting an Admin Org -> Onboarding a New Customer -> Trial Org Provisioning -> Cost and Usage Visibility -> Centralized Usage Metrics -> Troubleshooting (get the org before using it). - Use Cases table: rename 'How an Admin Org helps' column to 'Capability', and name the capability directly ('[X]: does Y') instead of 'Use X to Y' in every row - matches the Name: description pattern already used in the whatsnext block. * Remove Requesting an Admin Org page; fold minimal content into _index.md - The page only had two real facts (prerequisites, contact) surrounded by internal-mechanics detail irrelevant to a partner (Partner Plan, separate contract, US1-site creation, read-only access already stated in the Getting started alert). Deleted it and folded the prerequisites + contact directly into _index.md's Getting started section. - Contact is now partner-support@datadoghq.com only, not 'or a PSM' - the PSM alternative wasn't the intended request path. - Updated all cross-references (customer-onboarding.md, cost-and-usage-visibility.md, centralized-usage-metrics.md) and the left nav to drop the removed page. - cost-and-usage-visibility.md: softened 'The same data is available programmatically' to 'Cost and usage data is also available...' - the API and UI aren't guaranteed to return identical data. * Broaden partner scope, generalize PSM references, close remaining review gaps - Broaden 'resell or MSP partner' to include systems integrator partners throughout (Overview + eligibility bullet). - Replace 'PSM'/'Partner Sales Manager' with 'partner account team', matching how other Datadog partner docs refer to this contact (partner-support@datadoghq.com / 'Datadog partner representative' are the established terms; naming a specific role isn't). - customer-onboarding.md: merge the trial-to-paid transition into the existing 'Share the Trial Org' section instead of a new redundant section - continue working with the partner account team through to a signed contract. - trial-org-provisioning.md: add a 'Find the Trial Org ID' fallback section (browser console / bookmarklet), adapted from the equivalent section in getting_started/laying-the-groundwork.md, for partners who didn't capture the org ID from the result panel. - cost-and-usage-visibility.md: state that a Trial Org's usage isn't included until its customer org is connected (previously only stated on other pages, not the page most likely to be checked for it), and that final invoices are the authoritative source for billed amounts, not the estimated/projected views shown here. * Rewrite Getting started paragraph as flowing prose, not a bolted-together checklist * Getting started: Solution Provider terminology, Register Now link, screenshot placement - Registration/eligibility now uses the official DPN terminology (Solution Provider) instead of the earlier guessed resell/MSP/SI enumeration. - Add a Register Now link (partners.datadoghq.com/s/login/) for partners not yet registered, before the partner-support contact instruction for already-registered partners. - Move the Partner Portal registration screenshot to sit right after the Register Now sentence instead of before it. - Trial Org Creator note reformatted as a proper Note callout. Full review pass against our style rules across all six pages: - Fixed redundant phrasing ('by Datadog' after 'Datadog partner', 'as early as possible, even at an early stage'). - Genericized the remaining 'Partner Solutions Architect (PSA)' reference to 'partner account team', matching the PSM fix. - Updated stale scope language now that Onboarding a New Customer covers the full path through contract signature, not just Trial Org creation - 'a live Trial Org' -> 'a connected customer organization' in _index.md (twice) and customer-onboarding.md's description/Overview, and the Overview's 'two steps' updated to the actual three-part flow. - Verified no Vale-flagged words, filler words, you/your, orphaned refs, or dangling links to the removed Requesting an Admin Org page across all six files. * Fix inconsistent note styling: move read-only-access alert to Overview, fold Trial Org Creator line into prose The two notes sat side-by-side in Getting started with mismatched styles (one HTML alert box, one plain bold text). Moved the read-only access alert to the Overview where it fits conceptually (describing what an Admin Org is/does), and folded the short Trial Org Creator sentence into the preceding paragraph instead of styling it as its own note. * Updated documentation. * Add dedicated Customer Pricing Management page - New content/en/partners/multi_tenant_billing/customer-pricing-management.md, based on the partner-facing FAQ, RevEng partner deck, and the customer- facing FAQ for this capability. Called Preview throughout, not MVP. - Confirms the underlying mechanism: partner-configured pricing powers the customer's own Bill Overview page (estimated month-to-date cost, daily breakdown, group by product/sub-org). - Documents real Preview limitations sourced from the customer-facing FAQ: legacy MSP contracts, double-reseller chains, GovCloud orgs, cloud marketplace customers without a drawdown agreement, no projected costs/cost by tag/CCM costs, and the ~3% variance on off-contract ingest SKUs. - _index.md: shortened the redundant teaser (matching the pattern for every other capability with its own page), moved the screenshot to the new page, fixed the Use Cases table link from an in-page anchor to the real page, and removed a duplicate read-only-access alert box left over from an earlier edit. - Added the new page to the left nav. * Clarify per-child-org pricing limitation; style fixes (e.g. -> for example, subject-verb agreement) * Updated diagram * Remove redundant Customer Pricing Management teaser section from _index.md Now that it has its own page, it only needs the Use Cases table row, matching the pattern for every other capability with a dedicated page. * Add dedicated Customer Contracts Management page; trim Getting started to onboarding path - New content/en/partners/multi_tenant_billing/customer-contracts-management.md, based on the Confluence capability description and the underlying Partner Portal PRD: resell vs. MSP contract models, confirmed feature set (customers/contracts, contract details, invoices, MSP rollup, renewal reminders, discount/margin visibility, drawdown tracking), and what's explicitly out of scope (sales opportunities view, org hierarchy view, partner API access). - Moved the real customer_contracts.png screenshot to the new page; added two placeholders (customer_contracts_details.png, customer_contracts_invoices.png) for the contract-detail and invoices views. - _index.md: removed the redundant teaser section (same pattern as every other capability with its own page), updated the Use Cases table link, repositioned the Preview-capabilities alert after the table. - Getting started whatsnext trimmed to the onboarding path only (Onboarding a New Customer, Trial Org Provisioning, Troubleshooting) - Cost and Usage Visibility and Centralized Usage Metrics are now discoverable only through the Use Cases table. - Added the new page to the left nav. * Sort Multi-Tenant Usage Metering and Billing sub-pages alphabetically in left nav * Review and fix direct edits: typos, Vale violations, restore lost framing, remove orphaned images customer-onboarding.md: fixed 'varios' typo, removed 'ensure' (Vale violation), 'their Admin org' -> 'the Admin Org', 'oversee' -> 'view' matching the read-only framing used elsewhere - then restored the 'these steps matter' intent that got lost in that fix, per feedback. Also fixed a 'once the' -> 'after the' Vale violation in the restore. troubleshooting.md: removed 'please' (banned filler word), added a missing comma, converted a plain-text email to the markdown link format used everywhere else in this file. Reverted the 'Trial Org Provisioner' heading back to 'Trial Org Provisioning' per decision to keep that naming consistent across the doc set (not migrating). customer-contracts-management.md: removed the two inline screenshot placeholders (intentional simplification) - deleted the now-orphaned placeholder image files. * Fix broken sentence in Centralized Usage Metrics overview Merged sentence fragments didn't parse as valid English, and 'Centralize' was missing the 'd' to match the page title. Rewrote to preserve the intent (Admin Org oversees rolled-up, tagged metrics across the book of business) as two clean sentences. * Add standard Preview callout banner to Customer Pricing/Contracts Management Matches the site-wide convention (e.g. deployment_gates/_index.md): a {{< callout >}} banner with a Request Access button, right after the front matter. Pointed at partner-support@datadoghq.com since there's no public product-preview signup form for these partner- specific capabilities. Removed the now-redundant 'contact support to join the preview' What's next sections on both pages. * Refine Customer Pricing Management process steps; drop Not yet included section customer-pricing-management.md: corrected the configuration steps against the real UI (extracted from the source doc's embedded screenshots) - the View dropdown, editing via Edit before entering prices, the % Price Adjustment bulk tool, and the two non-contracted- product toggles (Set Custom Price Adjustment, Cap ingest markup at Datadog list price) instead of the earlier guessed 'bill at list price or apply a markup' framing. customer-contracts-management.md: removed the 'Not yet included' section per feedback. * Remove broken callout banners and irrelevant contract-model background The {{< callout >}} Request Access button doesn't work for these partner-specific previews (no public product-preview signup exists for them) - dropped it from both pages, folding the preview status back into a plain Overview sentence. Also removed the 'Datadog works with partners under two contract models' background from Customer Contracts Management - irrelevant to a partner who already knows their own contract type, lifted from the PRD's context section rather than written for this audience. * Apply review feedback: restructure Getting Started, rename Trial Org Provisioner, fix nav labels Split the landing page's intro section into "Requesting an Admin Org" (eligibility, registration, what to include when requesting) and a separate "Getting started" pointer to the rest of the docs. Rename "Trial Org Creator" to "Trial Org Provisioner" to match the actual capability name. Add "(Preview)" to the Customer Pricing/Contracts Management titles and nav entries. Replace circular "What's next" links between Cost and Usage Visibility and Centralized Usage Metrics with non-sequential "Related pages" sections. Tighten redundant "book of business" phrasing and an overloaded sentence in Customer Contracts Management. Add a troubleshooting entry for partners not invited to a new Admin Org. * Merge Customer Contracts FAQ content, reorder nav logically, small copy fixes Pull the Customer Contracts Portal FAQ doc's key features, screenshots, and Q&A into customer-contracts-management.md: contract MRR/UMRR, influence status, drawdown depletion, overdue invoices, cost-visibility status per customer, and key contacts (CSM/AE/partner account team/billing contact), plus two new screenshots and an FAQ section. Reorder the section nav from alphabetical to the partner lifecycle (Onboarding -> Trial Org Provisioning -> Cost and Usage Visibility -> Centralized Usage Metrics -> Customer Pricing Management -> Customer Contracts Management -> Troubleshooting), matching the Use Cases table order in _index.md to the same sequence. Rename "What's next"/"Related pages" to "Related docs" on Cost and Usage Visibility and Onboarding a New Customer, since those sections list related material rather than a build sequence. Explain the 30-day grace period on Cost and Usage Visibility, and drop the "while Datadog validates them" clause from the Preview alert. * Merge master: relocate Multi-Tenant Usage Metering and Billing under hugo/ master moved the entire Hugo site (content/, static/, config/, etc.) under a new top-level hugo/ directory while this branch was open. The menu edit merges cleanly via git's rename detection; the new pages and images added by this branch don't exist upstream so git can't rename them automatically - move them by hand to their hugo/ equivalents: hugo/content/en/partners/multi_tenant_billing/, hugo/static/images/partners/multi_tenant_billing/. Also adds the pending app.datadoghq.com/billing/customer-contracts direct-link addition to Customer Contracts Management. * Move Customer Pricing/Contracts out of partners section Customer Pricing Management and Customer Contracts Management move out of the Preview capabilities in the multi-tenant billing partner section, into core product documentation under account_management/plan_and_usage/partner_experience/, alongside each other. Per agreement with the PM: Customer Pricing is authored separately in main docs (not yet merged, on rliu/end-customer-cost- visibility-docs); Customer Contracts moves here as customer_contracts.md, carrying over its images (renamed to match this directory's hyphenated convention) and content unchanged. Remove both from the multi_tenant_billing left nav and from the _index.md Use Cases table's own page links, pointing instead to the new account_management URLs. Add a left-nav entry for Customer Contracts nested under Partner Experience in main.en.yaml. * Rename Customer Contracts Management to Customer Contracts; fix sidebar nesting Drop "Management" and "(Preview)" from the page's title/name; the Preview status is now conveyed only via an alert-danger caution box at the top of the page (matching the pattern used on forwarding_audit_events.md), not in the name itself. _index.md's own "(Preview)" tag for Customer Contracts and the generic intro alert wording are unaffected by the title change, since the capability itself is still Preview. Fix the left-nav sidebar not showing Customer Contracts nested under Partner Experience: left-nav.html hides a level-3 item's children by default (d-none) unless its identifier is in a hardcoded whitelist. Add account_management_partner_experience to that whitelist. * Trigger CI re-run for detect_hugo_site_dir/DDCI Status * Fold Customer Contracts FAQ into page body; add Further Reading section Drop the "(Preview)" tag from Customer Pricing's row in the Use Cases table too, matching Customer Contracts - both capabilities remain Preview, just not labeled in the table. On the Customer Contracts page: fold the two FAQ entries into the page body directly (Admin Org requirement noted inline where it's first needed, Billing Read permission as a Note near the nav step) instead of a separate FAQ section. Replace the further_reading front matter (confirmed not rendered by this page's layout - the whats-next partial that reads it is only wired into a few unrelated templates) with a manual "Further Reading" section, matching the parent Partner Experience page's naming. * Update customer_contracts.md * Fix broken nav-step link in Customer Contracts, drop unlinkable direct URL Wrapping a markdown reference link inside {{< ui >}} broke rendering (printed a literal unresolved [3] instead of a link) - {{< ui >}} isn't meant to wrap link syntax, just plain UI label text, matching every other page in this doc set. Since the UI label itself can't cleanly be a hyperlink, drop the direct-URL link entirely rather than work around it, and remove the now-unused [3] reference. * Move Customer Contracts back under the partners section Revert the account_management/plan_and_usage/partner_experience relocation - Customer Pricing and Customer Contracts moving into core product docs will be handled together in a separate PR instead. Restore customer-contracts-management.md and its images under partners/multi_tenant_billing/, restore its partners.en.yaml nav entry, and drop the main.en.yaml entry and left-nav.html whitelist addition that were only needed for the account_management nesting. Content improvements made along the way are kept: the "Customer Contracts" title (no "Management"/"(Preview)" suffix), the Preview caution box, the FAQ folded into the page body, and the Related docs section. * Remove 'join a preview' contact note from Use Cases section * Update Partners Getting Started page: add Multi-Tenant Billing link, fix stale links, add missing Dash years - Link to the new Multi-Tenant Usage Metering and Billing section from the topics list. - Add Dash 2024, 2025, and 2026 to the Dash Conferences playlists block (each verified against the actual YouTube playlist/video before adding). - Replace the dead Twitter link/label with X (twitter.com/datadoghq 301-redirects to x.com/datadoghq). - Add the DataDog/dpn repo (partner sample applications) to the GitHub repositories block. Checked every other link on the page (GitHub repos, YouTube channel, blog, LinkedIn, Facebook, status pages, release notes, partner portal) - all resolve correctly, no further changes needed. * Update hugo/content/en/partners/multi_tenant_billing/trial-org-provisioning.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/customer-onboarding.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/_index.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/_index.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Update hugo/content/en/partners/multi_tenant_billing/_index.md Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Replaced to make GovCloud sites more generic for the restriction. * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Apply suggestion from @jeff-morgan-dd Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com> * Remove broken customer_pricing link The /account_management/plan_and_usage/partner_experience/customer_pricing/ page doesn't exist yet (being created separately in #39118). Dropping the link for now per review feedback rather than blocking this PR on that page landing first - kept the 'Customer Pricing' text, just no longer linked. * Apply Jeff's outstanding review suggestions Went back through all 31 review comments from @jeff-morgan-dd - most of the literal GitHub suggestion blocks hadn't actually been applied despite later cleanup commits addressing other feedback separately. Covers: - Generalize the GovCloud exception instead of naming only US1-FED (US2-FED exists too) - kept it fully generic per follow-up direction, no site names - Capitalize the text after the colon in table/list entries for consistency (Trial Org Provisioning, Cost and Usage Visibility, Centralized Usage Metrics, Customer Contracts rows in _index.md; Related docs lists in cost-and-usage-visibility.md and customer-onboarding.md; account_name/ child_org_name bullets and Key contacts bullet) - Add trailing periods to image alt text per docs4docs alt-text guidelines, across all six affected pages - 'Partner Admin Org' -> 'Partner Admin Organization' for first-mention consistency (centralized-usage-metrics.md, cost-and-usage-visibility.md) - Split the Estimated/Usage metrics bullets in centralized-usage-metrics.md into separate sentences instead of a dangling colon+comma splice - Comma after 'for example' in centralized-usage-metrics.md - alert-danger -> alert-info for the Customer Contracts Preview banner, matching the alert style used elsewhere in these docs - Reworded the Trial Org region-selection guidance in customer-onboarding.md --------- Co-authored-by: jeff-morgan-dd <jeff.morgan@datadoghq.com>
* Update navigation steps for iOS configuration * Update hugo/content/en/mobile/guide/configure-mobile-device-for-on-call.md Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com> * Apply suggestion --------- Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
) * Correct log-based metric stream filter query syntax guidance - Replace the claim that stream filter query syntax matches Log Explorer search - Note that the filter is evaluated against the ingest stream, not indexed logs - Document that full-text search is unsupported in log-based metric filters - Add a validation step and quoted-phrase workaround for empty metrics - Add log-based metric filters to the full-text search limitation banner * Drop unverified wildcard and escaped-space claim from metric filter guidance Testing showed wildcards combined with escaped spaces do generate metrics, contradicting the reported behavior. Keep the validation step and the quoted-phrase fallback. * Convert passive voice to active in log-based metric guidance * Incorporate janine-c's feedback
Removed OpenTelemetry from the list of destinations.
* Flag Evaluation Tester docs * Update content/en/feature_flags/concepts/evaluation_tester.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update content/en/feature_flags/concepts/evaluation_tester.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * add the new page to the side-nav menu * screenshots * Updated markup of UI text, fixed some incorrect UI instructions, added a mention of new feature on Targeting rules page, updated capitalization of feature, other minor tweaks for accuracy. * Adding some cross-links to attributes, rules, and environments pages --------- Co-authored-by: Dave Kaloian <davyd.kaloian@datadoghq.com> Co-authored-by: Dave Kaloian <40408449+hdgone@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Cara Reaume <cara.reaume@datadoghq.com> Co-authored-by: Cara Reaume <35357020+clreaume@users.noreply.github.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
17 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )