Thank you very much for your great question,
I'm attaching a sample Management Pack, it creates one monitor for VM. By default it's cpu latency, but you can change to whatever our collector publish to WMI (it depends on the Collector version).Veeam.VMware.VM.Metric.Monitor.zip
I've created it with your threshold settings, so you can use it out of the box.Monitor type usage desciption:
The motnitor is using Veeam-branded monitor type (Veeam.Virt.Extensions.VMware.CommonPerformance.3StateThresholdMonitorType
), which takes WMI class (<ClassName>VMSTATS</ClassName>) and numsamples (<NumSamples>1</NumSamples>, how many samples to wait before triggering a monitor) as parameters. Since this monior type works for any metric in the configured class and for all instaces of the configured class, this monitor can be cooked-down (trust us this is reall y cool thing
in terms of performance). Then you just have to take metric you want into the performance mapper (<Value>$Data/Property[@Name='cpuLatency']$</Value>, object, counter and instance names could be anything you want) and perform a filtering, so that each VM will have its own metric (<FilterExpression>...</FilterExpression>)
You can either specify thresholds right in the management pack (<Threshold1>5</Threshold1><Threshold2>10</Threshold2>), or override them in SCOM console. Alert text can be changed in SCOM console too.
Let me know if you have any questions regarding using our montior types or just about creating custom monitors for data gathered by Veeam MP.