Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN 8.0 Administrator Guide > Use the Virtual Infrastructure Monitor > Create virtualization alerts in the Orion Alert Manager

Create virtualization alerts in the Orion Alert Manager

Table of contents
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 10 Votes: 0 Revisions: 3

Alerts notify you when an issue or error occurs in the virtual environment. The Orion Platform provides alerts for all monitored nodes and applications, including alerts for integrated products. VMAN provides over 40 virtualization alerts to identify common issues in virtual environments including clusters, hosts, datastores, and VMs.

For information about creating and editing alerts in the Alert Manager, see Creating New Alerts and alerts in the VMAN Getting Started Guide.

If VIM is integrated with Virtualization Manager, virtualization alerts are available by default. If you remove the integration, these alerts will be disabled, but you can still create your own alerts for object types including:

  • Virtual clusters
  • Virtual datastores
  • Virtual hosts
  • Virtual machines

To learn about the integration between VIM and Virtualization Manager, see Integrate VIM with Virtualization Manager.

These alerts include:

  • Threshold-based alerts: monitor network utilization, CPU load, memory usage, IOPS, latency, and capacity.
  • Activity-based alerts: monitor specific actions in an environment including authentication failures, syslog, changes in network configurations, and events.
  • Network-based alerts: monitor connections between networked servers and devices including latency, connection state, and IOPS.

Monitor alerts after deployment to troubleshoot and maintain your environment. Virtualization alerts trigger for real-time monitored data and events using virtualization thresholds (global and specific to VM). Recommendations require collected data over 1 hour for active to 7 days for predictive to effectively trigger.

Until the Orin Web Console collects the required data for recommendations, monitor alerts through the Virtualization Summary. Issues bubble up through the Recommendations and Alert resources.

Recommendations

Lists all triggered active and predictive recommendations.

If available, active recommendations include a link to a related alert:

All Active Virtualization Alerts Lists all triggered alerts for active issues in your virtual environment. Alerts display in order: critical, serious, and warning.
Potential Virtualization Issues

Lists triggered informational virtualization alerts.

Informational alerts indicate trends in status, usage, and capacity. For example, an informational alert triggers when VM management tool access times out between the Orion Platform and a VM.

Alert categories without triggered issues display as green.

Best practices for alerts

All alerts for virtualization and the Orion Platform are enabled by default in the Orion Web Console. To reduce noise, you can refine or disable unused alerts. To modify existing trigger conditions and actions, SolarWinds recommends you create a copy of an alert and customize the copy.

To better monitor issues with alerts:

  • Adjust thresholds. (recommended) Alerts trigger when monitored usage exceeds global or specific VM thresholds. Critical active alerts indicate spikes in usage and capacity. Potential alerts indicate trends that can lead to an issue.
  • Disable alerts. If an alert is not helpful for your monitoring needs, you can disable it. SolarWinds recommends you create a copy, modify the settings, and disable the original.
  • Create and customize alerts. The out-of-the-box alerts cover a range of issues you may want to customize. You can create a copy of an existing alert, disable the original and customize the copy. If you edit an out-of-the-box alert, a message warns what data can be modified or added.

  • Set notification actions for specific alerts, not all alerts. For large environments, email notification actions on every alert can overwhelm your staff. Set email notifications for specific alerts.

  • Monitor the Virtualization Summary. Use the Virtualization Summary to continuously monitor all alerts. The alerting resources update with every polling. Triggered alerts display in order of severity.
 
Last modified
04:19, 23 Jun 2016

Tags

Classifications

Public