New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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


[OPEN] PING for designated devices that do NOT count against Sensor Available total

Votes:

1

Your Vote:

Up

Down

Want this feature implemented, too? Please upvote by clicking Thumbs up! (Posts as a reply won't be published in this feature request thread. Read Me!)

User Story

As a PRTG User, I would like to see the existing PING Sensor not count against Sensor Available total. As someone who primarily supports small businesses (less than 20 devices), PRTG is an exceptional solutions to monitor important aspects of the network and server infrastructure. However, sometimes I just need to know if an end user device (desktop/laptop/tablet/smartphone) is up or down, connected or not, "ping" yes or no... etc. Even the investment of $1750 (plus $435 a year after at current pricing) for 500 sensors is high for small businesses (plumber, electricians, salons, restaurants, boutiques, etc.). As more services are shifting to the cloud, we still need to know if end user devices are up or down.

There are many free and/or easy ways to get a ping result back from an IP Device. Anyone with minimal experience with pretty much any scripting language could create one themselves. But having that monitoring and "real devices" in the same pane of glass is really valuable. It also helps us provide data to our clients in a simple and effective manner.

For these reasons, I believe a simple device ping should not count as a "Sensor" or there should be an alternative up/down option that is excluded.

Acceptance criteria

  • Criteria #1 - The existing PING Sensor not count against Sensor Available total or at least [or]
  • Criteria #2 - A second type of PING Sensor that reported the same status and but did not count against Sensor Available total. This sensor could lock a device so that no other sensors can be added. The administrator would have to convert this device to the default PING Sensor in order to add other sensors and at that point, the PING sensor would then count against the Sensor Available total. [or]
  • Criteria #3 - A special group type that would be locked down to only apply the existing PING Sensor. This group would have all member's PING Sensor excluded from Sensor Available total.

Status

Open

add-feature add-sensor improve-prtg prtg-kbtracker

Created on Apr 18, 2020 11:31:52 PM by  Adam (1) 1

Last change on Apr 20, 2020 4:10:47 AM by  Sven Roggenhofer [Paessler Technical Support]



Replies

Nobody has replied yet

Why not be the first?

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.