reporttool
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
reporttool [2007/10/01 16:18] faltin old revision restored |
reporttool [2009/03/03 12:54] jorabra Update configuration info. |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== The report tool ====== | ====== The report tool ====== | ||
| - | {{tools:report.png| }} The report tool presents a number of reports with information from your network. The report tool also links to the IP device center, to the "IP address scope - graphical view" and the services - graphical view. | + | {{tools:report.png| }} The report tool presents a number of reports with information from your network. The report tool also links to the "IP address scope - graphical view" and the services matrix. |
| Each NAV report is in essence an SQL query to the database. It shown its data in a number of columns. The | Each NAV report is in essence an SQL query to the database. It shown its data in a number of columns. The | ||
| data is in many cases also hyperlinks to other reports or other tools in NAV. The whole report system | data is in many cases also hyperlinks to other reports or other tools in NAV. The whole report system | ||
| is highly configurable, the basis for the system is the configuration file report.conf. Details on | is highly configurable, the basis for the system is the configuration file report.conf. Details on | ||
| - | the configuration is provides below. | + | the configuration is provided [[#report.conf|below]]. |
| ===== Reports ===== | ===== Reports ===== | ||
| Line 12: | Line 12: | ||
| An example report showing all your network equipment sorted by type: | An example report showing all your network equipment sorted by type: | ||
| - | {{screenshot:equipmtypes.png?800|The equipment type report}} | + | {{screenshot:3.3:equipmentypes.png|The equipment type report}} |
| From this report you can drill down on a particularly type and see the number of devices you have of this | From this report you can drill down on a particularly type and see the number of devices you have of this | ||
| Line 24: | Line 24: | ||
| * The search bars on top are shortcuts to interesting reports. The room searc lets you go directly to a room of interest. You may also search for a particular port name, or you may dive directly into the IP device center of a device in interest. | * The search bars on top are shortcuts to interesting reports. The room searc lets you go directly to a room of interest. You may also search for a particular port name, or you may dive directly into the IP device center of a device in interest. | ||
| - | ===== IP Device Center ===== | ||
| - | |||
| - | The IP device center is a dashboard for a given device showing relevant information. It presents | ||
| - | recent events for the device, if any. If the device is a switch or router a switch port and/or | ||
| - | router interface view is given. | ||
| - | |||
| - | {{screenshot:devcenter.png?800|IP device center }} | ||
| ===== IP address scope - graphical view ===== | ===== IP address scope - graphical view ===== | ||
| Line 36: | Line 29: | ||
| For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful to have an overview of all the subnets in operation, and whats more, how full they are, i.e. how many machines do they contain. NAV introduces a tabular view that gives an excellent overview on a single page: | For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful to have an overview of all the subnets in operation, and whats more, how full they are, i.e. how many machines do they contain. NAV introduces a tabular view that gives an excellent overview on a single page: | ||
| - | {{screenshot:prefixmatrix.png?800|The prefix matrix }} | + | {{ screenshot:3.3:prefixmatrix.png?700 |The prefix matrix }} |
| ===== Service matrix ===== | ===== Service matrix ===== | ||
| Line 42: | Line 35: | ||
| This tool is quite simple and only useful if you use the NAV service monitor to an extent. It displays | This tool is quite simple and only useful if you use the NAV service monitor to an extent. It displays | ||
| all servers and services in a matrix showing operational status. | all servers and services in a matrix showing operational status. | ||
| + | |||
| Line 47: | Line 41: | ||
| ====== Configuration ====== | ====== Configuration ====== | ||
| - | As mentioned the report system is higly configurable, you can alter the configuration file report.conf. | + | As mentioned the report system is highly configurable, you can alter the configuration file "report.local.conf", either adding new reports or overloading existing reports that exists in "report.conf". |
| - | In NAV 3.4 we will strengthen the means of editing reports by adding support for local reports, | + | |
| - | see [[devel:tasklist#smj3improve_the_report_tool|Task SMJ3]]. | + | |
| ==== report.conf ==== | ==== report.conf ==== | ||
| - | The NAV reports are made based on the ''report.conf'' configuration file. One can expand this file | + | The NAV reports are made based on the ''report.conf'' configuration file. You can expand this file |
| - | with new reports as one likes. Each report is in essence an SQL-query to the database (with some | + | with new reports as you like. Each report is in essence an SQL-query to the database (with some |
| - | limitations). It is easy to make hyperlinks from data in the report to other reports or elsewhere. | + | limitations). It is easy to make hyper links from data in the report to other reports or elsewhere. |
| An example report is given, this is the router port report: | An example report is given, this is the router port report: | ||
| Line 107: | Line 101: | ||
| Further explanation of the report.conf syntax: | Further explanation of the report.conf syntax: | ||
| - | |||
| Line 119: | Line 112: | ||
| | $hide |columns that must be included in the $sql because they are used in $url. $hide will not show the column in the report. | | | $hide |columns that must be included in the $sql because they are used in $url. $hide will not show the column in the report. | | ||
| | $extra |extra "static" columns at the right that can be used for hyperlinks | | | $extra |extra "static" columns at the right that can be used for hyperlinks | | ||
| - | | $sum |shows the total of a given column (may not work...)| | + | | $sum |shows the total of a given column (currently not working)| |
reporttool.txt · Last modified: 2011/04/03 17:28 by faltin
Page Tools
