In progress is a stage which will ideally remain inaction for a smaller duration and a monitoring tool sending a clear event in that duration is rare, due to monitoring frequency. But to answer the query , Inprogress ticket will not be changed to clear status, as the ticket is already being worked by ignio. But for Triaged/Manual status, clear will be done. For more details please check: https://digitate.atlassian.net/wiki/spaces/ID/pages/3262513156/Clear+Events+Handling+SP8
Yes cross tool correlation is possible in ignio, as you can see in the watch we have configured more than one tool, and the are correlated
There is no specific document related to switch/router cases. But based on the policy, or accepted derived signatures, alerts will be processed. For more details please check: https://digitate.atlassian.net/wiki/spaces/ID/pages/2830862650/Alert+Aggregation+SP8
ignio UI should be sufficient for tickets handled by ignio
No other policy configuration required. Self-heal policy configuration is required to get ignioApp Notification and action selection to be configured.
Widgets have improved. Most of the information was already there it is represented differently
This is for the purpose of billing. This is a SaaS solution and Accounts team will need to generate an itemized billing report. Outcome based proposal to customers based on no. of alerts/events managed by EM.
Yes, Action selection are FYA notifications where user can suggest the manual fixes as configured
Monitoring tools generally sends a Clear Event to notify that an earlier reported issue is now resolved. So ignio will now close any open Alert/Incident once a Clear Alert is received.
No, this is just one way in which an alert may get closed
Later in the demo we will showcase reports which will be used for outcome based pricing
Yes, as notes are now externalized as updatable templates, user can enter his language of interest.
Today we don’t have this in single view.
If it is an incident fetched by ignio, the same will be closed as suppressed with relevant details
It gives you a consolidated view (count) of how man alerts came and various actions performed by ignio on those alerts.
This was one of the usecase where in the inital weeks of go live Customer may like to keep “Fix allowed by ignio” as “False”
These are in roadmap
There is a wide variation of the issue descriptions and CI naming methodology in the data which we have observed , hence this may not be feasible. We are however, working on enhancing the current auto-extraction capability – which will be out in next release
We are planning to take it up in watch – tentative ETA : Dragon – SP3
