Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Usage → Get Itemized Tenant Consumption

AI-generated

Overview

The node interacts with the Druva MSP API to retrieve detailed itemized tenant consumption reports. It supports filtering by date ranges (specific dates, relative date ranges, or all dates), customers, edition names, products, product modules, usage descriptions, MSP global ID, and MSP name. This node is useful for generating detailed usage reports for tenants, which can help in billing analysis, resource management, and usage tracking within an MSP environment.

Use Case Examples

  1. Generate a report of tenant consumption for the previous month filtered by specific customers and product modules.
  2. Retrieve itemized consumption data for a specific date range to analyze usage trends.
  3. Get a detailed usage report filtered by MSP global ID to monitor consumption across managed service providers.

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 relative date range for billing period analysis, required if using relative dates.
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.
Filter by Edition Names Whether to filter results by specific edition names.
Edition Names List of edition names to include in the report, required if filtering by edition names.
Filter by Products Whether to filter results by specific product IDs.
Product IDs List of product IDs to include in the report, required if filtering by products.
Filter by Product Modules Whether to filter results by specific product module IDs.
Product Module IDs List of product module IDs to include in the report, required if filtering by product modules.
Filter by Usage Descriptions Whether to filter results by specific usage descriptions.
Usage Descriptions List of usage descriptions to include in the report, required if filtering by usage descriptions.
Filter by MSP Global ID Whether to filter results by a specific MSP global ID.
MSP Global ID MSP global ID to filter by (exact match), required if filtering by MSP global ID.
Filter by MSP Name Whether to filter results by a specific MSP name.
MSP Name MSP name to filter by (exact match), required if filtering by MSP name.
Return All Whether to return all results or only up to a given limit.
Limit Max number of results to return, used if not returning all results.
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

  • tenantId - The unique identifier of the tenant for which the consumption data is reported.
  • customerId - The unique identifier of the customer associated with the tenant.
  • usageDate - The date of the usage record.
  • productId - The identifier of the product associated with the usage.
  • productModuleId - The identifier of the product module associated with the usage.
  • usageDescription - Description of the usage type or category.
  • consumedQuantity - The quantity of the resource consumed during the usage period.
  • unitOfMeasure - The unit of measure for the consumed quantity.
  • cost - The cost associated with the consumed quantity.

Dependencies

  • Druva MSP API
  • API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to access usage reports.
  • Verify that date filters are correctly set; using specific dates requires both start and end dates.
  • If filtering by customers, edition names, products, or other filters, ensure the selected IDs or names are valid and exist in the system.
  • Check for API rate limits or network issues if the node fails to retrieve data.
  • Common error messages may include authentication failures, invalid date ranges, or missing required parameters. Review the error message details and adjust the node parameters accordingly.

Links

  • Druva MSP API Reference - Official API documentation for Druva MSP, useful for understanding available endpoints and parameters.

Discussion