...
| Per-Page Options Property | Description |
|---|---|
title | The title for this report page. Optional; if not present "Page <N>" is used. |
summary_title | The summary title is shown above the utilisation summary table. Optional; if not present "Utilisation Summary" is used. |
column_heading | The value of this property is used as table column heading for the business service column in the summary table. Optional; if not present, "Interfaces" is used. |
graph | The name of the NMIS graph to produce for each selected interface. Required. Note that the "short name" of the graph is to be used, e.g. "autil", not "Interface Utilisation including Availability". |
graph_order | The graphs for all members of one business service group will be arranged in the selected order. |
levels | A hash sub-structure that describes the desired coloring rules scheme for this page, based on utilisation ratiolevel. Optional; if not present, then the levels from the global configuration option report_summary_levels are used. |
Level Color Schemes
The coloring rules must be set separately for each page.
To simplify reuse the schedule editing GUI will let you pick only from existing schemes that are defined in opCommon.nmis: the color level schemes must be attached to the configuration item report_snapshot_levels, and each scheme must have its own key. opReports ships with two example schemes to illustrate this setup.
In both cases (for editing a schedule by hand, or for preparing reusable color schemes in the config), the levels structure levels option must be a deep hash structure, key being the level 'name', each value being a structure with the following properties:
...