Release date: 18 July 2017
Version 7.9 is a feature and enhancement release.
- The Infrastructure Summary wizard now supports generating a
complete reporting suite.
The reporting suite reports are made available via the publisher, with the
option to send the daily and weekly reports by e-mail as well, and include:
- several overviews of the current
situation, updated every 10 minutes throughout the day.
- a daily summary of the whole network infrastructure.
alerts generated during the previous day, with one report
for each type of alert.
- important events logged during the previous day, split
issues and system problems.
- a weekly analysis of the monitoring structure,
highlighting any issues with the configuration.
- The publisher now allows reports to be arranged into
groups, rather than all at one level. A group can contain both
reports and sub-groups.
- The New Scheduled Report wizard has improved support for
creating composite reports.
- Scheduled reports now allow different output descriptions to
be used for each output type.
- The dual configuration of availability monitoring for agentless
systems and of restart monitoring for all systems has been removed. All
availability and restart monitoring is now configured only at
the individual system level.
The responses that were previously configured centrally from
within the console at Administration -> Discovered Systems ->
System Monitoring are no longer used. Note that centralised
management of responses for availability and restart monitoring
is still available, and is now handled via the overall
infrastructure definition or via one or more custom policies.
For a typical configuration, where responses are managed via the
infrastructure definition, no configuration changes will be
required. If your configuration currently uses different
response actions for central and system-level availability or
restart monitoring, please contact technical support before
carrying out the upgrade.
- Resolved a potential security vulnerability in the
- Resolved an issue whereby if an external database was
configured but not available, data collected up to the point
that the external database subsequently became available again could potentially be