Overview
As an MSP, the severity levels included in your reports are crucial for prioritizing incident response. These levels act as an indicator of the seriousness of an issue, allowing you to determine the urgency of addressing it.
The monitoring tools generate alerts to notify Enterprise Workloads administrators of changes, high-risk actions, or failures in the environment. All of these details and actions are captured in the Alert History report. The Alert History report provides alert details based on their severities and types in a tabular representation
The combination of global customer ID, customer name, and account name provides a powerful tool for identifying specific entries in a large dataset.
There are a few quick filters that you can use to filter out the data quickly based on specific requirements such as service plan and customer name. The use of quick filters enhances the usability of the reports and provides more targeted insights. The following table lists details of the quick filters.
Quick Filter | Description |
Service plan | Use this filter to view data based on specific service plans. Select one or more plans from the dropdown list to narrow down your results. |
Customer Name | Use this filter to view data for a specific customer. Start typing the customer's name and select the matching entry from the autocomplete list. |
📝 Note
The MSC fetches data of reports within a maximum of 6 to12 hours
It might take 24 to 48 hours for the data to appear in this report if a new customer or tenant is added to MSC.
To access the report:
Go to Managed Services Center (MSC) > Reports > Enterprise Workloads > Alert History Report.
📝 Note
The report is displayed in the administrator’s timezone.
The following table lists the fields in the Alert History Report.
Field | Description |
Global Customer ID | A Unique Universal Identifier for a customer. |
Customer Name | Name of the customer. |
Account Name | Name by which Druva should identify the customer. |
Alert Type | The type of the alert that occurred. For example, Jobs. |
Severity | The impact that occurred for a resource or entity. For example, Critical, Info, Warning and others. |
Description | The details of the generated alert. For example, Backup Failed. |
Target | The entity where the alert first occurred.
For example, the Azure VM name displays here for Azure-specific Alerts. |
Generated On | The date and time when the alert first occurred. |
Organization | The name of the organization in which the workload is configured. |
Resolved | Status of alerts whether it is resolved or not. |
Actions
The following table lists the actions that you can perform on this report page-
Action | Description |
Add filter | Creates and applies filters to display customized report data. |
Rearrange column | Drag and drop column headers to change their order in the table. |
Manage Subscription | Create a subscription to receive the reports on schedule. |
Email Report | You can email the report as either an attachment or a link. |
Duplicate Report | You can duplicate the report and customize it as per your requirements. |