![]() ![]() They ask, "Can I submit expenses or not?" just as you would if the water or electricity supply that you subscribe to for your home were to have an issue. They are not interested in the details of individual servers, databases, or devices. IT customers use these services and are only interested in being able to use them. “Hey, but what’s a service, El Fuego?” First and foremost, Splunk ITSI borrows the concept of a service from the ITIL Framework: "A service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks"Īn example of an IT service could be expense submissions in SAP. Splunk ITSI goes for the high-quality, low-noise blend via its two main cases: Services Insights and Event analytics. What I'm saying is that traditional IT monitoring is high on quantity but low on quality. If you miss it, you run the very probable risk of using Splunk ITSI like a traditional monitoring tool and falling prey to the two demons of IT monitoring: Alert fatigue and Non-contextual alerts. But for Splunk ITSI to deliver us out of the sea of alerts that traditional IT monitoring put us in, we’ll need to understand how that paradigm works in your favor. While monitoring tools have been going low for decades, Splunk ITSI shoots high. Splunk ITSI is a paradigm shift in the boring world of IT monitoring. Splunk ITSI: It is Quality Alerts not Quantity of Alerts ![]() Why is this a huge issue, El Fuego? Let me bring it back to the basics and start at what Splunk ITSI is and then what it is not before I explain why this is a huge issue. How? By stooping down to infrastructure and calling it a day. ![]() As a senior Splunk ITSI veteran I can tell you that I’ve seen my share of implementations that miss the mark altogether. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |