skip to main content
Reporting
   
Reporting
Reports
It shows you the status on your hosts and services right now. The Reporting headline is about letting the user create historical reports from the information that op5 Monitor has collected.
A monitoring system receives a huge amount of data from your IT environment. op5 Monitor has a powerful, yet easy-to-use, built-in report generator.
The reports are generated from the history-logs from all the elements included in the report.
SLA
The reports in op5 Monitor can be mapped against unique Service Level Agreements. This means that you can directly see and follow-up on both your internal and external SLAs.
Creating an SLA report
The fast and easy way to create an SLA report is to only follow steps 1-3 and then skip to the end of the guide, which will cause default values to be used for almost all settings.
The complete instruction describes all settings.
To create a SLA report
1 In the reporting menu click on SLA Reporting
The report setup page is displayed
2 Choose Report type (what type of objects to base your reports on).
We use hostgroups in this guide.
3 Select the objects you like to base the report on and move them from Available hostgroups to Selected hostgroups.
4 Select Reporting period and Report timeperiod.

Reporting period controls the length of the report.

Report time period can be used to include or exclude times and dates from the report. This is based on the time periods set in the configuration.
5 Choose which SLA calculation method to use.
You may choose between 1
Group availability (worst state)
Average
Cluster mode (best state)
6 Set the desired values in the following options or go directly to step 7 and leave the settings with their default value.
a Choose if you like to count scheduled downtime as uptime, actual state or uptime with difference.
“Uptime, with difference" will count downtime as uptime, but will also print the difference from counting downtime as the actual state.
b Choose whether you would like to see the alias instead of the host name in the generated report.
c Choose whether to assume the previous state still applies when op5 Monitor isn't running.
d Choose whether you would like to hide specific states for the hosts or services in the report.
e If this report is based on a Business Service whose top level element has been published as a serviced, it is possible to include the events from the BSM. It will show the underlying checks that triggered alerts in the BSM. If the selected BSM service is not a top level element, no BSM events will be displayed.
f Enter a description for the report. This will be included in the header of the report.
g Choose whether to include soft states or only use hard states in the report.
h It is possible to include a Summary Report with the SLA report. For more information about summare reports, see Alert summary - Top alert producers on page 128
i Include performance graphs if you would like to include all the graphs for the hosts and services included in the SLA report.
j Select skin. Skins modify the visual appearance of the report.
This skin will be used in both HTML and PDF reports.
7 Enter SLA values as percentages between 0 and 100.
Click on the icon in front of the name of the months to copy the value to the other months that are available 2.
8 Click Show report.
The SLA report
When you have created your report you will get a result page looking like this.
The table below describes the parts of the result page
Nr
Description
1
The action icons allow you to
save the report
direct link to report
edit settings
save the report as a pdf or csv
print the report.
2
The report graphs.
Click on the graph to get an availability report for the duration of the SLA report.
3
The result, same result as above, shown in a table.
4
A list of every object included in the report. Click on the object name to get an SLA report for each and every object.
Editing the SLA report settings
ou do not have to create a completely new report if you only want to change a minor setting in the one you just created.
To edit the settings
1 Click edit settings.
2 Edit the settings you would like to change in the dialog shown below. All options are described in Creating an SLA report on page 112.
Click Show report to save the new values.
Availability
An availability report shows availability for host groups, service groups, hosts or services, during a specified period of time.
Creating an availability report
The fast and easy way to create an availability report is to only follow steps 1-3 and then skip to the end of the following guide, which will use default values for almost all settings.
The complete instruction describes all settings.
To create an availability report
1 In the main menu to the left click Availability
The report setup page is displayed
2 Choose Report type (what type of objects to base your reports on).
We use hostgroups in this guide.
3 Select the objects you would like to base the report on and move them from Available hostgroups to Selected hostgroups.
4 Select Reporting period and Report timeperiod. If you leave Report timeperiod empty it will be the same as 24/7.

Reporting period controls the length of the report.

