Creating Snapshot Reports

Reports created in the Windows Client can be published to the Web Application as 'dashboards'. Once published, these 'dashboards' can then be configured through the Web Application - Administration tool as snapshot reports, which are then included in the Reporting Essentials for Web Application page of the View Systems tool. This is done by using the following procedure.

After a restart of the machine on which the Web Application is running, snapshots will not be generated until the web interface is accessed for the first time. To avoid this and ensure that snapshots are generated before the Web Application is accessed, the Microsoft's 'IIS Application Initialization' feature can be used. This is included in IIS 8.0, and is available as a module for use in IIS 7.5. This can be configured on a global or ‘per application’ basis. See Microsoft documentation for further information.

A Snapshot Report will not be created for the Web Application until the first interval of data has been received as configured in the Display/Dashboard. ie. If the Display is configured using a 5-minute collection Interval, then it will take 5 minutes until the Snapshot Report will be available for viewing.

Create the required report in the Windows Client and then publish it to the Web Application using the ' Sending Documents to the Web Server.

The report needs to be constructed as a standalone document so it can be opened by directly double-clicking on it. If it cannot be opened by double-clicking, then it will not work correctly as a published snapshot.

A snapshot report cannot be created from a dashboard that is already used in an 'on-demand' report. If this is required, it will be necessary to first rename the source Report document in the Windows Client and then publish that to the Web Application.

Open the Web Reports page in the Web Application - Administration tool and then click the Add New Report button.

This will open the following page.

Report Dashboard to Publish

In the 'Report Dashboard to Publish' field, enter the name of the published dashboard that is to be generated as a report.

For example, if the source Display document in the Windows Client is named 'Busy Hour Report.dpy' then the 'Report Dashboard to Publish' field should be completed with 'Busy Hour Report'.

The available published documents will be located in the Prognosis\WebUI\IIS\Dashboards\User folder.

Generation Schedule (Publishing profiles)

Each Snapshot report is associated with one or more reusable Publishing Profiles. A Publishing Profile defines the schedule for generating snapshots and also defines how long the reports should be retained on disk and made available for viewing before they are deleted.

In the 'Generation Schedule' field select one or more profiles for the reporting period required.

Reports that collect data from multiple servers can operate in one of two ways:

●   Combined snapshot: A single snapshot will be generated containing information from all servers defined in the source report.

●   Snapshot per Node: A separate snapshot is generated for each server defined in any window within the report.

If a separate report for each server is required, check the 'Snapshot per Node' option.

If a new profile is required click the Manage Publishing Profiles button. This will open a page where a new profile can be created, see the Configure Publishing Profiles for details.

Timezones

Normally the Web Application will show times in charts in the time zone of the Prognosis Server that the Web Application connects to.

This setting is relevant for situations where the servers being monitored are in different time zones. This setting can be used to ensure that:

●   The snapshots are generated at the appropriate time

●   Any times shown in the report snapshots accurately reflect the timezone

●   The data and time selectors reflect the correct time for the selected report and server

If monitored servers are located in different time zones then it may be advisable to group them by timezone and make copies of the source report document and publish them separately with the appropriate timezone set.

Group Name in Reports Central

In the Web Application - View Systems tool, the Report Central navigation is organized by 'Report Groups'. This field defines which report group the new snapshot report entry will be displayed in. From the drop-down list, select which group on the Reports page this new report will be placed into.

Name seen in Reports Central

Enter a name for this report that will be shown in the selection box on the  Reports page of the View Systems tool.

Description of report to users

Enter a description for this report that will be shown on the Reports page of the View Systems tool.

Define Roles able to see this report

It may be useful to restrict reports to particular sets of users. For example, certain reports may contain information relevant to a particular managed service customer or to a particular internal line of business or to a set of stakeholders interested in a specific application or geographical site.

If the new report should only be available to users that are assigned to a defined Security role, check the box against the required Roles names. See the Security Page for details about Security Roles.

When finished click the Save button.

The Web Reports page will re-open showing the new report added to the drop-down list and reports will start to be generated according to the selected profiles.

The new report entry will now be listed in the Reports Central page of the View systems tool with the  icon. However, the Snapshot report itself will not be available until the scheduled generation time.

Considerations for creating Snapshot Reports

In most cases, Snapshot reports are based on Display documents that have been created in the Windows Client that pull data from a Database Collection. When the 'Snapshot Per Node' option is used, the generator will make a complete list of all servers that appear in any window within the report document. Separate snapshots are then generated for each server and data from any other server will not be included in the snapshot. As a result, it generally makes sense to use the same server group in all windows.

Provide feedback on this article