...
Policies can have a COMMENT field which the new EAE uses specifically for the "Name" of the policy. If not present the visually displayed name will be the full IF conditional, which can be harder to read than a short descriptive name.
...
Condition syntax, suggestions, and
...
autocomplete
The condition editor is not a normal input field and contains some code-editor-like functionality. Certain operators and names ("node", "event") are syntax highlighted for clarity. This can be expanded upon in the future.
The EAE also presents auto-completeable suggestions for common attribute of node. and event. These can be expanded upon easily, and can be dynamic (such as any tags defined in other actions).
To assist the user, when the expression =~ is typed, this will autocomplete to =~ qr{} to encourage the user to use this style of regex.
When the Condition field is empty and gains focus, the dropdown of top level suggestions (event, node) will be presented.
...
Policy nesting / converting to nested
...
More commonly there can be typos in action names. In this case the configuration will load, but will show invalid actions which can be cleared up:
...
Contextual help
The “Help” sidebar has been incorporated into the new editor in order to show help based on context and user action. This help is also “sticky” positioned so as to be always in the viewport if the user has to scroll many policies.
Each section of the editor (Policy, Escalation etc.) will show help specific to that section at the top:
...
Each action type can also be selected, which will show help content contextual to the action type:
...
Help is also shown based on the context of the condition editor, for event. and node. attribute information and regular expressions:
...
Note that upon release of this feature, the help content should be fleshed out.