PRTG Network Monitor - Libraries
Hello and welcome to this video about Libraries. My name is Kimberley Trommler and I am in Presales at Paessler.
PRTG Libraries are a method for you to build additional customized views of your device tree, arranged anyway you like. The libraries show the same monitoring data aas your main device tree, updated in the same scanning intervall but with the sensors organized in the different groupings. You could, for example, build libraries for certain target groups like for individual departments. Or you could build libraries for specific services such as email or for your web shop.
Using libraries you can mix and match groups, devices and sensors from different probes and different branches of the main tree. To group them together into as many logical views as you would like. You can also filter based on sensor type, status, tags or priority. PRTG comes with several preconfigured libraries such as all bandwidth sensors or CPU load sensors or all disk space sensors. In this video we are going to add two new libraries, using drag and drop, to demonstrate how to use a library and how to filter.
For a first example, we gonna create a library for a webshop which includes both - the active shop infrastructure and the backup infrastructure. We start by creating a new library and giving it a name. And I leave the rest as default now. In this view we can now start to structure a new library. Let's say we decide to group the devices and sensors into three main groups. The active infrastructure, the backup infrastructure and the shared database. So we create three groups now. And then rename the groups into something remainingful, you just rightclick and choose and edit "rename". This can be our main infrastructure and then our backup infrastructure and our shared storage. So we can now add devices to these tree groups by using drag and drop. First we are on our main webserver which is here - and I'll just drag it into the main infrastructure group. And then my backup webserver into the backup infrastructure.
Now since each of these webservers is attached to a different switch we'll add the two different switches. One for the main group and one for the cisco switch and one for the backup infrastructure. And each webserver is going over a different firewall. We now need to add the correct firewall to each group, too. Here is our active firewall and the sonic wall is our backup firewall. And finally we'll add a NetApp san. as our shared storage. So we now have all the devices we are interested in collected into one library. We can edit the library a littlebit so that the names are more meaningful. So for example this is a firewall, then we name it that.
This one is our active networking and this is our webserver. And I'll do the same thing for the backup infrastructure. This is a firewall and this is networking and this is the web server. And the NetApp is our san. So we got them all labeled now. If you'd like to reorder them, for example so that the webserver is at the top of the list rather than at the bottom, then you can just rightclick on it and choose "move to top" for example. And now the webserver is at the top. I think I'll do the same thing with this webserver so that they're similar. And when we now switch back to the overview tab we have the library showing only the devices and sensors that are relevant for the status of our web shop.
Let's now create a second library. This time using filters to select specific sensor types. So I will add another new library. And this time we're gonna collect all sensors that are relevant to quality of service. So I'll call my library "all QoS Sensors" and click continue.This time, rather than selecting the individual devices, I'll copy the entire local probe. This now shows all of the sensors on the probe at the moment but we only want to see the quality of service sensors. So we now need to filter out the rest. To do this rightclick on the note and choose "edit" settings.
We can rename the note here but more importantly we can now choose to "Show a collection of filtered sensors in the library". And when I click on that it gives me five options that I can use as filters. You can filter based on the node type, the sensor type, by status, tags or by priority. For our example, today we're gonna filter by type of sensor so that we can select all the quality service sensors. So I will choose to show specific sensor types only and I now get a list of all sensor types I have. I'll go through and find all of the QoS related ones. This one is one, and the Quality of Service one way and the Quality of service roundtrip and there is one more. There is the SNMP Cisco CBQoS sensor.
So I've now selected all the different Quality of Service related sensors that I have. I click ok and we wait for it to filter and rebuild the tree. So we now see all the Quality of Service sensors we got and when we switch back to the overview, we now have a library with Quality of Service sensors. There is one more thing I'd like to mention about libraries which is that you can configure settings and notifications at the library level. Similar to the options you have in the main device tree. For example under settings
You can configure different user access rights for each library to control who can read or edit the library. Independent of the user rights you have set in your main device tree. And for example you could create a notification that applies only to this library.
So if there is an error of this Quality of Service sensors, you can send an email to one department that is responsible for your service - even though these sensors were collected from different branches of your main tree. This lets you structure your configuration and notification in as many different types of hirachies as you need.
You can do some notifications based on your main device tree which might be organised by location and then your additional notifications in your libraries which might be organised by service.
This brings us to the end of this video. Thanks for watching!
If you have any questions about libraries or anything else in PRTG, please contact us at any time under [email protected]!
Thanks and Goodbye!