...
There is a configuration setting 'opreports_ms_availability_strict' in /path/to/omk/conf/opCommon.nmis which controls the behavior used in calculating availability in the report where NMIS does not contain a particular record for a monitored service.
The default setting for the setting is 'opreports_ms_availability_strict' => 'false' which can be interpreted as 'monitored service is not down unless NMIS provides an explicit record indicating service was down'.
The setting 'opreports_ms_availability_strict' => 'true' can be interpreted as 'monitored service is down where NMIS does not provide a record for the monitored service AND OR where NMIS provides an explicit record indicating service was down'.
Strict Availability Mode: 0|1 is written to the headings of the generated report to signify which 'opreports_ms_availability_strict' setting was used to generate the report.
This report offers optional embedded graphs of each monitored services availability and response time by default, and custom graphs as configured in the NMIS model file for the monitored service. The default choice is to include both the default graphs and custom graphs, but you can change that using the report options Include Embedded Graphs and Include Custom Graphs. The contents of the graph are not configurable, but the desired default size can be set using the configuration option opreports_embedded_graph_size_small (default: 300 pixels wide by 75 pixels high). The width of each graph is reduced dynamically starting from the default size when Custom Graphs are included in the report, but is never less than 50% of the default size. This behavior was implemented as reducing the width of the graphs dynamically by up to 50% was found to improve the viewability of all graphs with less chance of horizontal scrolling, and has minimal effect on interpreting the contents of each graph.
...