Hello everyone, In a matter of monitoring/listing our database servers by their version, I am trying to create a library by filtering by device tags. It would be extremely useful for our division to see all our servers in alternative views in PRTG.

But from what I read/tested, PRTG libraries only allow to create groups, where nodes display only sensors. In other words, I can't figure out how to display a whole device tree in a library when applying device tag filters. It is difficult to explain without visuals...

Example: In this case, the device tags are SQLServer2012; SQLServer2014; etc

-SQL Server Versions (Library)

--SQL Server 2012(Group)

-----Device1 (and not only sensors)

-----Device2 (and not only sensors)

--SQL Server 2014(Group)

-----Device3 (and not only sensors)

-----Device4 (and not only sensors)

Article Comments

I would tell you to make a Map of this before a Library. The Library isn't near as versatile as a Map would be for this application.

With the Map you can use the Device Tree map object linked to each device, and see just the sensors on each device. Then you can group those accordingly.

Does this make sense?


Mar, 2018 - Permalink

Thanks for your answer Benjamin.

The best solution would be based on tags, because the devices would appear automatically after their creation and therefore the maintenance of the list very reduced.

We would love to have custom lists of devices based on their tags and we thougth libraries would be the the way to go.

I tried some device tree maps but i can't figure out how to get a clean tree with only the devices needed. Is there any way to add devices based on their tags instead of adding them one by one? It would be tedious to add drag hundreds of devices in a map.

Thanks again!


Mar, 2018 - Permalink

I tested this in my lab, and unfortunately, we do not have this capability with devices in a Library.

But I like this idea, so I'm going to add a ticket for our devs to look into adding this.

Can you open a support ticket? Ask for me, and reference KB78736. I'll make the feature ticket, and link it to the support ticket.

Thanks!


Mar, 2018 - Permalink

Here is the support ticket number: PAE1016580 Thank you Benjamin!


Mar, 2018 - Permalink

Was this accepted as a feature? If so, what's time timeline for implementation?


Oct, 2018 - Permalink

Kevin,

Sorry, no update at this time.

Benjamin Day
Paessler Support


Oct, 2018 - Permalink

Chiming in to support this notion - nimskev35's suggestion would benefit many other members in my implementation of PRTG, too.


Oct, 2018 - Permalink

Hi guys,

The best way to help push this would be to open a feature request with our new form.

PRTG Feature Requests

Thanks!

Benjamin Day
Paessler Support


Oct, 2018 - Permalink