The following tables can help you monitor the status, performance and internal processes of the machines in charge of generating and sending events to Devo. This may be useful in case you have performance problems and want to know what's causing them or simply to statistically analyze the different internal processes to get an overview on machine resources destribution. These tables are the source of information used by the Systems Monitoring application to analyze and graphically represent machine performance. For these tables to receive data, the Devo-system and the Devo-monitor must be installed (click here to know how).
box.stat.unix* / box.stat.win.*
These tables collect information about different performance aspects of the different Linux/Unix and Windows machines involved in sending and receiving events. There are several tables, each of them focused on a specific aspect:
box.stat.unix.diskstat / box.stat.win.diskstat
These two tables collect information about different disk parameters that reflect the disk status of the different Linux/Unix and Windows machines involved in sending and receiving events. These tables present the same structure, which consists of the following columns:
Number of reads issued.
Number of reads merged.
Number of sectors read.
Time in milliseconds spent reading.
Number of of writes completed.
Number of writes merged.
Number of sectors written.
Time in milliseconds spent writing.
Number of I/Os currently in progress.
Time in milliseconds spent doing I/Os.
Weighted time in milliseconds spent doing I/Os.
File system block size.
Number of free blocks.
Number of free blocks for unprivileged users.
Number of inodes.
Number of free inodes.
Number of free inodes for unprivileged users.
box.unix / box.win
These table collect information about system events generated by different Linux/Unix and Windows machines. These are very complex tables that display many different aspects of system events, so you will rarely find all columns relevant. This relevance will be determined by the purpose and scope of your analysis. To reduce the magnitude of the table and adapt it to your needs, you can get rid of the columns deemed irrelevant before opening the table (click here to know how).