2 results found

1. Organize Probes by Division and Groups for Better Management

   As a network administrator at a large company with multiple sub-divisions, I want to organize probes into hierarchical groups by division so that I can better manage and navigate our monitoring infrastructure.
   Division 1
   ├── Probe 1
   │ ├── Group 1
   │ │ ├── Device 1
   │ │ │ ├── Sensor 1
   │ │ │ └── Sensor 2
   │ │ └── Device 2
   │ └── Group 2
   ├── Probe 2
   └── Probe 3

   Division 2
   ├── Probe 1
   ├── Probe 2
   └── Probe 3

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   Thanks for submitting your idea, to Paessler! We really appreciate you taking the time to share your feedback and help us improve our products.

   
   

   Your idea has been successfully received and is now in our review queue. Our team will carefully evaluate it, and we'll keep you updated on its status.

   
   

   In the meantime, feel free to share your idea with others to gather more support and comments. The more input we get, the better!

   
   

   Thanks again for your contribution.

   
   

   Best regards,

   The Paessler Product Team

2. Master Sensor for parent should not be a toggle but a shortcut

   The use of the "Master sensor for parent" precludes having a dependency on the ping (sensor) since the option to bind the sensor as the parent's dependency prevents setting a dependency on the sensor.

   The same can be implemented on the parent device by selecting the child sensor as the dependency, thus freeing the ping up to be dependent on say, a DNS check.

   The master sensor for parent, shouldn't be a toggle or prevent setting a dependency on the sensor, but should be a shortcut/script button, which when clicked, would set the dependency on the parent as the sensor which it's set as parent dependency button was pressed. If a different sensor's parent dependency button is pressed, there should be a dialog that the dependency on the parent is set and if they confirm the overwrite.
   The sensor settings screen for dependency should not clear the parent's dependency, since that is also tied to schedule and reverting to inherit, instead of previous settings, is a blind change.
   Currently the sensor/settings/Schedules, Dependencies, and Maintenance Window, Dependency Type / Master sensor for parent, is a blind, non-confirmed change to the parent. If the parent has a schedule, maintenance window or a set dependency using this function will update the settings without notice, warning or confirmation.

   Additionally, if the master sensor for parent is selected, and then on the parent device, the dependency is changed, the sensor still shows that master sensor for parent is selected, but does not function.

   The documentation needs to be a bit clearer on the side effects of using the feature

   The use of the "Master sensor for parent" precludes having a dependency on the ping (sensor) since the option to bind the sensor as the parent's dependency prevents setting a dependency on the sensor.

   The same can be implemented on the parent device by selecting the child sensor as the dependency, thus freeing the ping up to be dependent on say, a DNS check.

   The master sensor for parent, shouldn't be a toggle or prevent setting a dependency on the sensor, but should be a shortcut/script button, which when clicked, would set the dependency on the parent as the sensor… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminJonah Kowall (SVP Product and Design, Paessler) responded

   Thanks for submitting your idea, to Paessler! We really appreciate you taking the time to share your feedback and help us improve our products.

   
   

   Your idea has been successfully received and is now in our review queue. Our team will carefully evaluate it, and we'll keep you updated on its status.

   
   

   In the meantime, feel free to share your idea with others to gather more support and comments. The more input we get, the better!

   
   

   Thanks again for your contribution.

   
   

   Best regards,

   The Paessler Product Team