Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Consumption Billing Analyzer → Analyze Consumption with Quota Comparison

AI-generated

Overview

The 'Analyze Consumption with Quota Comparison' operation in the Consumption Billing Analyzer resource analyzes billing consumption data over a specified period, comparing actual usage against quota allocations. It supports filtering by customers, selecting date ranges either by specific dates or relative periods, and offers multiple calculation methods for billable values. The operation can convert byte values to larger units, apply rounding, and optionally filter out zero usage records. It is useful for MSPs or billing analysts who need detailed consumption insights with quota adherence, enabling cost control and usage optimization.

Use Case Examples

  1. Analyzing last month's consumption for specific customers to identify overages compared to their quotas.
  2. Calculating average daily usage over the current quarter and converting storage usage from bytes to terabytes for clearer reporting.
  3. Filtering out zero usage records and rounding results to two decimal places for a clean billing report.

Properties

Name Meaning
Date Selection Method Choose whether to use specific dates or relative date ranges for the billing period analysis.
Start Date Start date for the billing period (required if using specific dates).
End Date End date for the billing period (required if using specific dates).
Date Range Select a predefined relative date range for billing period analysis (used if relative dates are selected).
Filter by Customers Whether to filter results by specific customer IDs.
Customer IDs List of customer IDs to include in the analysis (required if filtering by customers).
Calculation Method Method to calculate billable values from daily consumption data.
Apply Rounding Whether to apply rounding to the calculated values.
Rounding Direction Direction for rounding calculated values (used if rounding is applied).
Decimal Places Number of decimal places to round to (used if rounding is applied).
Filter Out Zero Usage Whether to filter out items where both usage amount and CU consumed are zero.
Convert Byte Values Whether to convert raw byte values to a larger unit (GB or TB).
Target Unit Unit to convert byte values to (used if conversion is enabled).
Add Auto-Generated Key Whether to add a deterministic auto-generated key field to each record.
Key Field Name Name of the auto-generated key field (used if adding auto-generated key).
Show Only Overages Whether to return only records where consumption exceeds quota allocation.
Wrap Output Items When enabled, wraps all output items into a single item containing an array to prevent multiple executions downstream.
Wrapper Property Name The property name to use for the wrapped array of items in the output (used if wrapping is enabled).

Output

JSON

  • customerGlobalId - Global identifier for the customer.
  • tenantId - Identifier for the tenant.
  • startDate - Start date of the billing period analyzed.
  • endDate - End date of the billing period analyzed.
  • productName - Name of the product associated with the consumption.
  • productModuleName - Name of the product module associated with the consumption.
  • editionName - Edition name of the product or service.
  • usageDescription - Description of the usage type or category.
  • usageAmount - Amount of usage consumed during the period.
  • cuConsumed - Compute Units (CU) consumed, representing billable usage.
  • quotaAllocation - Allocated quota for the usage, used for comparison.
  • overageAmount - Amount by which usage exceeds the quota allocation.
  • id - Optional deterministic auto-generated key for the record, if enabled.

Dependencies

  • Druva MSP API with appropriate API key credentials

Troubleshooting

  • Ensure the API credentials are correctly configured and have necessary permissions to access consumption data.
  • If filtering by customers, verify that the customer IDs are valid and accessible by the API user.
  • Date range selections must be valid; specific start and end dates should be logical (start before end).
  • Rounding settings should be consistent; applying rounding with incompatible decimal places or directions may cause unexpected results.
  • If 'Show Only Overages' is enabled but no records appear, verify that there is actual overage data in the selected period and customers.
  • Network or API rate limit issues may cause errors; consider retry or error handling settings in the workflow.

Links

Discussion