Hi,

The PRTG Server located in Server1 is set to send a notification if Server2's (with PRTG Probe) CPU usage goes above 80% for 2 minutes (using threshold trigger). The notification runs an EXE that queries Server2 Top 10 processes.

Questions:

  1. Since Notifications EXEs are located on the PRTG Server we have to make the EXEs take in parameters such as hostname/IP right ?
  2. What are their placeholders (IP and hostname) to put into the EXE parameter box?
  3. And what is the placeholder for the individual channel names that has the threshold trigger?
  4. The sensor "System Health" has CPU/Memory channels in one sensor so to pass the right 'type' of error into the EXE I need to know the channel name that had its threshold trigger triggered, not just "System Health" sensor name.
  5. Is it possible to disable the System Health sensor? I want to add separate sensors for CPU and Memory and having System Health makes it redundant and put unnecessary strain on the system.

Thanks!


Article Comments

As for your questions:

  1. Exactly :)
  2. Have a look at the available placeholders in PRTG.
  3. There's none, you can only get the corresponding sensor that triggered the notification. You could use the API to get some channel information however. Not sure how one would correlate the notification info with the channel, though; you could parse the channel message for a name, but it may lead to ambigious results.
  4. See #3...
  5. Simply pause them indefinitely.

Let me know if I can be of any further assistance!


Aug, 2016 - Permalink

Hi,

Thanks.

Does PRTG probes do anything in terms of running scripts?

All they do is send data back and run the custom sensor scripts ?

Any plans of adding features to what the Probe can do?

Can we use nsclient++ or something to get more data?


Aug, 2016 - Permalink

The probe where the sensor runs actually runs the script behind the sensor. What would you like to have added in terms of features? NSClient++ currently is not supported, feel free to modify the scripts to suit the output necessary for PRTG (<your-prtg>/api.htm?tabid=7).


Aug, 2016 - Permalink