diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 1f71f106..5d0f18bc 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -86,14 +86,16 @@ If your usage exceeds your contracted amount, MuleSoft sends a monthly overage i == Viewing Usage and Billing -Mule Credits usage, monthly statements, and overage billing are centralized in Salesforce Digital Wallet. If you have an Anypoint Platform organization, you can also view your usage and entitlement details in Anypoint Usage Reports for cross-platform transparency. +Mule Credits usage is available in both Anypoint Usage Reports and Salesforce Digital Wallet. Salesforce Digital Wallet remains the billing source of truth for finalized Mule Credits totals, statements, and overage outcomes. Anypoint Usage Reports provide granular visibility into consumption by usage type, business group, and application. -To view your Mule Credits consumption: +Use both views together for a complete view of Mule Credits consumption. Digital Wallet shows finalized totals and trends. Anypoint Usage Reports show consumption details by usage type, business group, and application. Values can differ between these views. -. From the *App Launcher*, click *Digital Wallet*. -. Locate the *Mule Credits* consumption card in the *Consumption Cards* tab. +Use Anypoint Usage Reports to investigate consumption spikes, identify which business groups and applications are driving usage, and support internal forecasting or cost allocation workflows. -Digital Wallet is available in Lightning Experience in Enterprise and Unlimited editions, and requires the View Consumption user permission. +=== When to Use Each View + +* Use *Anypoint Usage Reports* to analyze what is driving consumption across usage types, business groups, and applications. +* Use *Salesforce Digital Wallet* to review finalized daily and monthly consumption and billing outcomes. === Digital Wallet Features at a Glance diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index af4d96e8..ac847304 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -4,11 +4,15 @@ Anypoint Platform captures usage metrics across products, but not all metrics are billable or reflected in usage reports. +== Usage Type Description + +These table defines usage metrics by product and explains how each metric is calculated for reporting. + [cols=3*] |=== |Product |Metric Description |Usage Details -.8+|Mule Runtime +.8+|Mule Runtime |Mule flow: Flow within a deployed and running Mule app that contains a Mule event source or route APIKit request |Flows are aggregated using a Max Concurrent model. The usage for a month is the highest number of flows that exist in a single given hour during a month. @@ -20,20 +24,19 @@ Anypoint Platform captures usage metrics across products, but not all metrics ar |Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in production environments. |vCore Usage in Preproduction: Virtual processing capacity allocated to run Mule applications and APIs in non-production environments, such as sandbox, QA, staging, and development |Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in non-production environments. -| Cluster capacity: A set of workers or nodes that act as a single deployment target for a given Runtime Fabric instance -| Allocatable CPU capacity of each node within the Runtime Fabric instance. -| CPU Limit (Millicores): Maximum amount of CPU resources a worker node in Runtime Fabric can use +|Cluster capacity: A set of workers or nodes that act as a single deployment target for a given Runtime Fabric instance +|Allocatable CPU capacity of each node within the Runtime Fabric instance. +|CPU Limit (Millicores): Maximum amount of CPU resources a worker node in Runtime Fabric can use a| The amount of CPU usage is aggregated over a specific period of time, such as an hour or a day. The CPU limit configuration of each application is summarized at each environment ID, then at each business group, and then at the root organization ID for preproduction (sandbox) and production environment types separately. -| CPU Reserve (Millicores): A guaranteed minimum amount of CPU resources allocated to a worker node in the Runtime Fabric instance -| CPU reserve is aggregated by calculating the total amount of CPU resources allocated by the user to reserve for applications within the cluster or Runtime Fabric instance. +|CPU Reserve (Millicores): A guaranteed minimum amount of CPU resources allocated to a worker node in the Runtime Fabric instance +|CPU reserve is aggregated by calculating the total amount of CPU resources allocated by the user to reserve for applications within the cluster or Runtime Fabric instance. |API Manager |API instances: API instances in production, preproduction, and unclassified APIs (not associated with an environment) that are managed by API Manager after they are created using add, promote, or import options. a|API instances remain under management until they are deleted. Instances of API Manager are aggregated using a Max Concurrent model with three separate metrics for production, preproduction, and unclassified (APIs that aren't associated with an environment). -+ [NOTE] Data for API Manager is available starting in October 2024. @@ -46,21 +49,21 @@ a|If an API is governed, all versions of that API are considered one governed AP |Omni Gateway requests are aggregated as a total of all requests during a month. .3+|LLM Proxy -| Prompt tokens: Number of tokens an LLM Proxy in the prompts an LLM Proxy sends to a specific LLM Model -| These tokens are the sum of all prompt tokens a specific LLM Proxy sends to a specific LLM Model during a month. A prompt sent to an LLM Proxy are considered an Omni Gateway API call and count towards the Omni Gateway API call metric. +|Prompt tokens: Number of tokens an LLM Proxy in the prompts an LLM Proxy sends to a specific LLM Model +|These tokens are the sum of all prompt tokens a specific LLM Proxy sends to a specific LLM Model during a month. A prompt sent to an LLM Proxy are considered an Omni Gateway API call and count towards the Omni Gateway API call metric. -| Completion tokens: Number of tokens in the responses that an LLM Proxy receives from a specific LLM Model +|Completion tokens: Number of tokens in the responses that an LLM Proxy receives from a specific LLM Model |These tokens are the sum of all response tokens a specific LLM Proxy receives from a specific LLM Model during a month. -| Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model -| Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. +|Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model +|Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. -|Composer -|Composer task: Any action executed on a Composer connector, including but not limited to read, create, update, and delete +|Composer +|Composer task: Any action executed on a Composer connector, including but not limited to read, create, update, and delete |Composer tasks are aggregated as a total of all actions during a month. -|RPA -|Robotic Process Automation (“RPA”) bot minutes: The number of minutes running process automations across all bot sessions +|RPA +|Robotic Process Automation (RPA) bot minutes: The number of minutes running process automations across all bot sessions |A single bot can run multiple parallel sessions, with RPA bot minutes counting for each parallel session. You can configure multiple bots to run the same process, with RPA bot minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA bot minutes. |Anypoint MQ @@ -77,9 +80,9 @@ Anypoint MQ API requests are available via API and aggregated on usage reports. |DataGraph orchestration: An API request made by Anypoint DataGraph to the source APIs to get data for the GraphQL API request made to Anypoint DataGraph |Orchestrations are not currently aggregated on usage reports. -| Intelligent Document Processing (IDP) -| Intelligent Document Processing (IDP) Document Pages: A single page processed by IDP -| IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. +|Intelligent Document Processing (IDP) +|Intelligent Document Processing (IDP) Document Pages: A single page processed by IDP +|IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. |=== == Anypoint MQ Usage diff --git a/modules/ROOT/pages/usage-reports.adoc b/modules/ROOT/pages/usage-reports.adoc index ef5144c0..6dc42912 100644 --- a/modules/ROOT/pages/usage-reports.adoc +++ b/modules/ROOT/pages/usage-reports.adoc @@ -101,6 +101,19 @@ Use the Anypoint Usage API to programmatically access usage data. The API provid To use the API, see the API documentation for the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a/usage-api/[Anypoint Usage API] for access and implementation details. Users must have Usage Viewer permission to access the Usage API. +For a summary of pricing models and where to review usage and billing context for each model, see xref:usage-metrics.adoc[]. + +[[granular-mule-credits-visibility]] +== Granular Mule Credits Visibility + +Anypoint Usage Reports provide operational drill-down visibility for Mule Credits-related consumption. + +[NOTE] +==== +Use Salesforce Digital Wallet for finalized, billing-relevant Mule Credits totals and statements. +==== + +For detailed Mule Credits usage guidance and billing context, see xref:mule-credits-usage-and-rates.adoc[]. [[usage-reports-on-control-planes]] == Usage Reports on Control Planes