Add Multi-Tenant Usage Metering and Billing partner docs (PSAOKR-5462) #38581
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,68 @@ | ||
| --- | ||
| title: Multi-Tenant Usage Metering and Billing | ||
| description: "Centrally manage usage, costs, and billing for end customers through an Admin Org." | ||
| cascade: | ||
| algolia: | ||
| subcategory: 'Multi-Tenant Usage Metering and Billing' | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| As a Datadog Solution Provider, you can use a **Partner Admin Organization** (Admin Org) to view and monitor cost and usage across customer organizations, provision trial organizations, and view billing across the customer base. An Admin Org is separate from any customer organization and is owned by Datadog; partners are invited to it with a Partner Role. | ||
|
|
||
| <div class="alert alert-info">By default, an Admin Org grants read-only access to cost and usage data for connected customer organizations, and personal or internal Datadog usage on the Admin Org is not supported. The Preview capability below adds supported pricing workflows.</div> | ||
|
|
||
| A customer organization is connected to an Admin Org automatically when its Datadog contract includes the partnership and is active. After connecting, a customer's usage and cost data is visible from the Admin Org, across all Datadog sites (for example, AP1, EU1, US1, US3, US5), except US1-FED, which requires its own Admin Org for regulatory purposes. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| {{< img src="partners/multi_tenant_billing/admin_org_hierarchy.png" alt="An Admin Org connected to multiple customer organizations" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| See [Onboarding a New Customer][15] for how these pieces fit into the path from a registered deal to a connected customer organization. | ||
|
|
||
| ## Requesting an Admin Org | ||
|
|
||
| Before requesting an Admin Org, the partner must: | ||
|
|
||
| - Be registered with Datadog on the [Datadog Partner Portal][1]. | ||
| - Have signed the agreement to transact with Datadog as a Solution Provider. | ||
| - Be approved as a Datadog partner. | ||
|
|
||
| Partners not yet registered can [Register Now][17] on the Datadog Partner Portal. | ||
|
|
||
| {{< img src="partners/multi_tenant_billing/partner_portal_registration.png" alt="Datadog Partner Portal registration page" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| Registered partners can request an Admin Org by contacting [partner-support@datadoghq.com][16]. Include in the request whether the partner also needs the Trial Org Provisioner capability enabled, for self-serve trial organization creation. | ||
|
|
||
| ## Getting started | ||
|
|
||
| {{< whatsnext desc="To get started with an Admin Org, see the following documentation.">}} | ||
| {{< nextlink href="/partners/multi_tenant_billing/customer-onboarding">}}<u>Onboarding a New Customer</u>: Take a prospective customer from a registered deal to a connected customer organization.{{< /nextlink >}} | ||
| {{< nextlink href="/partners/multi_tenant_billing/trial-org-provisioning">}}<u>Trial Org Provisioning</u>: Provision trial organizations for prospective customers directly from an Admin Org.{{< /nextlink >}} | ||
| {{< nextlink href="/partners/multi_tenant_billing/troubleshooting">}}<u>Troubleshooting</u>: Resolve common issues with Admin Org and Trial Org provisioning.{{< /nextlink >}} | ||
| {{< /whatsnext >}} | ||
|
|
||
| ## Use cases | ||
|
|
||
| Here are some ways an Admin Org can help: | ||
|
|
||
| | Use case | Capability | | ||
| |---|---| | ||
| | Self-serve Trial Org creation for prospective customers. | [Trial Org Provisioning][3]: create Trial Orgs directly from an Admin Org. | | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| | Monitor cost and usage across all customers in one place. | [Cost and Usage Visibility][2]: view estimated, historical, and projected cost and billable usage data. | | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| | Track usage metrics across the book of business. | [Centralized Usage Metrics][8]: roll customer usage metrics up into an Admin Org. | | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| | Let customers see their estimated costs based on the partner's pricing. | [Customer Pricing][9]: configure per-customer pricing. | | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| | Manage the book of business in one place. | [Customer Contracts][10]: track customers, contracts, invoices, and renewals. | | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Troubleshooting | ||
|
|
||
| For help with common Admin Org and Trial Org issues, see [Troubleshooting][7]. | ||
|
|
||
| [1]: https://partners.datadoghq.com | ||
| [2]: /partners/multi_tenant_billing/cost-and-usage-visibility/ | ||
| [3]: /partners/multi_tenant_billing/trial-org-provisioning/ | ||
| [7]: /partners/multi_tenant_billing/troubleshooting/ | ||
| [8]: /partners/multi_tenant_billing/centralized-usage-metrics/ | ||
| [15]: /partners/multi_tenant_billing/customer-onboarding/ | ||
| [16]: mailto:partner-support@datadoghq.com | ||
| [17]: https://partners.datadoghq.com/s/login/ | ||
| [9]: /account_management/plan_and_usage/partner_experience/customer_pricing/ | ||
|
Contributor
There was a problem hiding this comment. This link doesn't currently go anywhere (404s) - is there another PR for this page? |
||
| [10]: /partners/multi_tenant_billing/customer-contracts-management/ | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| --- | ||
| title: Centralized Usage Metrics | ||
| description: "Monitor usage metrics across all connected customer organizations from an Admin Org." | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| Centralized Usage Metrics lets the Admin Org oversee usage and estimated usage metrics from every connected customer org. Metrics roll up to the Admin Org tagged by customer, so partners can filter and attribute usage across their entire book of business from a single set of dashboards, monitors, and alerts. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| Datadog produces two kinds of usage metrics: | ||
|
|
||
| - **Estimated usage metrics**: in the `datadog.estimated_usage.*` namespace, update within minutes and provide a near real-time view of usage. Estimated usage metrics can differ from billable usage by roughly 10-20% on average, with larger variance for low-usage organizations. See [Estimated Usage Metrics][1] for the full metrics reference. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| - **Usage metrics**: in the `datadog.usage.*` namespace, come from the same metering and billing pipeline that produces the bill, so they track Plan & Usage closely. Usage metrics are less immediate than estimated usage metrics, but accurate enough for billing conversations. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| Use estimated usage metrics to catch usage spikes early, and usage metrics to report numbers that reconcile with the bill. | ||
|
|
||
| ## Attribution tags | ||
|
|
||
| Rolled-up metrics carry two tags: | ||
|
|
||
| - `account_name`: the parent org name (the Admin Org). | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| - `child_org_name`: the child org name (the customer organization), relative to the parent. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Query usage metrics | ||
|
|
||
| When building a dashboard widget or monitor: | ||
|
|
||
| - For estimated usage metrics, select {{< ui >}}Metrics{{< /ui >}} as the source and use a `datadog.estimated_usage.*` metric. | ||
| - For usage metrics, select {{< ui >}}Usage{{< /ui >}} as the source and choose a usage type, for example Infra Hosts. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| | Product | Estimated usage metric | Usage metric | | ||
| |---|---|---| | ||
| | Infrastructure hosts | `datadog.estimated_usage.hosts` | `datadog.usage.infra.hosts` | | ||
| | APM hosts | `datadog.estimated_usage.apm_hosts` | `datadog.usage.apm.hosts` | | ||
| | Custom metrics | `datadog.estimated_usage.metrics.custom` | `datadog.usage.metrics.custom` | | ||
| | Indexed logs | `datadog.estimated_usage.logs.ingested_events` | `datadog.usage.logs.indexed_logs` | | ||
|
|
||
| Scope a query to one customer with `child_org_name`, or break out every customer with `by {child_org_name}`: | ||
|
|
||
| ``` | ||
| # Estimated usage metric (Metrics source) | ||
| sum:datadog.estimated_usage.hosts{*} by {child_org_name} | ||
|
|
||
| # Usage metric (Usage source) | ||
| sum:datadog.usage.infra.hosts{*} by {child_org_name} | ||
| ``` | ||
|
|
||
| {{< img src="partners/multi_tenant_billing/usage_metrics_rollup.png" alt="Dashboard querying usage metrics rolled up from customer orgs, filtered by child_org_name" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| To match Plan & Usage totals, use a 1-hour rollup for host-style products and graph in UTC, since Plan & Usage reports in UTC. | ||
|
|
||
| ## Related docs | ||
|
|
||
| - [Cost and Usage Visibility][2]: cost and billable usage data across connected customer orgs. | ||
|
|
||
| [1]: /account_management/billing/usage_metrics/ | ||
| [2]: /partners/multi_tenant_billing/cost-and-usage-visibility/ | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| --- | ||
| title: Cost and Usage Visibility | ||
| description: "Monitor cost and billable usage across all connected customer organizations from an Admin Org." | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| A customer organization connects to the Partner Admin Org (Admin Org) automatically when its contract includes the partnership and is active. After connecting, a customer's usage and cost data becomes visible from the Admin Org, across all Datadog sites the customer uses. The connection is removed automatically 30 days after the contract expires, giving the partner a grace period to retain visibility while the contract is being renewed. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| **Note**: A Trial Org's usage is not included here until its customer organization is connected this way; see [Trial Org Provisioning][4]. | ||
|
|
||
| ## View cost and usage data | ||
|
|
||
| Go to {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Usage & Cost{{< /ui >}} in the Admin Org to view estimated, historical, and projected cost and billable usage data across all connected customer organizations, grouped and filtered by customer, product, or account. See [Plan and Usage Experience for Partners][1] for details. | ||
|
|
||
| Cost and usage data is also available programmatically through the following [Usage Metering API][2] endpoints: | ||
|
|
||
| | API | What it's for | Note | | ||
| |---|---|---| | ||
| | [Get Estimated Cost Across Your Account][6] | Estimated cost for the current and previous month | Requires `include_connected_accounts=true` | | ||
| | [Get Historical Cost Across Your Account][7] | Historical cost for previous months | Requires `include_connected_accounts=true` | | ||
| | [Get Projected Cost Across Your Account][8] | Projected end-of-month cost for the current month | Requires `include_connected_accounts=true` | | ||
| | [Get Billable Usage Across Your Account][9] | Billable usage summaries | Requires `include_connected_accounts=true` | | ||
| | [Get Usage Across Your Account][10] | Usage summary data across the account | Requires `include_connected_accounts=true` | | ||
| | [Get Hourly Usage by Product Family][11] | Hourly usage broken down by product family | Requires `filter[include_connected_accounts]=true` | | ||
|
|
||
| ## Related docs | ||
|
|
||
| - [Centralized Usage Metrics][3]: usage metrics rolled up from every connected customer org. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| - [Trial Org Provisioning][4]: provision trial organizations for prospective customers. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| [1]: /account_management/plan_and_usage/partner_experience/ | ||
| [2]: /api/latest/usage-metering/ | ||
| [3]: /partners/multi_tenant_billing/centralized-usage-metrics/ | ||
| [4]: /partners/multi_tenant_billing/trial-org-provisioning/ | ||
| [6]: /api/latest/usage-metering/#get-estimated-cost-across-your-account | ||
| [7]: /api/latest/usage-metering/#get-historical-cost-across-your-account | ||
| [8]: /api/latest/usage-metering/#get-projected-cost-across-your-account | ||
| [9]: /api/latest/usage-metering/#get-billable-usage-across-your-account | ||
| [10]: /api/latest/usage-metering/#get-usage-across-your-account | ||
| [11]: /api/latest/usage-metering/#get-hourly-usage-by-product-family | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| --- | ||
| title: Customer Contracts | ||
| description: "Manage the partner's book of business - customers, contracts, and invoices - from an Admin Org." | ||
| --- | ||
|
|
||
| <div class="alert alert-danger"> | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| Customer Contracts is in Preview. | ||
| </div> | ||
|
|
||
| ## Overview | ||
|
|
||
| Customer Contracts gives a partner a single place to manage customers, contracts, and invoices for their book of business with Datadog. Partners can look up this information directly, instead of relying on the partner account team for routine lookups. | ||
|
|
||
| Go to {{< ui >}}Plan & Usage{{< /ui >}} > {{< ui >}}Customer Contracts{{< /ui >}} in the Admin Org; see [Requesting an Admin Org][2] if one isn't set up yet. | ||
|
|
||
| {{< img src="partners/multi_tenant_billing/customer_contracts.png" alt="Customer Contracts tab under Plan & Usage in an Admin Org, listing customers and contracts" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| **Note**: The Billing Read permission is required to view Customer Contracts. | ||
|
|
||
| ## What's included | ||
|
|
||
| - All customers connected to the Admin Org, and their current and historical contracts, with renewal reminders for contracts coming up for renewal or already past their renewal date. | ||
| - Contract MRR (CMRR), Usage MRR (UMRR), influence status, and contract start and end dates, along with rates per product and order form PDFs. | ||
| - For drawdown contracts, the remaining balance, projected overshoot, and projected depletion date compared to the contract end date. | ||
| - For MSP contracts, which customers belong to each contract. | ||
| - Discount and margin visibility per contract. | ||
| - Whether [Customer Pricing][1] is enabled for each customer, not yet configured, or needs an update after a contract change. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
| - Key contacts per customer: the Datadog CSM, the Datadog AE, the partner account team, and the billing contact receiving invoices. | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| {{< img src="partners/multi_tenant_billing/customer_contracts_detail.png" alt="Customer Contracts detail panel showing spend overview, drawdown depletion, contract info, and contacts for a customer" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| Invoices are listed per customer with issue and due dates, amount, and payment status, and roll up into overdue counts and totals on the main Customer Contracts page: | ||
|
|
||
| {{< img src="partners/multi_tenant_billing/customer_contracts_invoices.png" alt="Customer Contracts invoices tab listing invoice numbers, dates, amounts, and status for a customer" style="width:100%;" >}} | ||
|
lucarelli111 marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Related docs | ||
|
|
||
| - [Requesting an Admin Org][2] | ||
|
|
||
| [1]: /account_management/plan_and_usage/partner_experience/customer_pricing/ | ||
|
Contributor
There was a problem hiding this comment. Broken link - please verify availability of this page |
||
| [2]: /partners/multi_tenant_billing/#requesting-an-admin-org | ||
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.