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 "Get DR Failover Activity Report" operation within the "Report - Hybrid Workloads" resource fetches disaster recovery (DR) failover activity data from the Druva MSP API. This report provides insights into failover events related to hybrid workloads, which is critical for monitoring and auditing disaster recovery processes.
Typical use cases include:
- Tracking and auditing DR failover activities over specific time periods.
- Filtering reports by customer to focus on particular accounts.
- Generating compliance or operational reports for IT teams managing hybrid cloud environments.
For example, an IT administrator might use this node to retrieve all DR failover activities in the last 30 days for a set of customers to analyze failover frequency and success rates.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available 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 the report data by date: • No Date Filter — include all dates. • Specific Dates — filter between a start and end date. • Relative Date Range — select from predefined relative ranges like current month, last 30 days, etc. |
| Start Date | The inclusive start date for filtering report data (used only if "Specific Dates" is selected). |
| End Date | The inclusive end date for filtering report data (used only if "Specific Dates" is selected). |
| Date Range | Predefined relative date ranges for filtering report data (used only if "Relative Date Range" is selected). Options include: Current Month, Previous Month, Current Quarter, Previous Quarter, Current Year, Previous Year, Last 30/60/90 Days, Last 6/12 Months, Year To Date. |
| Filter by Customer(s) | Whether to filter the report results by specific customers. |
| Customer IDs | List of customer IDs to filter the report by (shown only if filtering by customers is enabled). |
Output
The node outputs JSON data representing the DR failover activity report entries. Each item in the output array corresponds to a single failover event or aggregated report record, containing fields such as timestamps, customer identifiers, and failover details.
If binary data were involved (e.g., file exports), it would be summarized here, but this operation focuses on JSON report data.
Dependencies
- Requires an active connection to the Druva MSP API with appropriate API authentication credentials configured in n8n.
- The node depends on the Druva MSP API endpoint for hybrid workload reports.
- Pagination and filtering are handled internally via API requests.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying invalid date ranges (e.g., start date after end date) may result in empty or error responses.
- Requesting too many records without enabling "Return All" may truncate results due to the limit.
- Filtering by customer requires valid customer IDs; invalid or empty selections may yield no data.
Error Messages:
- Errors from the API (e.g., rate limits, invalid parameters) will be surfaced as node execution errors.
- Network connectivity issues can cause request failures.
- If the resource or operation is not implemented, the node throws an explicit error indicating so.
To resolve these:
- Verify API credentials and permissions.
- Double-check date filters and customer selections.
- Enable "Return All" cautiously to avoid large data loads.
- Review API documentation for parameter constraints.
Links and References
- Druva MSP API Documentation (general reference): https://docs.druva.com/
- n8n Documentation on Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- Best Practices for Date Filtering in APIs: https://restfulapi.net/filtering/