ignio AIOps, from Digitate in Santa Clara, is a solution designed to improve business agility by creating a unified view of the IT estate, connecting business functions to applications and infrastructure. This is combined with behavior profile of systems and applications that is continuously learnt using this blueprint. ignio aims to improve the transparency of complex Enterprise IT landscapes.
N/A
Splunk IT Service Intelligence (ITSI)
Score 10.0 out of 10
N/A
Splunk supports IT operations analytics with the Splunk IT Service Intelligence premium offering, a software application available to subscribers to Splunk Cloud or Splunk Enterprise log analytics and SIEM platforms.
-Autonomous alert and incident management related to infrastructure, NW, and applications. -Excellent fit to handle CPU, memory, and disk space alert management - proactive and predictive. -Several automation features (self-healing) - CPU/Memory modifications; disk extensions; patch management -Provisioning of user access and infrastructure servers, etc.
[Splunk IT Service Intelligence (ITSI)] is well suited when you have a system that you want to visualize, and then layer in information from many different sources. This will allows ITSI to intelligently create alerts based on the system as a whole vs the individual components. In some cases, a simple splunk dashboard would really suffice over using ITSI. Teams deploying ITSI should really understand the use cases and consider using simple dashboards where they make sense, and use ITSI for topological views.
There is a lot more the desktop tool can do. For example, we need to apply an upgrade to get the tool to talk to our infrastructure while employees are working from home. The tool was initially installed with the assumption that the desktops would be in UserLand. Instead after COVID-19 the desktop/laptops have been used for over a year on people's home networks. As of right now, we have to sync when the devices are connected to VPN. Moving forward with the upgrade, we will be getting this data over TLS when they are connected to the untrusted networks.
The concept of ignio AlOps requires OCM efforts within most operational teams. This isn't necessarily the fault of the tool itself, but when implementing ignio, or any AIOps tool, the team will get a lot of pushback as an outside team is centralizing the operational improvements. The tool should have a centralized intake process that will allow the collection, ranking, and management of automation opportunities. ignio AlOps should then simulate the proposed efficiencies from implementing something within the backlog. Right now a lot of local teams are having a hard time getting on the same page as the enterprise teams, and a common methodology for prioritizing (even if overly simplistic) would go a long way to enterprise planning.
These tools are very new and things get added to them all the time. There should be a way for the product's stakeholders and process owners to understand the additional value ignio AlOps is gaining over time.
The terminology takes some getting used to: Aggregation policies, notable events, correlation searches, glass tables. If you're not familiar with ITSI, these terms can be a bit overwhelming and steepens the learning curve.
We have had some technical issues with the underlying support when used in a multisite cluster. We've had to build in several points of redundancy to make sure it works as expected.
I'd like to see additional types of notable events, like informational events that come in for when an incident is created or when an alert is acknowledged so all of those action steps can be viewed on the episode timeline without affecting the count of events.
We have replaced our monitoring platform with Splunk & ITSI, and with the success, it's seen at our organization thus far we would be hard-pressed to pivot to another tool. Frankly, our business partners and application teams love Splunk & ITSI.
ignio AIOps version upgrades were a heavy lift. Having to learn a new language versus an industry standard language took time. More consideration on overall internal long-term support needs to be determined.
Splunk IT Service Intelligence (ITSI) is a platform with extended functionality and provides various functionalities which can be utilized to improve the efficiency and accuracy in analyzing the data and detecting the attacks.
We have built a healthy relationship with the vendor support team throughout the implementation phase, all incidents raised were resolved within the SLA without a fail
During POC, pre-planning, and implementation, we have had interactions with numerous folks at Splunk. Everyone from sales & engineering to markets analysts to specific IT component SMEs, and a small professional services engagement to get started. They have all been exceptionally helpful and go above and beyond the call of duty. They actively reach out to ensure success is being realized and find ways to help proactively, instead of having to simply open support cases with the vendor.
I am happy with the way team has implemented and shared the product for our organization. However, would like to see it get extended to the other line of business too.
Splunk has raised itself as a platform not just as a tool unlike other products in the market. If I talk about Moogsoft it also has similar capabilities but Splunk ITSI has more visibility and its GUI is making a different impact on the users. ServiceNow and Splunk are equally capable products however Splunk seems to have more tech-savvy people tools than ServiceNow.
