Actions39
- Admin Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Hybrid Workloads Actions
- Report - Usage Actions
- Service Plan Actions
- Task Actions
- Tenant Actions
Overview
The "Report - Hybrid Workloads" resource with the "Get Resource Status Report" operation in this node allows users to retrieve status reports about hybrid workloads managed within the Druva MSP platform. This report provides insights into the current state of various resources, filtered by multiple criteria such as date ranges, customers, workload types, resource statuses, and resource types.
This node is beneficial for IT administrators and MSP operators who need to monitor and analyze the health and status of their hybrid cloud workloads. For example, it can be used to generate periodic reports on resource availability or issues, helping teams proactively manage infrastructure and ensure service continuity.
Practical examples include:
- Generating a monthly status report for all resources across specific customers.
- Filtering the report to show only resources with critical status values.
- Limiting the report to certain workload types or resource types to focus on particular segments of the environment.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or limit the output to a specified number. |
| Limit | Maximum number of results to return when not returning all. Value range: 1 to 100. |
| Date Selection Method | Choose how to filter data by date: no filter, specific start/end dates, or predefined relative date ranges. |
| Start Date | The inclusive start date for filtering report data (used if "Specific Dates" is selected). |
| End Date | The inclusive end date for filtering report data (used if "Specific Dates" is selected). |
| Date Range | Predefined relative date ranges for filtering report data (used if "Relative Date Range" is selected). Options include current/previous month, quarter, year, last 30/60/90 days, last 6/12 months, and year to date. |
| Filter by Customer(s) | Whether to filter the report results by specific customers. |
| Customer IDs | List of customer IDs to filter by (shown if filtering by customers is enabled). |
| Filter by Workload Types | Whether to filter the report by workload types. |
| Workload Types | List of workload types to filter by. For alert history reports, this filters by alert type. |
| Filter by Resource Status | Whether to filter the report by resource status values. |
| Resource Status | List of resource status values to filter by (shown if filtering by resource status is enabled). |
| Filter by Resource Types | Whether to filter the report by resource types. |
| Resource Type | List of resource types to filter by (shown if filtering by resource types is enabled). |
Output
The node outputs JSON data representing the resource status report according to the applied filters. The structure typically includes an array of resource status entries, each containing details such as resource identifiers, status values, workload types, timestamps, and possibly related metadata.
If binary data were involved (not indicated here), it would represent files or attachments related to the report, but this operation focuses on JSON-formatted report data.
Dependencies
- Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
- The node depends on the Druva MSP API endpoints for fetching customers, workload types, resource statuses, and resource types to populate dropdown options dynamically.
- Proper permissions and API access rights are necessary to retrieve report data.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Selecting incompatible filter combinations may result in empty datasets.
- Exceeding API rate limits could lead to temporary request failures.
- Providing invalid date ranges (e.g., start date after end date) might cause errors or no results.
Error Messages:
- Authentication errors usually indicate invalid or expired API keys; reconfigure credentials.
- "Resource not implemented" error occurs if an unsupported resource is selected.
- Network or timeout errors suggest connectivity issues with the Druva MSP API.
- Validation errors on input parameters should be checked against allowed values and formats.
To resolve these, verify API credentials, check filter settings, ensure network connectivity, and consult Druva MSP API documentation for limits and constraints.