AIOps 2.3-Test Summary Report

Module

Limitations (Deferred Defects)

AIOps PWF

• Correlation has issues when custom field added as a 'Group By' attribute.

• In progress indicator is not shown to user when Auto Resolution triggered, moves to HITL and details for same not captured in BE

• Active alerts remain in open state with the next action empty.

• Impact and Urgency in ITSM cannot be changed and tested in AIOPs for high and medium combinations.

• 'Remove hold' is captured wrongly in the activity session in ITSM tickets.

• Dashboard Alert Pattern – Range indicator of alert Pattern is not positioned centrally to widget or vertically to the right of widget

• Sync with ITSM for ticket updates will be affected when there are multiple projects’ API channels in use simultaneously.

• Alert Processing report from Alert console will show error message to choose shorter time range when API scanner channel polls empty results continuously for long time.

• Email Channels should be created and authenticated from a service account in the incognito window to have it working.

• Multi realm projects’ dashboard should be accessed from different browsers if accessed simultaneously

• Email Template - fields been missed in incoming alert template, data in other fields gets added with wrong data.

• Email Verba Template - Alert id, more information URL is not captured in Elastic search. Alert Attribute if not hostname OID, is not captured.

• Email Template - Additional details if added to SolarWinds mail format, gets added to previous field data in ES

• Alert listing - Auto Refresh - No maximum limit validation available. Entering a larger value does not work as expected.

• AIOps currently support iHub channel’s – Queue, API Scanner and Email only. Queue channel - Add/Edit is possible only via API.

• Same email id cannot be configured in multiple source emails of Extract email workflow.

Rollback

• Full rollback option is not available. Rollback will take care of only items upgraded using upgrade container. Any upgrade done outside of upgrade container will not be rollbacked using the shipped rollback feature