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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNDk0IiwiaGFzaCI6IjQ1ZmI3MDJiLTQ3ZjItNGRkOS04OGZjLTU0ODUyN2IzNDk4YSJ9
1-800-691-1991 | 9am - 8pm ET
EN

NWorks Metric Definitions and VC Events

Purpose

Some customers want to create custom alerts, change settings within their VC, or verify what type of data is being collected.  Veeam supplies a list of what Metrics and Events that we use for nWorks.

Solution

Here is a list of the nWorks Metrics:

https://helpcenter.veeam.com/docs/mp/vmware_reference/metric_definitions.html?ver=80U6

Here is a list of the nWorks Events:
https://helpcenter.veeam.com/docs/mp/vmware_reference/vcenter_events.html?ver=80U6

An example of how to use these 2 list is if you wanted to know how to create an alert for when a VM loses network connectivity, you would use the nWorks Events list (answer: VmNetworkFailedEvent) and if you wanted to know VM CPU usage you would use the Metrics list (answer: cpuUsedPct for percent or cpuUsageMhz for Mhz). 

More information

If you need assistance with this or have any questions, feel free to contact support. 

KB ID:
1494
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.x
Published:
2012-01-24
Last Modified:
2020-08-28
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