Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
$26
per month
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.
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
[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.
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.
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.
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.
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.
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.
Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...
