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 - Enterprise Workloads → Get Alert History Report
AI-generatedOverview
This node operation fetches the Alert History Report from the Druva MSP API under the 'Report - Enterprise Workloads' resource. It allows users to retrieve alert history data filtered by various criteria such as date ranges, customers, workload types (alert types), and alert severity levels. This operation is useful for enterprises needing detailed historical alert data for monitoring, auditing, or compliance purposes.
Use Case Examples
- An enterprise IT admin wants to generate a report of all critical and warning alerts from the previous month to analyze system health and incidents.
- A security team filters alert history by specific customers and alert severity to focus on high-priority issues across their managed workloads.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return when 'Return All' is false. |
| Date Selection Method | Method to filter report data by date: no filter, specific dates, or relative date ranges. |
| Start Date | Start date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| End Date | End date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| Date Range | Predefined relative date range for filtering report data, used when 'Relative Date Range' is selected. |
| Filter by Customer(s) | Whether to filter results by specific customers. |
| Customer IDs | IDs of the customers to filter by, used when 'Filter by Customer(s)' is true. |
| Filter by Workload Types | Whether to filter by workload types (alert types for this report). |
| Workload Types | Types of workloads (alert types) to filter by, used when 'Filter by Workload Types' is true. |
| Filter by Alert Severity | Whether to filter by alert severity levels. |
| Alert Severity | Alert severity levels to filter by (Critical, Warning, Info), used when 'Filter by Alert Severity' is true. |
| 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
alertId- Unique identifier of the alert.alertType- Type of the alert (corresponds to workload types).alertSeverity- Severity level of the alert (Critical, Warning, Info).alertMessage- Message or description of the alert.alertTimestamp- Timestamp when the alert was generated.customerId- Identifier of the customer associated with the alert.tenantId- Identifier of the tenant associated with the alert.additionalDetails- Any additional details related to the alert.
Dependencies
- Druva MSP API
- API key credential for authentication
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access the Alert History Report.
- If no results are returned, verify the date filters and other filter criteria to ensure they match existing alert data.
- Common error messages may include authentication errors, invalid date range errors, or exceeding API rate limits. Check the error message details and adjust parameters accordingly.
- Enable 'Wrap Output Items' if the next node should process all results as a single batch to avoid multiple executions.
Links
- Druva MSP API Documentation - Official API documentation for Druva MSP including report endpoints.