Report time period can be used to include or exclude times and dates from the report. This is based on the time periods set in the configuration.
5 Choose which SLA calculation method to use.
You may choose between 3
Group availability (worst state)
Average
Cluster mode (best state)
6 Set the desired values in the following options or go directly to step 7 and leave the settings with their default value.
a Choose if you like to count scheduled downtime as uptime.
b Choose whether you would like to include a complete log for the included objects in the report
c Choose whether you would like to to include trend graphs. It is also possible to rescale the part of the graphs where there are state changes to make them more visible.
d Choose whether you would like to see the alias instead of the host name in the generated report.
e Choose whether to assume the previous state still applies when op5 Monitor isn't running.
f Choose whether you would like to hide specific states for the hosts or services in the report.
g Enter a description for the report. This will be included in the header of the report.
h Choose whether to include soft states or only use hard states in the report.
i It is possible to include a Summary Report with the SLA report. For more information about summare reports, see Alert summary - Top alert producers on page 128
j Include a summary pie chart to the report.
k Include performace graphs if you would like to include all the graphs for the hosts and services included in the SLA report.
l Select skin.
This skin will be used in both HTML and PDF reports.
m If this report is based on a Business Service whose top level element has been published as a serviced, it is possible to include the events from the BSM. It will show the underlying checks that triggered alerts in the BSM. If the selected BSM service is not a top level element, no BSM events will be displayed.
7 Click Show report.
The Availability report
When you have created your report you will get a result page looking like this.
The table below describes the different parts of the result page.
 
Nr
Description
1
The action icons allow you to change and save the report:
Save it to be able to create a scheduled report
Edit some report settings in a popup frame
Direct link to report
Download the report as a CSV file.
Show the report as an PDF.
Print the report.
 
2
This is the actual result. You can here see how much time each object has been in the different states.
Click on the object names in the list to get a more detailed report for them.
There are two summary rows in the bottom of the table:
Average
This is the average value for a group of hosts/services. It is calculated by adding the % Time for each host/service and then divide the total value with the amount of hosts/services in the group.
Group Availability (SLA)
The SLA value for a given time is the worst, "most broken" state of any of the objects in the report. It displays the amount of time where all hosts/services in the group has been UP/OK or in a PROBLEM state at the same time.
3
A pie chart displaying the result in a graphical way.
Editing the availability report settings
You do not have to create a totally new report if you only like to change a minor settings of the one you just created.
To edit the settings
1 Click edit settings.
2 Edit the settings you like to change in the dialog shown below. All options are described in Creating an availability report on page 117.
3 Click Show report to save the new values.
 
Save reports
There are two reasons for saving a report:
It is easy to reach the same report the next time you would like to see it.
You can set up a schedule for it to be regularly regenerated with current data and sent to you or anybody else in an email, or saved as file.
To save a report you need first to create the report. When viewing the report the save option will be available.
The procedure is the same for both SLA reports and Availability reports. In the guide below we will use a SLA report.
Saving a report
To save a report
1 Create a new report.
2 In the result page click Save report.
3 Give the report a name.
4 Click Save report.
Schedule reports
If you want a report to be regularly regenerated, you should schedule the report to do this automatically.
Before you schedule a report you need to create it ( Creating an SLA report on page 112 or The Availability report on page 121) and then save it (Save reports on page 123 ).
Scheduling reports can be done by clicking Schedule in the reporting menu.
 
Note that the report first must be saved before a scheduled report can be created.
In the guides below we will schedule a SLA report but it is done exactly the same way for the availability reports.
Schedule a report from the result page
1 Create the report as shown in Creating an SLA report on page 112.
2 Save the report as shown in Saving a report on page 124.
3 Click create schedule icon.
4 Fill in the options in the new window.
a Select report type, choose the same type of report that you saved before.
b Choose Report Interval. This will be how often the report is supposed to be sent.
c Select the saved report.
d Add Recipients email addresses, separated by a comma.
e Give the report a file name. This is the name that the pdf file will have when it arrives in your mailbox.
f Add a description for the scheduled report.
g Add a path where to save the report. The path must be absolute and include the filename, with either .pdf or .csv prefix depending in what format you want the file. This is optional.
5 Click Save.
Schedule a report from the report menu
Before a report can be scheduled through the menu a report must first be saved.
1 Create the report as shown in Creating an SLA report on page 112.
2 Save the report as shown in Saving a report on page 124.
3 Go to the report menu and select Schedule Reports.
4 Select the report typ, the saved report and report interval.
5 Enter the email addresses of the recipients of the report. To enter multiple addresses, separate them by commas.
6 If you would like to save the report as a file, enter a local path of the op5 server. This could be saved to a mounted share on the op5 server.
7 Click on Save.
 
