On the PRTG Status page, I can find, amongst many other things, a lot of parameters regarding the core system memory. What do they mean?
This article applies to PRTG Network Monitor 16 or later.
PRTG Core System Memory Parameters
As an IT pro, you know that managing the memory of your systems is essential for almost everything. That is why prompt information about your system memory usage is always useful. Instead of flipping through your whole system to collect the PRTG related data you need, PRTG has information ready for you.
Note: The information you get refers to the PRTG core server. If you run a PRTG cluster, the information refers to the cluster node you are currently logged in to.
Path And Parameters
Where do you find the memory usage information? Go to Setup | PRTG Status in the PRTG web interface and scroll to Core System Memory.
PRTG currently shows the following 31 parameters:
|1||Committed||The amount of memory that your system commits to the PRTG core.|
|2||Allocated||The amount of memory that the PRTG core is currently using.|
|3||Unused||The amount of allocated memory that PRTG currently is not using.|
|4||Free Physical||The amount of free memory currently available on your core system’s physical memory.|
|5||Total Physical||The total amount of memory provided by your core system’s physical memory.|
|6||Free Pagefile||The amount of free memory currently available in your system’s pagefile(s).|
|7||Total Pagefile||The total amount of memory of your system’s pagefile(s).|
|8||Free Virtual||The amount of free memory available in your core system’s virtual memory.|
|9||Total Virtual||The total amount of memory of your core system’s virtual memory.|
|10||Free Effective||The effective amount of free memory on your core system. Corresponds to Free Pagefile.|
|11||Object Count||Number of PRTG internal data structures, also known as tree nodes, for example, number of sensors + users + reports.|
|12||BaseInstance||Amount of memory used for the tree node Instance.|
|13||BaseAccess||Amount of memory used for the tree node Access Rights.|
|14||BaseHistory||Amount of memory used for the tree node History of Configuration Changes.|
|15||BaseCurrent||Amount of memory used for the tree node Current Configuration Information.|
|16||BaseData||Amount of memory used for the tree node Configuration Data.|
|17||BaseChannel||Amount of memory used for the tree node Channel Settings.|
|18||BaseTrigger||Amount of memory used for the tree node Trigger.|
|19||BaseIDs||Amount of memory used for the tree node IDs.|
|20||BaseLookup||Amount of memory used for the tree node Sensor Lookups.|
|21||BaseCheck||Amount of memory used for the tree node Check Requests.|
|22||BaseDeplist||Amount of memory used for the tree node Dependency List.|
|23||Datasets||Amount of memory currently used for datasets, like for graphs.|
|24||State||Amount of memory currently used for user specific datasets.|
|25||Interface||Amount of memory currently used for tree node specific table objects.|
|26||IndexCache||Amount of memory currently used for the index dataset cache, which is especially important in a cluster.|
|27||TreeTotal||Total amount of memory used by the PRTG tree.|
|28||DatasetCache||Amount of memory currently used for the dataset cache, concerning especially historic data. In brackets you see the number of datasets saved in the cache.|
|29||StorageSystem||Amount of memory space currently used for the storage system.|
|30||Sessions||Amount of memory currently used for sessions. A user can activate more than one session. In brackets you see the number of currently activated sessions.|
|31||StateObjects||Number of user specific state objects found in your core system’s memory.|