Working on alerts Alerts can be handled in various ways in keeping with company policy and constraints. You can resolve an alert or you can immediately close a potentially dangerous DBMS session in response to an alert. In addition, you can create a rule based on the scenario that triggered the alert (particularly useful in preventing future false positives) or establish trust for a specific current session. View alert details View alert details to investigate and take necessary action on an alert. Resolve an alert When an alert is first triggered, the alert is displayed in the alert list with a default status of Unresolved. You can review the details of the alert and depending on the properties, change its resolution state to either Resolved or False Alarm. Create a rule based on an alertCreate a rule for an alert and save the rule under Custom Rules. This is helpful when you need to create an exception such as, preventing the repeated occurrence of false positives. Create a rule exception based on an alertCreate an exception to a vPatch or custom rule based on an alert. Generate alert reportsGenerate a report that contains detailed information about each of the alerts displayed in the alerts list. Archive alerts Archiving the alerts at regular intervals ensures that the size of the alerts does not increase significantly. Archived alerts are compressed and then stored in an archive file. Create a resolve typeBased on your own experience, you can create custom resolve types to monitor alerts generated in response to specific conditions or events. Edit a resolve type name You can edit the name of a user-defined resolve type at any time. Delete a resolve type Delete a user-defined resolve type that is no longer needed.