Splunk ITSI streamlined our incident management by allowing Splunk administrators to easily see all incident details and cascade them down to relevant stakeholders and customers. ![]() Splunk ITSI is reliable, and its AI-driven predictive analytics help identify potential component or device failures. The CAB team can provide approvals quickly because the information is easily accessible. Architects can plan better using the environmental details provided by ITSI. It has centralized all resources for administrators and service personnel. Splunk ITSI has helped our organization in many ways. This will allow us to prioritize incidents based on their criticality and notify stakeholders accordingly. ![]() Once we have implemented the CMDB to meet our requirements, Splunk ITSI's predictive analytics can identify any devices that will be affected by planned changes and provide us with that information. Splunk ITSI provides end-to-end visibility into our network environment, which reduces the manual effort required to capture configuration data and helps us identify weaknesses in our network. Splunk ITSI also provides a central source for the documentation of our application dependencies. Splunk ITSI helps the advisory board's cab team increase efficiency by instilling trust in systems over manual administrators. The mean time to resolve has been reduced thanks to Splunk. Once we implemented it, the alert notification was automatically sent to people, so it automatically reduced the time to two to five minutes. Previous to implementing Splunk, the mean time was one hour or so. We've used it when there wasn't an existing system, and we would have had similar results with other tools in the market. It has a similar meantime to detect as Dynatrace. We've been able to reduce the mean time to detect. From the UI, you can correlate the alerts using dynamic conditions (not just static ones). It can aggregate the alerts and just create an alert only when needed. Teams were able to map the availability of the system more accurately - up by 28%. It's good for the customer on the technical side. At a single glance, there is a complete view of infrastructure. Customers have noted the solution helps streamline incident management. If you have a noisy system, when there's an alert, people tend to miss issues. That said, I'd say the admin needs a deep understanding of the infrastructure. The predictive analytics are pretty good. You have to write your own scripts, however, it's not as user-friendly. The capability of recording any transaction is not possible in Splunk. We struggled with one use case where payments were failing and they couldn't understand if it was the infrastructure or bandwidth. The only thing that is lacking is the application monitoring. In addition, we've been able to reduce the time to resolve. We've been able to resolve this quicker, and our main time to detect has been drastically reduced. Previously, we used to take a lot of time getting to the root cause of what happened. Our main time to detect has been reduced as well. Looking at it helps provide a resolution. In that case, I would look at endpoint visibility from the infrastructure to the end of the service call, including all the scans, tracing, and everything. That likely means there's an issue with that region. For example, for the authentication service that we have, users for certain regions are not able to authenticate completely. ![]() It helps in streamlining the incidents that are coming in. The product has helped to streamline our incident management with end-to-end visibility. That said, when it comes to an incident during an outage, end-to-end visibility helps us deep dive or drill down to find out the root cause and how to make the platform better for the future. In the everyday work that we do, we don't really use endpoint visibility since that is not required if we look at normal and general use cases. We can take a deep dive into the incident. The endpoint visibility is definitely helpful, and that is mainly for the application team. The end-to-end visibility of IT assigned to our network environment is great. However, for us, I would say that root cause analysis, problem detection, and anomaly detection are the most helpful features. There's one feature which is a prediction and detection feature that we have gone through. The root cause analysis is very helpful for us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |