New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Monitoring VMWare

Votes:

0

Your Vote:

Up

Down

We are currently using PRTG to monitor our enterprise environment and are looking to improve certain areas - specifically alerting to lower notification "noise".

We have made the specific decision to do all alerting from libraries - which are dynamically regenerated from the device tree as devices are added and removed.

Also of note is due to the very large scale of our environment (using a cluster and remote probes) we are still heavily dependent on leveraging SNMP as our primary polling method to keep performance at an acceptable level.

Monitoring of VMWare is implemented as follows:

  1. Vcentre Server (>500 VMs)
    1. autodiscovered / rebuilt every 24 hours using specialized guest template (VMGuest_only.odt included at end)
    2. VMs polled every 5 min for performance (using VMWare VM SOAP sensor)
  2. Specialized / Mission Critical VMs (ie: Mfg, SQL)
    1. monitored on a standalone basis (ping, snmp uptime, snmp cpu, snmp memory, snmp disk free, snmp traffic)
    2. notification and alerting is generated out of custom libraries dedicated to the technical teams responsible for the VM
  3. Alerting
    1. Ping is used as a primary means of up / down alerting (60 sec polling)
    2. Alerting is almost solely based on state triggers (which tend to be sensitive to short term events ie: cpu spikes)
    3. Alternatives would be to use threshold based triggers (ie: sustained high cpu) but this would impact all sensors in a library.

      SNMP cpu sensors (most desired spec as we are hugely compute bound) would ideally yield a down state in the event of sustained high CPU. The Linux SNMP library allows use of 1,5,15 min cpu load sensors - something similar would be ideal as we could use the 15 min load as our trigger for a down state.

      I have looked the VMWare provided MIBs in the hopes of finding something there of use but I'm not seeing anything. One solution we have looked at is doing a library based on filtered sensor types to CPU and setting a threshold trigger on that but this seems like more of a work around than a proper solution.

Anyone have any insights, suggestions or feedback ?

VMGuest_only.odt


<?xml version="1.0" encoding="UTF-8"?>

  <devicetemplate id="vmware-guest-only" name="vmWare Guests Only" priority="1" deviceicon="C_OS_VMware.png" >

  <check id="ping" meta="ping"/>

  <check id="vmhostsoap" meta="MetaVmwareServerHostSoap" requires="ping"/>

<!--create id="vmhost" kind="esxserversensorextern" meta="MetaVmwareServerHostExtern" requires="metavmwareserverhostsoap"   displayname="Guest VM [name]"-->

  <create id="vm" kind="vcenterserverextern" meta="Metavcenterserverextern" requires="vmhostsoap">

    <createdata>

      <priority>3</priority>

      <interval>300</interval>

    </createdata>

  </create>

  </devicetemplate>

libraries notifications prtg snmp vmware

Created on Dec 6, 2017 10:30:57 PM by  Darrin Domoney (0) 1

Last change on Dec 7, 2017 11:41:42 AM by  Stephan Linke [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Hi Darrin,

Thanks for the detailed request, that sure makes helping easier :) Just to recap, you want to monitor CPU usage, i.e. alert upon it, but not have it the other sensors impacted by that? Then the best way would be a dedicated node in the library (or a new library) that targets these sensors (SNMP CPU Load) specifically and alerts accordingly due to their threshold.

You could also differentiate between various severity levels by filtering the nodes by priority and have different notification options for each of them :)


Kind regards,
Stephan Linke, Tech Support Team

Created on Dec 7, 2017 12:07:55 PM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.