The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Access: WAE Live > Settings > Explore and Analytics tab
WAE Live supports multiple interface types that you can view on the Explore page and are used when creating reports from the Analytics pages. The Settings > Explore and Analytics tab lets you specify the default interface type used. You can override the default for the Explore pages, but not for the Analytics pages.
WAE Live acts on objects (network elements) that are discovered or created prior to WAE Live accessing the plan file. For example, interfaces might be discovered by WAE Collector while demands thereafter can be added to the plan file. Each object has a set of default properties (attributes) that are tracked in and retrieved from the data store. For example, an LSP’s Shortest TE Path, a node’s CPU, or an interface’s Traffic In are all properties that are collected and stored by default. In addition to these default objects, from the Settings > Explore and Analytics tab you can create user-defined properties to fit your specific needs.
Note These settings are configured for all networks; that is, they are not configurable on a per-network basis.
You can specify the default interface types to show in Explore and use in Analytics (reporting):
Examples: ae0.0, Bundle-Ether1, Port-Channel7
You can define your own properties to use when creating reports. User-defined properties derive their values from other properties. For example, rather than tracking incoming traffic (Traffic In) and outgoing traffic (Traffic Out), you might need to track the ratio of incoming to outgoing traffic (Figure 4-1).
Note For two-word properties, use one word in the definition. For example, for the Remote Node property, use “remotenode.” For Traffic In and Traffic Out properties, use “traffin” and “traffout” in the definition.
Figure 4-1 Example of a User-Defined Property Definition Using Simple Arithmetic Expression
As with default properties, these user-defined properties are available in the Explore and Analytics pages.
Each user-defined property consists of an object, a user-specified name, and a user-created definition.
Step 1 Navigate to WAE Live > Settings > Explore and Analytics.
Step 3 From the Add New Property dialog box, choose the object type to which the newly created property applies (interfaces, interface queues, nodes, and so on).
Step 4 Enter a property name. Once the property is saved, this name appears as a selectable property for the given object in Explore and Analytics pages.
Step 5 Enter a definition value.
Step 6 Click Preview to view the results that the object and definition return.
The definition field accepts alphanumeric characters and regular expressions. Each definition is an expression using one or more default properties. The following rules apply:
– Arithmetic expressions: +, -, *, /, and % (Figure 4-1)
– Relational operators: >, <, =, <=, and >=
– Logical operators: AND, OR, and NOT
– Regular Expression Functions
– Edit (pencil icon)—Edit the user-defined property.
– Delete (trash can icon)—Delete a user-defined property. There is no undo.
In the Definition field for your user-defined property, you can use regular expressions to filter results using regexp_extract and regexp functions.
|
---|
regexp_extract(formatted_result, identifier1, pattern1, identifier2, pattern2,...) |
This searches a string with a list of regular expressions to produce a formatted string result compiled from back references. Back references are the results of capturing groups from the regular expressions and referencing them in order by $N, where N is a number that is greater than or equal to 1. This N identifies the captured string returned by a back reference in the order it appears in the matching pattern. At a minimum, only three arguments are needed for regexp_extract. You can use any number of pairs of attributes and expressions.
Example: In this example, both captured groups ($1 and $2) come from the regular expression for Description. The expression for Node does not have any capturing groups. It is used only as an additional filter. If any of the regular expressions fail to match, the overall regexp_extract fails to match.
"regexp_extract("$1 ($2)", Description, ";interconnect to ([^\(]*) \(([^\)]*)\)", Name, "^(?!.*lo)")
|
---|
This regexp syntax returns true, false, or null.
Example: If Node starts with 'palt', then sum the Traffic In and Traffic Out values. If the Node starts with something else, or is null, no value is displayed.
case when regexp(node, '.*PALT.*') then traffin + traffout else null end
Example: If your node names include site names, this regexp syntax is useful for creating site properties for interfaces.
The CASE statement allows conditional values based on a set of expressions. All result-expressions must be of the same type. That is, they can all be numeric or all be string, but they cannot be a mixture of both string and numeric.
|
---|
Example: This example creates a user-defined property if a node name matches a remote node and if neither name is null.
when regexp_extract('$1', node, '(....).*\.(..)\..*') isnull then null
when regexp_extract('$1', remotenode, '(....).*\.(..)\..*') isnull then null
when regexp_extract('$1', node, '(....).*\.(..)\..*') = regexp_extract('$1', remotenode, '(....).*\.(..)\..*') then true else false end
Two syntaxes are used for the supported expressions: EBNF (Extended Backus–Naur Form) and a simpler query. You can use one or multiple words for isNull and isNotNull.
A simple query has the following syntax:
Table 4-1 lists the grammar in EBNF format.
|
|
---|---|