Weekly reports are sent out on Mondays and monthly reports are sent out on the 1:st every month.
Modifying scheduled reports
To modify a scheduled report
1 Click Schedule reports in the main menu.
2 Double click on any field you like to modify.
3 Click OK to save.
4 If you want to save the report as file, enter a absolute path including the filename and prefix (.pdf or .csv) in local persistent filepath.
Deleting scheduled reports
To delete a scheduled report
1 Click Schedule reports in the main menu.
2 Click delete icon on the schedule you like to delete.
3 Click OK.
 
Events and logs
Alert summary - Top alert producers
One useful report in op5 Monitor is the Top alert producers report. This report is created from the Alert summary.
The Top alert producers report makes it easy to identify the biggest problem producers in your environment monitored by op5 Monitor.
Creating a Top alert producers report
To create a Top alert producers report
1 Click Alert summary in the main menu.
2 Select custom report mode.
3 Select all hostgroups.
4 Select Report period 4.
5 Select Summary type and set it to Top alert producers.
6 Leave the Alert Types with the default value.
7 Choose Hard states for State Types, we are only interested in the real problems.
8 Choose only problems sate for both hosts and services.
9 Set the number of items to show in the resulting report. 5
10 Click on Show Report.
Top alert producers result
Now we have a report ready to be examined.
This report can be used as a guide to help you to minimize the number of false alerts and notifications. Significant amounts of false alerts can lead to the users loosing faith in the monitoring system.
Saving an Alert summary report
Alert summary reports are useful from time to time. So when you have created a new one you will probably like to use that one an other time. Then it is a good idea to save it.
To save an Alert summary report.
1 Create an Alert summary report like you did in Creating a Top alert producers report on page 128, show the report then:
2 Click Save report.
3 Enter a name for the report and click Create Summary Report.
Scheduling an Alert summary report
For the exact same reason as it is to schedule an availability report or a SLA report you might want to schedule an alert summary report.
To schedule an alert summary report
1 Create an Alert summary report like you did in Creating a Top alert producers report on page 128 and save the report.
2 Click the plus icon at the right top of the page
3 Follow the instructions in Schedule reports on page 124, just select “Alert summary report” as report type.
4 Click Save.
Trends
Trends display a graphic view of status on a host or a service during a selected time period. This graphical view is reached from Availability reports.
Creating a trend report
To create a trend report
1 Click Include trends graph.
2 The trends will be shown in the report.
Event log
An event log displays a list of all events that has occured in op5 Monitor. It shows you everything from alerts and notifications to op5 Monitor service restarting. In other words this is a log viewer for the main op5 Monitor log.
Viewing and filtering logs
In the op5 Monitor event log you can
view every event that took place in op5 Monitor
filter out any kind of events you do not want to see
set the start and end time of the logs you like to view.
To view the event log
Click the Event log icon in the main menu and there you go.
As you can see in the picture below everything except for Initial and logrotation states are shown by default.
The event log view is divided into two parts
filtering
logs
In the filtering you can change what type of events you like to show and also between what dates you would like to view logs for.
The logs are grouped by hours to make it a bit easier to find what you are looking for.
Alert History
The alert history view is a view for all alerts that has been detected by the system.
Viewing and filtering logs
In the op5 Monitor alert history you can
view every alert that took place in op5 Monitor
filter out any kind of alerts you do not want to see
set the start and end time of the alerts you like to view.
To view the alert history
Click Alert history icon in the main menu, and you see an unfiltered list of alerts.
Filter alert history
The list can be long. Try applying a filter to it by using the filter options. You can access them through the Edit settings icon.
 

1 Traditional Availability reports are based on group availability (worst case). An alternative way is to use average values for the group or object in question. Note that using average values is sometimes considered not to be an proper form of SLA.

2 Only the months that are included in the report will be available.

3 Traditional Availability reports are based on group availability (worst case). An alternative way is to use average values for the group or object in question. Note that using average values is sometimes considered not to be a proper form of SLA.

4 Since this is the first time we generate this report we use the last 31 days. When you use this on, for example, weekly basis you could use the last 7 days.

5 If you have a large environment with a lots of host you might want to increase the number of shown items.