AIOps Release 3.0.0

Overview

AIOps 3.0 release introduces a new AIOps UI, focused on improving the user experience while working with correlated alerts. This release also introduces a new AI capability – pattern mining in alert history and using those patterns in alert correlation.

AIOps 3.0 introduces a redesigned UX focused on the user experience of an ITOps engineer. The changes are primarily focused on the screens where ITOps engineers spend the most time - alert listing screen in AIOps View. All other parts of the application have been updated to look consistent with the new design. Some of the key changes to highlight are,

• Menu items - Alerts, Tickets, Infrastructure, Configuration etc. which are currently arranged at the top has been moved to a vertical menu on the left.
• Global Search – The new global search allows users to search across alerts/tickets/devices in a single search.
• Switch Projects – It is now easier to switch to a different project from within the current project itself.
• Alert Cluster Severity – Severity is now more visible and available as a column.
• Quickly identify by alert status – Visual differentiation of open/active/resolved alert clusters
• Correlation – Clicking on the correlation bubble will open a window showing all alerts in the cluster and details.

You can access the new AIOps UI using the new URL. The old URL will be decommissioned in the next release.

New URL: <<domain>>/paas/itops/aiopsui/smartops/<<org>>
Old URL: <<domain>>/paas/itops/itopsui/smartops/<<org>>

For e.g., the new URL in Stage is https://stage.ustsmartops.ai/paas/itops/aiopsui/smartops/ustglobal

AIOps 3.0 introduces an AI capability which mines through alert history to identify alert patterns. These patterns will reflect derived associations such as topology, from the historic patterns of alerts. These patterns can then be used to augment alert correlation.

In addition to the chosen correlation method (hybrid/similarity), admins can also enable pattern-based correlation. The pattern-based correlation will be used only when there is ambiguity in the correlation of an alert by the base method or if no correlation is suggested by it.

Preview and Apply Settings
An admin can preview the patterns and resulting correlation, before enabling pattern-based correlation.

The preview is a two-step process which uses historical data within AIOps to illustrate how this feature will impact alert correlation.

• Step 1 - Preview patterns generated based on current settings
• Step 2 - Preview alert correlation based on patterns generated

If the preview looks good, the admin can review the preview alerts which are correlated using patterns and provide feedback. With this, the settings will be completed, and pattern-based correlation can be enabled.

Pattern based correlation in alert clusters
If alerts are correlated using patterns into an alert cluster, users can preview the pattern used for the correlation and provide feedback.

When a recovery alert is received out of order, it will create a new cluster. Such orphan recovery alert clusters will remain open until an operator resolves it. To reduce redundant user action, such clusters will now be auto closed.

Device Maintenance window can now be defined in bulk for multiple devices using this API - /api/updateDeviceMaintenanceStatus.

To optimize the comments updated on a ticket, this release introduces an enhancement in how ticket comments are updated. AIOps updates default comments in specific scenarios. However, if a ticket template has been set up for any scenario, the default comment updates will be turned off and only the comment specified in the ticket template will be updated.

Today ticket templates can be defined for following scenarios

• Ticket is created
• New alert added to ticket
• Reassignment from VE

Admins can control the ticket comment updates in these scenarios, using this enhancement.

Release Artifacts

Deployment Artifacts

For support and more enquiries, you can write a mail to us on feedback.smartops@ust-global.com