How to use the monitoring report

Back to news

The objective of this report is to be able to highlight the devices and/or services of one or more host(s) that regularly trigger alerts.

It is therefore necessary to review the hosts / unit services that regularly have issues, to attempt to reduce monitoring alerts or false positives.

For that, its useful to consult the following report: Monitoring data summary .

Using the report

This report is available in the Configuration / Reporting menu.

Report parameters:

Type: reporting

  • Title: The title of the report
  • Visibility: make this report public or private
  • Type: Report
  • Template: “Monitoring data summary”
  • Period: choose the number of days to analyze 7, 30 or 90 days
  • Until: end date of the analysis. eg. 16/09/2018 with a period of 7 days. This will analyze the 7 days preceding the 16/09/2018.
  • Ending: x days before report generation. Use this if you chose to schedule this report. eg. the report is weekly every Monday.

The analysis will be performed on a period x days prior to Monday.

Company / Site: choose the desired filter

Hosts: choose the desired filter

In the example above, we only take Windows servers

Services: select the filter

In the example above only disk space checks are considered.

Sending Policy: select language and delivery method

Use case – reduce false positives

Objective: to eliminate false positives that have been highlighted in the analysis.

We run the report manually and analyze it in Excel. To do this, in the Monitoring / Reports menu, select the report and click on the download arrow on the right of the screenshot

Analysis of the produced file

The resulting file is in Excel format and contains the following columns:

– Partner / Customer

– Company / Site

– Host

– Unit service

– Availability rate

– Objective

– Number of transitions to critical

– Number of transitions to warning

– Number of transitions to unknown

– Number of transitions to indeterminate

– Time in Critical

– Time in Critical (in seconds)

– Time in Alert

– Time in Alert (in seconds)

– Time in unknown

– Time in unknown (in seconds)

– Time in indeterminate

– Time in indeterminate (in seconds)

 

What interests us most will be the number of transitions to a Critical state.

Here, we notice that my Disk-space has changed state 11 times over the period defined in my report.

 

Verification in ServiceNav

When I look at my thresholds I may conclude that they are too low, resulting in the critical transition.

I choose to modify them to avoid having notifications about this check in future.

This report is therefore very useful in giving an overview of services or hosts that change status regularly. It makes it possible to adapt thresholds based on the analysis carried out.

UK ServiceNav Product Development Manager; my priority is to be needful of the particular requirements of all ‘English-speaking’ markets where ServiceNav is sold. I have over 20 years experience of the IT monitoring field - covering a wide variety of products and technologies.

More recent posts from the Servicenav team

17/5/19

ServiceNav 3.19 – SNMP TRAPS – News / Plug-in Updates

In Brief SNMP TRAPS, in addition to using polling as a source of alerts Some devices offer, through their SNMP MIBs the ability to send… Read more

15/5/19

On-call with the ServiceNav mobile app

More and more information systems are operating 24 hours a day, and the production windows for applications are constantly increasing. The reason? businesses with international… Read more

13/5/19

Monitoring and changes: where destinies meet

The basics Change management can be very complex, with potentially very significant impacts in terms of availability, costs and loss of data . Monitoring can… Read more