Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Managing fault alerts in vRealize Operations Manager (74781)

Last Updated: 3/10/2020Categories: InformationalTotal Views: 10023Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Purpose

This article provides information on managing Fault based alerts in vRealize Operations Manager.

Resolution

Fault based alerts come from the monitoring source, such as vCenter.
These create an alert in vRealize Operations Manager that stays active until the issue is addressed in the monitoring source, and the alarm is cleared on the source.

Fault based alerts are not actively checked by vRealize Operations Manager for active symptoms, and as such will not be resolved or cleared by vRealize Operations Manager.  Instead, once the alarm is cleared on the source side, the alert will become inactive in vRealize Operations Manager within a few collection cycles.

Though you can manually cancel a Fault based alert in vRealize Operations Manager, this will not clear the underlying alarm from the source.  Canceling a still active Fault based alert will result in the alert re-triggering in vRealize Operations Manager if the source alarm is still active.

Related Information

To test if vRealize Operations Manager is still receiving a Fault alarm from the source, manually cancel the Fault based alert.  If the alert re-triggers, then the Fault alarm is still active on the source.
To cancel a Fault Alert, follow the procedure below.

Log in to the vRealize Operations Manager UI as an administrative user.

Navigate to Alerts > All Alerts.

Select the desired Fault Alert, then click Actions > Cancel Alert.

Click Yes to confirm the alert cancellation, then click OK in the info dialog box.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
ホット パッチを適用した後、使用量メーターがログ バンドルのエクスポートに失敗し、暗号化されていないレポートを送信する (74693)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

VMware vCenter Operations Manager

VMware vCenter Operations

Related Versions:

VMware vRealize Operations Manager 7.5.x

VMware vRealize Operations Manager 7.0.x

VMware vRealize Operations Manager 6.7.x

VMware vRealize Operations Manager 6.6.x

VMware vRealize Operations Manager 6.5.x

VMware vRealize Operations Manager 6.4.x

VMware vRealize Operations 8.x

VMware vRealize Operations 8.1.x

VMware vRealize Operations 8.0.x

view all

Take Our Survey

Support Assistant