...
| 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. |
| WAN | all, interfaces ignored before 3.1.4 | Before As of version 3.01.4 the WAN report ignores ignored interface selections; . 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 As of version 3.01.4 the QoS report ignores 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 QoS 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 | |
| Interface Utilisation | 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
...
In the GUI this choice is called "by Regular Expression", opreports-cli uses the command line argument noderegexnode_regexp=<regular expression>, and for scheduled reports you'd specify this with the property node_regexp.
The node regular expression is evaluated at report creation time.
The regular expression syntax is Perl's standard, described in detail in this Perl Regexp Tutorial.
Nodes and Interfaces whose names/descriptions match regular expressions
This feature was added to opReports in version 3.1.4.
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 reports where interfaces are not relevant this option behaves just like the previous selection type.
In the GUI this option is called "by Regular Expression for Nodes and Interfaces". opreports-cli requires that you supply both node_regexp=<regular expression> and node_intf_regexp=<regular expression> arguments. The report schedules use the same property names as the opreports-cli parameters.
Both regular expressions are evaluated at report creation time.
Explicitly listed Nodes
In the GUI this choice is called "Pick from Node List".
...