Alexey D. wrote:Hello John,
I'm just wondering, maybe this runaway process has some 'external signs' (raised disk I/O, memory usage, etc.)?
Monitor has plenty of alarms to fine-tune and catch that behaviour. Can you describe your runaway process?
I'm trying this angle, but it's not accurate enough for my liking (well, the customer's liking, actually. I'm the consultant for them in this scenario). I can usually get the process to trigger a spike in active memory on the VM and THAT gets me the alert I want, but we get some false positives when other, legitimate things pike the VMs memory. To answer your question about the process, these are XenApp servers and there is an issue with Outlook using up available memory....caused by the print driver isolation feature of R2 (I am not a citrix guy, but our citrix guy is working with Citrix, Microsoft and the customer on this). The customer does not want to spend money on Citrix Edgesight and since I'm in there as a vSphere consultant, demonstrating the benefits of VEEAM One (for other reasons unrelated to this issue, such as replacing vFoglight), I thought I'd take a crack at getting some reliable alerts for this Citrix issue while I was onsite. Like I mentioned above, it's decent when I do it via active memory, but I still get false positives.
Vitaliy S. wrote:By the way, do you have any EMS? How do you monitor your physical environment? SCOM by any chance?
The customer has no monitoring solutions in-place today except vFoglight. And hopefully VEEAM One soon.
Gostev wrote:Let's discuss this feature request internally.
Cool. Thanks for listening.