Recently, many of our customers and partners have asked us about Splunk’s IT Service Intelligence and how it compares with Loom's solution, so here we are, highlighting and demonstrating some of the key differences between the two products.

Manual Configurations vs. Non-existent Configuration

Once configured properly, Splunk’s IT Service Intelligence, or ITSI, will provide you with great visibility into your application and infrastructure. It allows you to “zoom out” for a general view of your stack, or “zoom in” for locating specific services or metrics that are of interest. However, this will only be possible after you have configured each and every metric that is of interest. You will need to manually “draw” your system architecture for the software. Loom's solution on the other hand, can automate this entire process for you. Once your data starts flowing, Loom can automatically analyze all logs, auto-identify metrics, and elements that are of interest. Doing almost all of the work for you. Loom's solution will not only define the metrics and thresholds to extract all the value you’re looking for, it will also apply its AI to foresee possible issues, eliminating the need for a human user to determine what to monitor and how to monitor it.

Cover What You Know vs. Discover Unknowns

In addition to the fact that ITSI has a very time-consuming set-up to start with, it also is limited to what you already know. In a sense, think of Splunk’s ITSI as your “defense system”, it will cover soft spots that you have identified and know about ahead of time. While having a defense system in place is obviously important, in order to ‘win’ the game you also need a good “offense”. Here, Loom’s collect-all, analyze-all approach comes into play. Loom's solution applies statistical methods to analyze ALL your data and find meaningful anomalies without any need for the user to tell it what to look for. This means that you are discovering NEW issues that you may not have known about, and taking care of them before they become critical.

Correlations Within a Service vs. Cross-Application Correlations

Both ITSI and Loom's solution will generate an alert for you, and both will draw correlations from different events to try to help you clarify the root cause. ITSI will present you with your pre-defined KPI’s and measure them over time, helping you understand which KPIs behave abnormally and when. That being said, it is important to note that this type of analysis will only be available per service, only on one layer of your stack at a time. Loom's solution takes a different approach, connecting events from different applications and services throughout your stack, allowing you to better differentiate between the symptoms and the root cause. 

Let’s say that your users are having problems logging into a specific application. Receiving an alert about this is well and good, but Loom's solution can give you a deeper understanding. Loom will be able to correlate that the application is not the root cause, but rather the issue with active directory is the source of this problem (for example).

Resolution made easy with Loom's TriKB

Last but not least, here is something unique to Loom's solution: 

Normally you will get an alert, understanding the problem, and then figure out what steps need to be taken to resolve the issue. This can be a process that takes some time, and requires a lot of knowledge gathering. Why not save this information so that it is easily accessible? Here Loom's solution really shines with Tribal Knowledge (or “TriKB”). TriKB will save the work you’ve already done (or the work that others have done before you), and help spread the knowledge throughout your organization. If the same problem comes up again, a clear explanation and steps to take for resolution will be available to anyone who uses Loom's solution. No need to “reinvent the wheel” time and time again.

AIOps For Modern Hybrid IT 

Watching Over Your Logs So You Don't Have To 


Did this answer your question?