...
On the other hand, providing insufficiently precise information to reports that require it will result in an error message (e.g. trying to run a summary report with just group=X).
| Report Type | Selection Mechanisms | Notes |
|---|---|---|
| Node | single node only | The node report supports a single node only. If your selection contains more nodes, then the report is created for the first listed node. |
| Node Health | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Node Availability | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Grouped (Node) Availability | all, interfaces irrelevant new in opReports 3.1.4 | Interface selections are not relevant for this report. |
| WAN | all interfaces ignored before 3.1.4 | Before version 3.1.4 the WAN report ignored interface selections. It operates on all active or any selected interfaces of the selected nodes whose net type is "wan". |
| WAN Utilisation Distribution and WAN Utilisation Distribution Summary | all new in opReports 3.1.8 | It operates on all active or any selected interfaces of the selected nodes whose net type is "wan". |
| QoS | all interfaces ignored before 3.1.4 | Before version 3.1.4 the QoS report ignored interface selections. It operates on all active or any selected interfaces of the selected nodes', if QoS is configured for the interface. |
| CoS | all | For each selected node this report covers all active or any selected interfaces that have Class of Service configured. |
| Uptime | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Response Time | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Interface Capacity | all | |
| Grouped Interface Capacity | all | |
| Interface Utilisation | all | Interface selections are honored but the "type" component (in selections by node+interface+type) are ignored as not relevant. |
| Interface Unicast Packets | all | Interface selections are honored but the "type" component (in selections by node+interface+type) are ignored as not relevant. |
| CPU | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Free Memory | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Memory Pool | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Memory Buffer | all, interfaces irrelevant | Interface selections are not relevant for this report. |
| Traffic Usage | all | Interface selections are honored but the "type" component (in selections by node+interface+type) are ignored as not relevant. |
| Traffic Summary | node+interface+type | This report strictly requires this specific selection format. |
| Traffic Snapshot | opCharts Business Services, selected per page | This report type strictly requires lists of Business Services for each of its (multiple) page definitions. |
| Configuration Summary | all, interfaces irrelevant | Interface selections are not relevant for this report |
Choosing the selection mechanism for scheduled reports
...
Nodes must match the regular expression given for the node name, but interface descriptions must also match a separate regular expression.
Only those interfaces are selected where both regular expressions match. For
However, for reports where interfaces are not relevant this option behaves just like the previous selection type, interfaces are disregarded.
The regular expression for interfaces is applied to both the interface's ifDescr and Description properties in parallel, and a match for either or both selects the interface.
(The NMIS GUI presents ifDescr as "Name" or "Name (ifDescr)". Depending on the device and its modelling ifDescr may or may not be adjustable, but Description can be set easily within NMIS.)
...
Groups must match the regular expression given for the group name AND
Nodes must match the regular expression given for the node name AND
Interface descriptions must also match a separate regular expression.
Only those interfaces are selected where all three regular expressions match.
However, for reports where interfaces are not relevant, interfaces are disregarded.
...
Groups must match the regular expression given for the group name AND
Nodes must match the regular expression given for the node name AND
Interface descriptions must also match a separate regular expression.
Only those interfaces are selected where all three regular expressions match.
However, for reports where interfaces are not relevant, interfaces are disregarded.
...