Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Usage → Get MSP Commit and Balance Report

AI-generated

Overview

This node operation fetches the MSP Commit and Balance Report from the Druva MSP API. It allows users to retrieve detailed usage reports related to commitments and balances for managed service providers. This is useful for MSPs to analyze their service usage, monitor commitments, and manage balances effectively over specific or relative date ranges.

Use Case Examples

  1. An MSP wants to generate a report for the previous month to review their committed service usage and remaining balance.
  2. A user needs to fetch the MSP Commit and Balance Report for a custom date range to analyze usage trends and billing details.

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 (used if Date Selection Method is Relative Date Range)
Return All Whether to return all results or only up to a given limit
Limit Maximum 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

  • items - Array of report items when output is wrapped
  • count - Count of total items in the wrapped output
  • json - Individual report item data when output is not wrapped

Dependencies

  • Druva MSP API with appropriate API key credentials

Troubleshooting

  • Ensure the API credentials are correctly configured and have permissions to access MSP Commit and Balance reports.
  • If the node returns an error about the resource not being implemented, verify that the resource parameter is set to 'reportUsage' and the operation to 'getCommitAndBalance'.
  • If no data is returned, check the date selection method and date range parameters to ensure they are valid and cover a period with available data.
  • If the node fails on some items but continues on others, enable 'Continue On Fail' to handle partial failures gracefully.

Discussion