Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Report - Usage → Get Customer and License Daily Report

AI-generated

Overview

This node operation fetches the Customer and License Daily Report from the Druva MSP API. It allows users to retrieve detailed daily usage data related to customers and their licenses, which is useful for monitoring consumption, managing licenses, and analyzing usage trends over specific periods.

Use Case Examples

  1. A managed service provider wants to generate a daily report of license usage for specific customers to optimize license allocation.
  2. A company needs to analyze daily consumption data for billing and auditing purposes over a selected 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 when 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 is enabled.
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return if not returning all.
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 report data for customer and license daily usage.

Dependencies

  • Druva MSP API with appropriate API key credentials

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access usage reports.
  • If filtering by customers, verify that the customer IDs provided are valid and exist in the system.
  • Check date parameters for correctness, especially when using specific dates to avoid invalid date ranges.
  • If the node returns an error, review the error message for details such as rate limits or missing required parameters and adjust accordingly.

Discussion