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

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 Download

Top Tags


View all Tags

Only receive notifications for Ping Sensors down

Votes:

0

Your Vote:

Up

Down

My problem is identical to this thread from 9 years ago: https://kb.paessler.com/en/topic/25383-disable-notifications-for-all-sensors-except-most-critical

In essence, we want to receive email notifications for when a Ping sensor goes down in a specific group. Our first strategy for this was to use a filtered library, but that currently isn't an option due to this bug: https://kb.paessler.com/en/topic/88764-collection-of-flitered-sensors-ignores-bypasses-linked-object

The only other option we've thought of that might work, is manually adding every single ping sensor in that group to a library, node by node. This obviously isn't really optimal, obviously, and I was wondering if anyone knew of a better method to achieve our goal (until the issue with library filters and/or tag inheritance is resolved).

Also note that we do have Ping sensors set as the master sensor/dependency, the issue is not that we get several notifications when a device goes down, but rather that we only care about notifications from Ping sensors and nothing else.

filtering inheritance library notification notification-email notifications ping-sensor tags

Created on Nov 4, 2020 4:29:37 PM by  csparks1 (0) 1



3 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

If I'm not mistaken, the issue should indeed be resolved in 20.4.63.1427:

Library FiltersFilters in libraries properly work again. In the previous PRTG version 20.4.63.1412, filtering on a Linked Object did not work. A library node always showed all sensors of a PRTG instance that matched the filter, not only matching sensors of the linked object. Furthermore, Filter by Tags had issues with correct filtering so that the library node showed wrong or no sensors in some scenarios.

is that what you have running currently?

Created on Nov 5, 2020 5:04:51 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Woops, yes we hadn't yet updated. Thanks for pointing that out.

Created on Nov 5, 2020 5:25:16 PM by  csparks1 (0) 1



Votes:

0

Your Vote:

Up

Down

Awesome :) Great to hear that it's now resolved. Have a great weekend ahead!

Created on Nov 6, 2020 8:58:04 AM 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.