Reports

Fault Management Reports: Includes Event History, Service Instability report, Device Instability, Threshold Violations

Performance and Capacity Planning: Top N usage and trend report, 30 Day upcoming trends

SLA Reports: Unavailability, Downtime

Stored/Scheduled Reports: Modify, Execute or delete queries

13.1 Preset Reports

These reports give operational and engineering analysis of your IT infrastructure and answer some commonly asked questions.

13.1.1 Operational Reports

What problems or events occurred within the last 24 hours?

Which devices have the most problems, and what are those problems?

Where are network problems occurring?

What are the most problems on entire IT infrastructure?

Which devices have bandwidth, disk, CPU problems?

What detailed information is available for each monitored element?

13.1.2 Planning & Performance

Which servers are most utilized?

Which servers are least utilized?

Which disks are closest to filling up?

Which disks, CPU, and links are NOT utilized?

What CPU, bandwidth, or disk problems are projected for the next 30 days?

How many days will it take for monitored elements to reach established threshold levels?

These Reports help you plan and target your IT infrastructure investments by showing where capacity restraints are causing performance bottlenecks.

Gives useful data on the capacity planning for creating redundant capacity where required and removal of excess capacity where it is not required by reporting on TOP N devices or Tests by highest or lowest usage values. This report can be based on the status of one or more test types.

For Bandwidth, CPU and Disk Space utilization give a trend analysis for next one month and allow you to plan accordingly.

13.1.3 End-to-end Service Reports

Service Outages

Service Health Report

13.1.4 SLA Reports

SLA thresholds, which are distinct from the thresholds monitored by End-users, enable Administrators to get additional information about system performance without creating additional tests. (They are called SLA thresholds because they were designed to allow administrators to see whether Service Level Agreements are being met.)

SLA thresholds are configured by a NetVigil Administrator at the User-Class level (MANAGE | User-Class | SLA Thresholds and Actions). When a polled result crosses an SLA threshold, it triggers an SLA violation event. A single result that crosses both a user threshold and an SLA threshold generates two events.

For example, assume that the head of the IT department for an organization has an SLA that guarantees that response time on the network will stay below 50 ms. To check this, she sets the SLA threshold for Round Trip Time tests to 50 ms. At the same time, an End-user creates a Round Trip Time test for one of his servers. He finds any RTT below 75 ms acceptable, so he sets the Warning and Critical thresholds to 75 and 85 ms, respectively. During one polling interval, the recorded Round Trip Time is 65 ms. Because this falls below the End-user thresholds, it does not trigger a user event, and if the End-user runs a device instability report, the server does not appear. However, the polled result does exceed the SLA threshold, so an SLA violation event is recorded. If the Administrator runs an event report against SLA thresholds, she will see that Departments associated with this User-Class are not getting the performance promised in the SLA.

The Unavailability/Downtime SLA Report is based on device availability as measured by the ICMP packet loss test. The report shows how many times and for how long Packet Loss tests were in the Critical or Unreachable states when compared with the SLA threshold. It shows the Top 10 devices by amount of "unavailability", displaying total time unavailable and % unavailable, with graphics showing either view.

Users may link to an availability distribution report/graph as well. This histogram is a distribution of the numbers of devices falling into blocks of 10% availability. That is, it displays the number of devices falling between 0-10% availability, 10-20% availability, and so on.

The Threshold Violation report allows you to run reports on system resources (CPU, disk space, bandwidth, etc.), comparing test results with SLA thresholds.

13.2 Custom Reports

In addition to the large number of preset reports listed above, NetVigil offers complete flexibility in creating ad-hoc reports over any time period.

Generates one or more of the Top Ten, Number of Events Distribution, Event Duration Distribution, Number of Events, Performance, Statistics, Trend Analysis reports for the particular tests of chosen test types for a device.

Generates reports for one or more of Top Ten, Number of Events Distribution, Event Duration Distribution, Number of Events for devices of a particular vendor and Device type.

Features the event distribution against time reports for chosen types of Tests or a particular device.

Short Graphical Reports for last 24 hours 5-minutes interval for a particular test/device or types of tests chosen

Plots reports for the similar tests on a single graph allowing comparison of performance.

The reports are broadly categorized into two types, Fault/Event and Performance, which are described in the sections that follow.

13.2.1 Fault/Event Reports

These reports use events (or threshold violations) to calculate the number of times or the total time spent in warning or critical conditions. These reports answer questions such as:

Availability: what was the total time for which monitored elements were unavailable?

How many outages occurred?

What was the average time of an outage (MTTR)?

The Fault Management Reports provide an in-depth and rigorous analysis of the events where tests/devices and services crossed thresholds. They provide Device and Service reports on the most fault prone services and the number of events that occurred.

is designed to provide a consolidated view of events for either the last 24 hours or for a specific historical month. Each report entry is a unique combination of device name, test name and severity, detailing both the total duration in the specified severity (i.e. CRITICAL, WARNING, etc.) and the number of times that the test entered that severity. Below the text listing is a graphical display of the top 10 'worst' results in a horizontal bar style. Clicking on any of the column headings for the text list will automatically update this graph.

provides reports on top 10, 25 or 50 services affected by number of events. The report consists of the Frequency distribution of the events during each hour of the day, each day of the week/month and duration of events.

Are the most important reports that allow you useful data on threshold Violations for Bandwidth, CPU, Memory and Disk Utilization.

13.2.2 Performance

These reports are based on the raw data samples and are aggregated over time according to your aggregation scheme. They are used to:

Calculate statistics such as mean, max, percentiles

Generate trend reports using regression analysis to predict the number of days before thresholds will be reached.

13.3 Sample Reports

13.3.1 Main Report Generation Page

13.3.2 Top N Problems across IT Infrastructure

This report pinpoints the main problems across the entire IT infrastructure by calculating the total time they were in Critical or Warning stage.

13.3.3 Most Critical Devices on Network

This report identifies network devices that have had the most alarms (events). It also shows the distribution of alarms on a daily basis as well as the distribution over the day of the week and hour of day. You can drill down into a device and see all the individual problems on that device and also see trend reports from the same screen.

13.3.4 Drill Down on Disks on a Device

13.3.5 Upcoming Disk problems in Next 30 days

13.3.6 Network Reports

13.3.7 Service Health and Impacting Components

This report shows a 24 hour snapshot of all the individual components of a service or a device. If a particular test has gone into any non-OK state within an hour, that hour is colored to reflect the non-OK state.