AIOps 2.0 - Test Summary Report

Module

Limitations(Deferred Defects)

ITOps PWF

• 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 service account in incognito window to have it working.

• Impact/Urgency cannot be set via ticket templates for the tickets created from ITOps

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

• Dashboard Alert Pattern - With top 5 alerts for each day with different alert names coming in for different days, selecting large duration in date filter - X axis data goes not readable

• 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 larger value does not work as expected.

• ITOps 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.