Actions79
- Admin Actions
- Alert Summary Actions
- Backup Health Summary Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Enterprise Workloads Actions
- Get Alert History Report
- Get Backup Activity Report
- Get DR Failback Activity Report
- Get DR Failover Activity Report
- Get DR Replication Activity Report
- Get Resource Status Report
- Get Storage Consumption by BackupSets Report
- Get Google Alerts Report
- Get Google License Usage Report
- Get Google Preserved Users Datasources Report
- Get Google Shared Drive Backup Activity Report
- Get Google Shared Drive Restore Activity Report
- Get Google Storage Consumption Report
- Get Google User Count and Status Report
- Get Google User Last Backup Status Report
- Get Google User Provisioning Report
- Get Google User Restore Activity Report
- Get Google User Workload Report
- Get M365 Alerts Report
- Get M365 Groups Backup Activity Report
- Get M365 Groups Discovery Report
- Get M365 License Usage Report
- Get M365 Preserved Users Datasources Report
- Get M365 Public Folder Backup Activity Report
- Get M365 SharePoint Backup Activity Report
- Get M365 SharePoint Site Discovery Report
- Get M365 Storage Consumption Report
- Get M365 Teams Backup Activity Report
- Get M365 Teams Discovery Report
- Get M365 User Count and Status Report
- Get M365 User Last Backup Status Report
- Get M365 User Provisioning Report
- Get M365 User Restore Activity Report
- Get M365 User Workload Report
- Report - Usage Actions
- Service Plan Actions
- Storage Region Actions
- Task Actions
- Tenant Actions
- Tenant Config - Enterprise Workloads Actions
- Tenant Config - inSync Actions
Report - Usage → Get Chargeback Tenant Consumption Daily Report
AI-generatedOverview
This node operation fetches the Chargeback Tenant Consumption Daily Report from the Druva MSP API. It is useful for MSP administrators or billing analysts who need detailed daily consumption data for tenants to analyze chargeback costs and usage patterns. For example, it can be used to generate daily usage reports for tenants to allocate costs accurately or monitor consumption trends over time.
Use Case Examples
- Generate a daily chargeback report for tenants within a specific date range to analyze usage and billing.
- Retrieve daily consumption data for tenants filtered by specific customers to understand customer-specific usage patterns.
Properties
| Name | Meaning |
|---|---|
| Date Selection Method | Choose whether to use specific dates, relative date ranges, or include all dates (no date filter) for the report. |
| Start Date | Start date for the usage report period, required if 'Specific Dates' is selected. |
| End Date | End date for the usage report period, required if 'Specific Dates' is selected. |
| Date Range | Select a predefined relative date range for billing period analysis, required 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 is enabled. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return 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 daily 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.
- If filtering by customers, verify that the customer IDs are valid and accessible by the API user.
- Check date parameters for correctness, especially when using specific dates or relative date ranges to avoid empty or invalid responses.
- Common errors may include authentication failures, invalid parameter errors, or API rate limits being exceeded. Review error messages and adjust parameters or credentials accordingly.