Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Watch4net: How do I configure Watch4net to alert on Smarts Events? (317558)

Last Updated: 3/22/2024Categories: How toTotal Views: 15880Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

How do I configure Watch4net to alert on Smarts Events?

The RPE feature (Report Pack for Events) should and must be already installed and functional. See APG-RPE-How-To.pdf in /opt/APG/Docs or C:\Program Files\APG\Docs.
1. Create the APG Events Adapter in the Alerting module in the Frontend:

In Administration, go to Modules and open Alerting
Select Adapters and click "Create new element":

Type:                    APG Events Adapter
Name:                   Smarts Events Adapter
Value field:            Any numerical field from a Smarts event (such as FirstNotifiedAt). Note you need to specify one. See below for a full list of the Smarts event fields and their data types.
Properties field:    Inculde all fields from a Smarts event that you need to push to the Alerting-Backend. Each field must be separated by a comma. Eg ClassName,Name,EventName
Port:                     4010 (any unused port on the server where the alerting backed is installed)

Click Save
Go to Adapters and ensure the newly created adapter is Enabled.

2. Create an Alert definition.

The Alert filter should filter only on properties made available by the Events Adapter (e.g. EventName is present or ClassName=='Router').
The log template can be used, but the Entry Content should be changed to use Smarts Event fields (e.g. PROP.'ClassName' event is PROP.'Name' and element is PROP.'ElementName').
Again, only use fields that were made available to the Alerting-Backend via the Properties field of the Events adapter.
Save and Enable the alert.

3. Install the Generic-Event-Writer module
/opt/APG/bin/manage-modules.sh install generic-event-writer

4. Configure the Event-Processing-Manager to send alerts to the Generic-Event-Writer

Edit /opt/APG/Event-Processing/Event-Processing-Manager/Default/conf/processing.xml:

Add the following line. This will enable the Generic-Event-Writer configuration:

<!-- Generic Event Writer -->
<processing-element name="Generic-Event-Writer" config="Generic-Event-Writer/Default/conf/generic-event-writer.xml"/>

Edit the Smarts-Listener line and set it to send the events also to a Generic-Event-Writer stream named data:

<!-- Smarts Listener -->
<processing-element name="Smarts" config="Smarts-Listener/Default/conf/smarts-listener.xml" data="AC Generic-Event-Writer[data]" />

Edit /opt/APG/Event-Processing/Generic-Event-Writer/Default/conf/generic-event-writer.xml) and enable the stream:

<!-- Data received on the specified INPUT stream will be sent on the specified port. -->
<data-stream>data</data-stream>
<hostname>localhost</hostname>
<port>4010</port>
<serializer>
<class>com.watch4net.events.common.serialization.GenericEventSerializer</class>
</serializer>
</sender>

IMPORTANT!
- Ensure port used (4010) is the same as the one defined for the APG Events Adapter in step 2.
- Ensure the name of the stream (data) is the same as what is specified processing.xml configuration for Smarts-Listener (data="AC Generic-Event-Writer[data]").

5. Restart the Event Processing Manager and check the logs.

The Event Processing Manager will not start if the APG Events Adapter from Step 1 is not enabled.

6. Check the log file created by the Alert created on step 2

If the file prefix is Alerts/log, the file location will be in /opt/APG/Backends/Alerting-Backend/Default/Alerts/ directory.

Related Information

Smarts Event fields and their data types:
Name                              STRING
ClassName                      STRING
InstanceName                STRING
EventName                     STRING
ClassDisplayName          STRING
InstanceDisplayName     STRING
EventDisplayName         STRING
ElementClassName         STRING
ElementName                 STRING
SourceDomainName      STRING
SourceEventType         STRING
Active                           BOOLEAN
OccurrenceCount         LONG
FirstNotifiedAt              LONG
OpenedAt                    LONG
ClosedAt                      LONG
LastChangedAt            LONG
IsRoot                          BOOLEAN
IsProblem                     BOOLEAN
Acknowledged             BOOLEAN
ClearOnAcknowledge  BOOLEAN
EventType                   STRING
EventState                  STRING
Category                     STRING
EventText                   STRING
Severity                       LONG
Impact                         LONG
Certainty                     FLOAT
InMaintenance            BOOLEAN
TroubleTicketID           STRING
Owner                        STRING
UserDefined1 - 20      STRING
Source                        STRING
SourceSpecific            STRING

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant