https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMDMyIiwiaGFzaCI6IjhkNWM1ZWEyLTgwNzItNDcwYi05Yzc2LWFiYjBhNGE1OTUyNSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Filtering VC events in nworks SPI

Challenge


Cause

There may be, however certain reasons for not collecting events with "Verbose" severity level: it reduces the total amount of captured events and mitigates the traffic back to collector (there have been cases, when the Customers were concerned with this).

Solution

There are 3 levels of event filtering:

1. VC side. Only used in case of VCVerboseFiltering ON. nworks sends VC event list from "vcEvents.xml" as a parameter to create eventFilter on VC side. It means that VC will only return events present in this list. This method, however, could lead to severe performance issues with VC DB and can not be used on some environments (big environments are especially prone to being affected by this).

2. Collector side. nworks gets ALL events of the last interval, but sends into Operations Manager only events present in "vcEvents.xml" (independent of their severity). Other events will be suppressed. Although nworks gets all events of the last interval, it should not lead to DB overload since no subqueries (or indexes) should be applied on VC side.

3. HP Agent side. Events are present in "vcEvents.xml" and sent to Operations Manager but filtered by suppression rules.

Removing events from "vcEvents.xml" will drop events on the collector side not loading HP Agent, but all event will be gathered from VC in this scenario.

KB ID:
1032
Version:
5.x
Published:
2011-07-14
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later