Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The "Get Itemized Tenant Quota" operation under the "Report - Usage" resource retrieves detailed quota usage data for tenants within a specified date range and with optional filters. This node is useful for MSP administrators or billing analysts who need to analyze tenant-level usage quotas, monitor consumption patterns, or generate reports for billing reconciliation.

Typical scenarios include:

  • Generating monthly or quarterly usage quota reports for tenants.
  • Filtering quota data by specific customers, product editions, products, or usage descriptions.
  • Analyzing tenant quota consumption over custom or relative date ranges such as last 30 days or current year.

For example, an MSP might use this node to get itemized quota usage for all tenants in the previous month filtered by the "Enterprise" edition and specific product modules to prepare billing statements.

Properties

Name Meaning
Date Selection Method Choose how to select the date range for the report: "All Dates" (no filter), "Specific Dates" (custom start and end dates), or "Relative Date Range" (predefined periods like current month, last 30 days, etc.)
Start Date The start date of the usage report period (required if "Specific Dates" is selected)
End Date The end date of the usage report period (required if "Specific Dates" is selected)
Date Range Predefined relative date ranges for the report period, e.g., "Current Month", "Previous Year", "Last 90 Days" (used if "Relative Date Range" is selected)
Filter by Customers Boolean flag to enable filtering 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 Boolean flag to enable filtering results by specific edition names
Edition Names List of edition names to include in the report; options are "Business", "Enterprise", "Elite" (required if filtering by edition names)
Filter by Products Boolean flag to enable filtering 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 Boolean flag to enable filtering 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 Boolean flag to enable filtering results by specific usage descriptions
Usage Descriptions List of usage descriptions to include in the report; options include "Accelerated Ransomware Recovery", "Active Users", "Cloud Storage", "Long Term Retention Storage", etc. (required if filtering by usage descriptions)
Return All Whether to return all results or limit the number of returned items
Limit Maximum number of results to return if not returning all (minimum 1)

Output

The node outputs JSON data containing the itemized tenant quota usage records matching the specified filters and date range. Each record typically includes details such as tenant identifiers, quota metrics, usage descriptions, product and edition information, and timestamps corresponding to the usage period.

If binary data were involved (not indicated here), it would represent associated files or attachments related to the report, but this operation focuses on structured JSON data.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • The node uses the base URL https://apis.druva.com for API requests.
  • Some input properties load dynamic options from the API, such as customer IDs, product IDs, and product module IDs, requiring proper API access permissions.
  • No additional external services beyond the Druva MSP API are required.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Selecting filters without providing required values (e.g., enabling "Filter by Customers" but not specifying any customer IDs) will likely result in errors or empty responses.
    • Date range conflicts, such as an end date earlier than the start date, may cause request failures.
    • API rate limits or network issues can interrupt data retrieval.

  • Error Messages:

    • Errors related to missing parameters will indicate which required field is absent.
    • API errors will propagate messages from the Druva MSP service, often indicating invalid filters or unauthorized access.
    • If the resource or operation is not implemented, the node throws an error stating so.

  • Resolutions:

    • Ensure API credentials are correctly set up and have necessary permissions.
    • Provide all required filter values when enabling their respective flags.
    • Validate date inputs before execution.
    • Use the "Return All" option cautiously to avoid large data loads that may time out.

Links and References

Discussion