No. I don’t think customer will be okay, not to have all incidents in ITSM for auditability purpose. ignio App supports both Android and iOS. I meant, in demo, Android devices are not allowing to present/share screen if you are giving demo
No. I don’t think customer will be okay, not to have all incidents in ITSM for auditability purpose. ignio App supports both Android and iOS. I meant, in demo, Android devices are not allowing to present/share screen if you are giving demo
This is assisted triage scenario. i.e. ignio could not self heal/recover issues..in this case, incident will appear on Queue Manager Dashboard. By default it will go to Expert Resolver. If Expert Resolver does not work then Queue Manger/Service Delivery Manager can assign incident to resolver in the team..
Not yet. We have plan for this in future release.
Yes – exception can be added on specific server
Yes – in selected area, remediation is available. We continue to improve the coverage of technologies for fixes.
Nope. It is configurable and any jar name can be used.
Current offering is specific to log4j vulnerability detected. Plan is to allow users provide/configure pattern/versions
Yeah.. provided coverage of Blueprint and accuracy are 100% or may be > 95%!
Normally these paths are based on the OS versions/patch versions. Its not part of server node attribute. Hence we have to bring them as an attribute as part of OS. This need to be updated on regular basis based on OS versions/patches released if we bring them into BP.
Imagine scenario of ready for the business checks majority of monitoring tools captures incidents once incident occurs while ignio HC will proactive notify issue in advance, both at Application and Infra levels. Second, in Dragon release, Technology specific dashboards are provided along with Ops Console/Control to execute recovery steps from the same UI.