Custom XML Reports

Introduction

Many of the Network Monitor products available today include pre-formatted, standard reports, and Custom reports can be desinged on demand.

ActiveXperts has a different approach by providing XML/XSL based reports.
XML files are used for describing the report data, while XSL Stylesheets are used for formatting the report.
If you are used to HTML, formatting a report through XSL will be pretty easy.

The 'Detailed Availability Reports' and 'Availability Summary Report' can be customized only when using the XML-based Report format, with an XSL Stylesheet linked to it.

All customizations are made by modifying the XSL Stylesheets, like:

Including/excluding rules from the report;
Different sorting in the report;
Including/excluding columns from the report;
Changing HTML tags, like titles, tables, colors, sizes, etc.

By default, two XSL Report Stylesheets are delivered with the product:

AvailabilityDetails.xsl - default XSL Stylesheet for XML based 'Detailed Availability Report';
AvailabilitySummary.xsl - default XSL Stylesheet for XML based 'Availability Summary Report'.

Use a normal Text editor to make changes to the XSL Stylesheets. The default AvailabilityDetails.xsl and AvailabilitySummary.xsl stylesheets can be found in the \Server\XmlReports directory.

For those who are new to XML and XSL, it's recommended to visit the W3Schools Online Web Tutorials site and read the XML and XSL chapters.

Tags in the 'Detailed Availability Report' Report

The following tags are reported in the 'Detailed Availability Report' XML report and can be used in the related XSL Stylesheet file:

Tag	Description
<from-secs>	Begin time of report, in seconds after 01/01/1970
<from-date>	Begin time of report, in date format (i.e. mm/dd/yyyy)
<to-secs>	End time of report, in seconds after 01/01/1970
<to-date>	End time of report, in date format (i.e. mm/dd/yyyy)
<rule/id>	ID of the Rule, as it is used throughout the whole program
<rule/displayname>	DisplayName of the Rule, as it is used throughout the whole program
<rule/event/from-secs>	Begin time of the event, in seconds after 01/01/1970
<rule/event/from-date>	Begin time of the event, in date format (i.e. mm/dd/yyyy)
<rule/event/from-time>	Begin time of the event, in time format (i.e. hh:mm:ss)
<rule/event/to-secs>	End time of the event, in seconds after 01/01/1970
<rule/event/to-date>	End time of the event, in date format (i.e. mm/dd/yyyy)
<rule/event/to-time>	End time of the event, in time format (i.e. hh:mm:ss)
<rule/event/result>	The last Result of the Rule, represented by a string
<rule/event/result-id>	The last Result of the Rule, described by a unique number. The Result ID's are described later in this chapter
<rule/event/duration-secs>	Duration of the event, in seconds
<rule/event/duration>	Duration of the event, formatted as: 'xx hrs yy min'

Tags in the 'Availability Summary Report' Report

The following tags are reported in the 'Availability Summary Report' XML report and can be used in the related XSL Stylesheet file:

Tag	Description
<from-secs>	Begin time of report, in seconds after 01/01/1970
<from-date>	Begin time of report, in date format (i.e. mm/dd/yyyy)
<to-secs>	End time of report, in seconds after 01/01/1970
<to-date>	End time of report, in date format (i.e. mm/dd/yyyy)
<rule/id>	ID of the Rule, as it is used throughout the whole program
<rule/displayname>	DisplayName of the Rule, as it is used throughout the whole program
<rule/success-secs>	Total amount of time (in seconds) that Rule had status: Success
<rule/success-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Success
<rule/success-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Success
<rule/failure-secs>	Total amount of time (in seconds) that Rule had status: Failure
<rule/failure-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Failure
<rule/failure-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Failure
<rule/uncertain-secs>	Total amount of time (in seconds) that Rule had status: Uncertain
<rule/uncertain-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Uncertain
<rule/uncertain-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Uncertain
<rule/depfailure-secs>	Total amount of time (in seconds) that Rule had status: Dependee Failure
<rule/depfailure-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Dependee Failure
<rule/depfailure-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Dependee Failure
<rule/maintenance-secs>	Total amount of time (in seconds) that Rule had status: Maintenance
<rule/maintenance-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Maintenance
<rule/maintenance-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Maintenance
<rule/onhold-secs>	Total amount of time (in seconds) that Rule had status: On Hold
<rule/onhold-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: On Hold
<rule/onhold-pct>	Total amount of time (in percentage of total Report time) that Rule had status: On Hold
<rule/notprocessed-secs>	Total amount of time (in seconds) that Rule had status: Not Processed
<rule/notprocessed-hrsmin>	Total amount of time (in hh:mm format) that Rule had status: Not Processed
<rule/notprocessed-pct>	Total amount of time (in percentage of total Report time) that Rule had status: Not Processed

Network Monitor Data Types

Type ID's (also called: Function ID's):

Type ID	Description
0	<UNDEFINED TYPE>
1	<FOLDER>
10	ICMP
20	Disk Space
30	TCP/IP
31	DisplayName of the Rule, as it is used throughout the whole program
32	SMTP
33	HTTP(s)
34	FTP
35	RSH
36	DNS
37	SNMP
38	NNTP
39	IMAP
40	NTP
50	Service
60	File
90	Event Log
100	VBScript
110	ODBC
111	ADO/SQL
112	Oracle
120	MS Terminal Server

Result ID's

Result ID	Description
0	Uncertain
1	Success
2	Error
3	Failure
4	Maintenance
5	On Hold
6	Dependee Error
7	Dependee Failure
99	Not Processed