Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Usage → Get Chargeback Tenant Consumption Monthly Report

AI-generated

Overview

This node operation fetches the Chargeback Tenant Consumption Monthly Report from the Druva MSP API. It is useful for MSP administrators or billing analysts who need detailed monthly consumption data for tenants to manage chargebacks and billing accurately. For example, it can be used to generate monthly usage reports filtered by specific customers or date ranges to analyze tenant consumption patterns and costs.

Use Case Examples

  1. Generate a monthly chargeback report for all tenants for the previous month.
  2. Fetch the chargeback consumption report for specific customers within a custom date range.

Properties

Name Meaning
Date Selection Method Choose whether to use specific dates, relative date ranges, or include all dates (no date filter).
Start Date Start date for the usage report period (required if using specific dates).
End Date End date for the usage report period (required if using specific dates).
Date Range Select a predefined date range for billing period analysis (used if relative date range is selected).
Filter by Customers Whether to filter results by specific customer IDs.
Customer IDs List of customer IDs to include in the report (required if filtering by customers).
Return All Whether to return all results or only up to a given limit.
Limit Max number of results to return (used if Return All is false).
Wrap Output Items When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times.
Wrapper Property Name The property name to use for the wrapped array of items in the output. Default is "items".

Output

JSON

  • json - The main JSON output containing the chargeback tenant consumption monthly report data.

Dependencies

  • Druva MSP API with appropriate API key credentials

Troubleshooting

  • Ensure the API credentials are correctly configured and have permissions to access the chargeback tenant consumption report endpoint.
  • If filtering by customers, verify that the customer IDs are valid and accessible by the API user.
  • Check date parameters for correct format and logical consistency (start date before end date).
  • Common errors include authentication failures, invalid parameter values, or API rate limits. Review error messages for specific guidance.

Links

Discussion