Splunk ITSI (IT Service Intelligence) Reviews

I work in the telecommunication domain where we manage routers, WLAN services, and various other services from which we collect data. Based on the health of these services, we create health reports in Splunk ITSI (IT Service Intelligence). We have multiple sites with material controllers linked to different routers, and these routers connect to different devices, creating a hierarchy in our domain systems. We receive services with different metrics, and based on those services, we visualize our health report in Splunk ITSI (IT Service Intelligence).

Regarding Splunk ITSI (IT Service Intelligence), we have not contacted support directly, but we have requested support for some use cases in Splunk core.

We have a partnership with Splunk. Based on our pricing and license, they provided 800 hours for a year, making them available for 800 hours throughout the year. We typically have weekly calls with the technical staff, and whenever we encounter issues, they usually reply with solutions within one or two days.

Two or three features I appreciate most about Splunk ITSI (IT Service Intelligence) are the Service Analyzer, which is the main component of Splunk ITSI (IT Service Intelligence), and the Glass Tables. We also have maintenance scheduling features built into Splunk ITSI (IT Service Intelligence).

These are the core functionalities we use extensively in Splunk ITSI (IT Service Intelligence). We use features such as deep dives and KPIs frequently, which are foundational features. These are built-in, and we build additional features based on services and KPIs. On top of that, we create Service Analyzer dashboards and Glass Tables. One valuable feature is the scheduled maintenance window provided by Splunk ITSI (IT Service Intelligence) because Splunk does not offer this scheduling maintenance feature in the core product, but Splunk ITSI (IT Service Intelligence) helps us with these maintenance reports. Overall, I appreciate three or four features in Splunk ITSI (IT Service Intelligence).

The installation process is the first aspect I dislike about Splunk ITSI (IT Service Intelligence). If you do not configure it correctly, you will encounter issues in the search head. Because we use a distributed environment where each component has its own specific roles, installation is critical and requires careful attention. Splunk ITSI (IT Service Intelligence) is built with many applications. It is a compressed file, and when you extract the Splunk ITSI (IT Service Intelligence) app, you receive approximately 19 apps. Some applications, add-ons, and packages must be installed on specific components. If you do not configure an application correctly, it will not work. Sometimes we encounter issues during installation because of this complexity. I believe the installation process should be more uniform, meaning it could be deployed across all components to avoid post-installation issues. Sometimes after installation, you receive errors, and users cannot access Splunk ITSI (IT Service Intelligence). We have experienced this type of issue due to installation errors.

I believe there is currently room for improvement regarding scalability. When we create Glass Tables containing many searches, the Glass Tables sometimes fail due to memory constraints, and we receive error pages. Splunk ITSI (IT Service Intelligence) should have a lightweight version to address these concerns. I would rate current scalability as medium.

I have observed that Splunk ITSI (IT Service Intelligence) fails if you do not have good hardware requirements. It fails because Splunk ITSI (IT Service Intelligence) itself is a resource-heavy package containing many JavaScript and Python scripts. It requires good hardware requirements on both Linux and Windows systems to function properly.

I believe there is currently room for improvement regarding scalability. When we create Glass Tables containing many searches, the Glass Tables sometimes fail due to memory constraints, and we receive error pages. Splunk ITSI (IT Service Intelligence) should have a lightweight version to address these concerns. I would rate current scalability as medium.

We have a partnership with Splunk. Based on our pricing and license, they provided 800 hours for a year, making them available for 800 hours throughout the year. We typically have weekly calls with the technical staff, and whenever we encounter issues, they usually reply with solutions within one or two days.

I would give Splunk support a score of seven.

Positive

The installation process is the first aspect I dislike about Splunk ITSI (IT Service Intelligence). If you do not configure it correctly, you will encounter issues in the search head. Because we use a distributed environment where each component has its own specific roles, installation is critical and requires careful attention. Splunk ITSI (IT Service Intelligence) is built with many applications. It is a compressed file, and when you extract the Splunk ITSI (IT Service Intelligence) app, you receive approximately 19 apps. Some applications, add-ons, and packages must be installed on specific components. If you do not configure an application correctly, it will not work. Sometimes we encounter issues during installation because of this complexity. I believe the installation process should be more uniform, meaning it could be deployed across all components to avoid post-installation issues. Sometimes after installation, you receive errors, and users cannot access Splunk ITSI (IT Service Intelligence). We have experienced this type of issue due to installation errors.

One person can perform the installation, but that person must have strong admin knowledge.

The installation timeline depends on the infrastructure. In our case, it took one day for the installation.

Splunk ITSI (IT Service Intelligence) is maintained by our customer, so I am not certain about the pricing. It is a paid product, so you cannot download it directly. It is not publicly available. You need to obtain a license. In our case, the client already purchased Splunk ITSI (IT Service Intelligence), and it has a limited number of downloads or access after providing an email. Currently, no one can download it, which makes the pricing unclear to me. I believe the pricing is based on daily volume ingestion.

Splunk ITSI (IT Service Intelligence) has good visualization capabilities. The Glass Tables are another strength. The Glass Tables have minimal control features. They are similar to the Dashboard Studio in Splunk core, but Glass Tables have less control compared to the standard Dashboard Studio.

I want to add that Glass Tables are similar to the Dashboard Studio; however, Glass Tables have some limitations compared to the Dashboard Studio that I wanted to highlight.

I have used an infrastructure monitoring add-on related to infrastructure monitoring. I have also used the Splunk ITSI (IT Service Intelligence) Essentials add-on. I do not believe those add-ons are currently available in the Splunk base.

Splunk ITSI (IT Service Intelligence) requires Java JRE 1.8 after installation on your end. Java must be present on the server for Splunk ITSI (IT Service Intelligence) to work. There is one additional requirement I do not recall entirely, but Java and certain versions must be compatible with the Splunk version. For example, if you are using Splunk version 7, it should be compatible, but currently, Splunk has version 10.

Whenever we install Splunk ITSI (IT Service Intelligence), the search head should have good RAM, virtual CPUs, and local disks to maintain Splunk ITSI (IT Service Intelligence).

I believe incident management features are achieved by the Episode feature in Splunk ITSI (IT Service Intelligence).

We have not used that use case for incident management, but in the course content, there are alerts, and we maintain incidents with the Episodes feature. They have that feature available, so it can be handled by the Episodes feature in Splunk ITSI (IT Service Intelligence).

In Splunk ITSI (IT Service Intelligence), there are Notable Events provided that help manage alert fatigue within our team.

It is the same as the Dashboard Studio, but there are some limitations in the Glass Tables. Customized dashboards are not fully supported as they are in core Splunk.

I believe Splunk ITSI (IT Service Intelligence) is a large package, and I may not have explored most of the features. Whatever I have explored has been beneficial. I would give Splunk ITSI (IT Service Intelligence) an eight out of ten rating.

We have a partnership since Infosys is a partner of Splunk. There is a partnership in place, but we are a service-providing team. We provide services to our clients who are also partners of Splunk.

I use Splunk ITSI (IT Service Intelligence) as a manager of the managers, a tool sitting on top of all the other observability tools. It gets the alerts feed from all the sources such as Splunk Enterprise, AppDynamics, and ThousandEyes, and within Splunk ITSI (IT Service Intelligence), with its service intelligence and topology mapping, it creates the impactful journey that shows what service is dependent on what and that rich correlation happens within Splunk ITSI (IT Service Intelligence) policies.

In a large enterprise such as ours, we have several business services to be monitored and log collection to be done. Splunk ITSI (IT Service Intelligence) has been there for quite some time now and we use it for event correlation and as our AIOps engine.

The best features in Splunk ITSI (IT Service Intelligence) are that it acts as our single pane of glass for monitoring. All the alert feeds feed into it, and our command center team gets rid of the problem of the swivel chair, where they used to look at multiple screens before Splunk ITSI (IT Service Intelligence). With Splunk ITSI (IT Service Intelligence), all alerts feed into one tool, providing rich dashboards and visualizations for our team to look at, making it a standout feature.

We have used Splunk ITSI (IT Service Intelligence)'s incident management features, including an integration between Splunk ITSI (IT Service Intelligence) and our ServiceNow instance, which is our main ITSM and CMDB. We have created Notable Event Aggregation Policies in Splunk ITSI (IT Service Intelligence) to make episodes which call incidents. This allows us to create automatic and direct incidents to the service owners based on the smart correlation happening within the platform. We are doing incident management, and it's pretty smart and automatic.

We do utilize Splunk ITSI (IT Service Intelligence)'s intelligent alerting as proactive monitoring has always been our priority, ensuring we always monitor our stack. The event correlation and intelligence that Splunk ITSI (IT Service Intelligence) provides can correlate events from different sources and predict issues by observing trends and threshold breaches. We use that for getting proactive alerts, allowing us to see potential issues firsthand, checked by the SREs for validation. The intelligence within the platform is good and helps us stay on top of production issues.

Splunk ITSI (IT Service Intelligence)'s intelligent alerting has significantly helped manage alert fatigue within our team, especially with the large volume of alerts we face that previously overwhelmed teams. Splunk ITSI (IT Service Intelligence) has enabled noise reduction by deduplicating alerts based on specific keys and its own intelligence. We have also defined custom policies for grouping alerts, resulting in a significant reduction in alert volume, fewer incidents, richer context, and lesser queues for incidents in ServiceNow.

Splunk ITSI (IT Service Intelligence)'s customizable dashboards greatly facilitate our team's ability to monitor critical business services, as we create dashboards catered to different personas of users. The command center dashboards we have created in Splunk ITSI (IT Service Intelligence) are quite rich with detailed context, and we also developed a dashboard for our business and C-level users for a top-level view, referred to as the CTO dashboards. Additionally, we have SRE dashboards created, providing us flexibility with custom dashboards, along with some valuable out-of-the-box ones we utilize.

In terms of improvements for Splunk ITSI (IT Service Intelligence), I would suggest adding more out-of-the-box plugins and adapters, especially as there is a high demand for observability and dashboarding around AI observability. Despite the growing interest in AI observability, there are not many available plugins in Splunk ITSI (IT Service Intelligence) that are either out-of-the-box or recommended by vendors. More emphasis on this aspect in the future would be beneficial.

Regarding missing features in Splunk ITSI (IT Service Intelligence) that I would like to see included in the future, it would be beneficial to have the possibility of performing real-time call-outs. We currently have an integration with PagerDuty for that purpose, but if Splunk ITSI (IT Service Intelligence) could handle real-time call-outs automatically—not just incident creation—this would reduce our dependency on PagerDuty and consolidate processes within Splunk ITSI (IT Service Intelligence).

I have been working with Splunk ITSI (IT Service Intelligence) for around one and a half years.

Regarding stability, we have hardly experienced platform-level outages with Splunk ITSI (IT Service Intelligence). Occasionally, we have faced some slowness, which we reported to Splunk, and those issues were promptly resolved. Overall, we have not encountered significant downtimes, only instances of slowness.

In terms of scalability, we have not experienced any issues with Splunk ITSI (IT Service Intelligence)'s scalability. We anticipated the volume of alerts during the license purchasing process, and it handles the incoming alerts well.

I would evaluate customer service and technical support from Splunk as good. We have regular monthly catch-ups with the vendor and a weekly call to review our support cases. We receive direct responses regarding support cases, and if needed, our technical account manager is able to follow up during our weekly sessions. We also have leadership monthly sessions, ensuring we maintain regular contact with them and find them approachable.

On a scale of one to ten, I would rate the technical support as around eight out of ten.

Positive

Prior to adopting Splunk ITSI (IT Service Intelligence), we looked at a different product called BigPanda during a proof of concept. We evaluated its features, but ultimately, we did not choose it for deployment, selecting Splunk ITSI (IT Service Intelligence) over it instead.

I am not directly familiar with the initial setup process or deployment of Splunk ITSI (IT Service Intelligence), as that occurred before I joined the organization. However, I am somewhat aware of the setup process and its requirements.

The key differences between Splunk and BigPanda revolve around nativities; our underlying monitoring tool stack originates from the same enterprise. Splunk Enterprise, ThousandEyes, and AppDynamics naturally integrate with Splunk ITSI (IT Service Intelligence), whereas with BigPanda, custom intelligence creation would be necessary. Although BigPanda had many features, the alignment with our observability tools makes having everything from one vendor more efficient, reducing the complexity of managing multiple vendors.

My advice for organizations considering Splunk ITSI (IT Service Intelligence) is to recognize that many still rely on observability tools as the last mile for monitoring alerts. Integrating an AIOps layer, such as Splunk ITSI (IT Service Intelligence) on top of existing monitoring tools, significantly aids in noise reduction and alleviates alert fatigue. I find it quite useful, and I would recommend it to other enterprises, whether large or medium scale, as they would likely see a reduction in incidents, improved smart correlation, and quicker resolution of service issues through predictive analysis. I would rate this solution an eight out of ten overall.

I recommend Splunk ITSI (IT Service Intelligence) for large enterprises and the government sector.

The best features of Splunk ITSI (IT Service Intelligence) are the APM, the Application Performance Monitoring, and the diagnostic capabilities. It is state-of-the-art.

The intelligent alerting in Splunk ITSI (IT Service Intelligence) is very good. The predictive analysis can give you proactive information about potential bottlenecks that can occur on applications, desk, storage, SQL servers, databases, or other systems. It is very effective.

The customizable dashboards in Splunk ITSI (IT Service Intelligence) facilitate our customers because they are highly adaptable. We have multiple types of dashboards, depending on who will be utilizing them, such as engineering, middle management, IT heads, or NOC teams that will be monitoring systems.

The metrics I rely on for monitoring in Splunk ITSI (IT Service Intelligence) depend on what kind of asset or CI we are monitoring. For applications, we have the number of concurrent transactions, response time from the database, and write time on the desk. There are multiple parameters and metrics that we utilize in the monitoring part within ITSI.

Splunk ITSI (IT Service Intelligence) can be improved in terms of the service management function, which is the only drawback, and there are some limitations in terms of event correlation, specifically when correlating between different CIs. If this were fixed, it would be an amazing function, with cross-correlation between different CIs.

I would appreciate additional features in the next release of Splunk ITSI (IT Service Intelligence) such as cloud infrastructure monitoring including CICDs, Kubernetes, and similar technologies. This would be brilliant.

I have been working with Splunk ITSI (IT Service Intelligence) for four years now, or possibly more.

If you are looking for only a shallow solution, there are other alternative options that can be useful for such purposes.

Other Splunk products are much better, including Splunk ITSI (IT Service Intelligence), EPM, Enterprise Security, and core. Everything is perfect.

It is not suitable for smaller companies because they do not need it and it is expensive. It will be very expensive and complex for them.

The implementation process for Splunk ITSI (IT Service Intelligence) is complex, but this is typical for this type of product.

I do not utilize its incident management features much; we typically integrate Splunk ITSI (IT Service Intelligence) with other ITSM solutions for incident management. We do not utilize the service management modules because it is not what it is meant to do. We only use it for data diagnostic, alert management, performance, proactive monitoring, diagnostic, and event correlations related to performance or availability.

The impact of ITSI's predictive analytics on decision-making processes is very good.

Concerning performance, scalability, and interface, everything is perfect.

On a scale of 1-10, I rate this solution a 9.

My use case for Splunk ITSI (IT Service Intelligence) is for alerting and monitoring my inventory, specifically my organization inventory.

The best features of Splunk ITSI (IT Service Intelligence) are event correlations and predictive analysis, especially the glass tables where we can view the analysis of our inventory. This allows us to track inventory observability effectively, helping us react when something unusual occurs, prompting alerts. We have integrated it with an ITSM tool, so we receive alerts there.

Using the incident management feature in Splunk ITSI (IT Service Intelligence) has significantly improved our operations. Our CloudOps team used to utilize an earlier logic monitor, which was difficult to handle. Now, we set thresholds, enabling both the Infosec team and the CloudOps team to receive alerts that fall under compliance, which has helped us greatly.

Using intelligent alerting in Splunk ITSI (IT Service Intelligence) has definitely helped considerably. Instead of creating manual alerts, we pass some scripts to assign groups, which reduces our workload. We don't need to create ITSM tracking tickets as it's integrated, leading to automation that saves us time and ensures we don't lose sight of any production service issues. Our goal is to maintain observability within our control.

One area where Splunk ITSI (IT Service Intelligence) has room for improvement is the high cost associated with it.

At times, there is a complex setup required for Splunk ITSI (IT Service Intelligence). Once it is established, it becomes easy to use, but the initial setup can be challenging, particularly around integration.

I think the integration aspect of Splunk ITSI (IT Service Intelligence) could improve, especially regarding dashboards and inventory alerts. It would be beneficial to have more reliable features and additional fields instead of relying on multiple options for team alerts, as this is somewhat complicated for users.

I have been using Splunk ITSI (IT Service Intelligence) for around three years.

When discussing stability, I mean the application's performance without crashing or issues. I rate the stability of Splunk ITSI (IT Service Intelligence) an eight, which indicates good performance despite occasional downtimes or bugs.

I would also give Splunk ITSI (IT Service Intelligence) an eight for scalability, indicating it performs well in that area. However, scalability may vary depending on licensing and specific circumstances in large-scale environments.

For technical support from Splunk, I would rate them an eight; they are quite effective.

Positive

Our CloudOps team used to utilize an earlier logic monitor, which was difficult to handle.

The deployment of Splunk ITSI (IT Service Intelligence) is not complex; I can confidently say it is straightforward.

We have a partnership with Splunk, which has been in place for a long time, and that is how we acquired the product.

Regarding ROI percentage, we estimate a 30 to 35 percent saving on resource costs and around 25 to 30 percent savings on inventory expenses, all credited to utilizing Splunk ITSI (IT Service Intelligence) effectively. In terms of return on investment, we have saved resources significantly and reduced costs for our cloud inventory by working primarily within Splunk ITSI (IT Service Intelligence), rather than using other tools. This has allowed us to benefit considerably.

Regarding pricing, I find it to be quite high, which could pose a challenge for customers. I believe Splunk should review this pricing, especially considering its acquisition by Cisco. Regarding pricing, I would rate Splunk ITSI (IT Service Intelligence) an eight out of ten, indicating a high expense level.

When comparing Splunk ITSI (IT Service Intelligence) with other solutions such as Dynatrace, Elastic, or BMC, I find everything is available in Splunk. Integrating with other tools could lead to additional maintenance and resource needs, which makes me inclined to continue using Splunk.

When comparing Splunk ITSI (IT Service Intelligence) with other solutions such as Dynatrace, Elastic, or BMC, I find everything is available in Splunk. Integrating with other tools could lead to additional maintenance and resource needs, which makes me inclined to continue using Splunk. For those looking to implement Splunk ITSI (IT Service Intelligence), I generally advise that it may not be suitable for small businesses due to costs. Medium companies can consider it, while larger organizations are likely to find it beneficial. I definitely would not recommend Splunk ITSI (IT Service Intelligence) for small organizations, as it would be too costly for them. I have given this review an overall rating of eight.

I use Splunk ITSI (IT Service Intelligence) to determine if our network traffic is healthy, to identify abnormalities in our hardware, and to define KPIs while asking it to provide a score based on the KPI and event analytics.

Customizable dashboards help with my team's ability to monitor critical business services. Now we can create dashboards as we want, which is easier compared to previously.

Dashboards provide visualization and deep dive for root cause analysis, which we had to build previously. Those logics had to be built manually, but now the system can do it on its own when we ask it.

From my experience of working with Splunk ITSI (IT Service Intelligence) for two years, the most beneficial aspect for me is that it is AI-enabled, providing us with very good analytics. Analytics that we used to do manually can now be completed automatically, and the system can create tickets for us automatically.

The Intelligent Alerting feature helps to manage alerts and alert fatigue. It pops up even for things which we have not configured, which was not a feature before.

The Incident Management feature helps me with operations. Earlier, somebody had to analyze issues and then manually create a ticket, but now the system automatically creates tickets for us.

I see areas for improvement in Splunk ITSI (IT Service Intelligence) such as cost, which is high. The subscription cost is high. Upgrades are a problem and support needs improvement.

Regarding support, it is not easy. They always give remote support, but if you want to physically talk to someone, that becomes difficult because not every problem can be explained using vocabulary. Some problems are better explained in person and demonstrated directly. Those problems are difficult to explain, and especially with an on-premises deployment, it becomes more difficult because we have to interact outside and share data.

Regarding upgrades, the issue is that because it is on-premises, upgrades become complex for us. On-cloud upgrades are easy, but on-premises upgrades are very painful.

I have been using this solution for two years now.

Stability is good with Splunk ITSI (IT Service Intelligence).

Scalability is not a big challenge with Splunk ITSI (IT Service Intelligence).

I would rate support from zero to ten points at six points, maximum.

Positive

I have worked with other products similar to Splunk ITSI (IT Service Intelligence). We are currently working with Armis, which is a cloud platform for vulnerability management. We are also working with Dynamics 365 and CodeLabs, which is a dashboarding platform.

When comparing Splunk ITSI (IT Service Intelligence) with those products, I do not see significant differences because these are different types of products. Splunk ITSI (IT Service Intelligence) is more of an analytics platform, Armis is a vulnerability management platform, and CodeLabs is a dashboarding platform. These are different platforms, making them difficult to compare on an apples-to-apples basis.

In terms of Splunk ITSI (IT Service Intelligence) installation and deployment, I would say it is complicated, especially if it is on-premises.

In deployment, the challenge is that we cannot have them on call, as all support is remote. When we are stuck with an error, having them come back and us responding takes a lot of time. If it was a remote support situation where they come on a call and we discuss and troubleshoot together, it would become very easy.

Concerning the price, I mentioned it is a costly solution, but I see some return on investment here. Any return on investment is difficult to quantify because this is for risk management. Risks can mean that if one failure happens, it can result in risks in hundreds of thousands of USD. If nothing happens, these platforms provide value for our setup. The value can only be realized when these platforms are not there because when you see alerts and find abnormalities, you take action and mitigate the risk. This is why I am saying that this is for risk, so it is difficult to put a price on ROI.

My current experience is basically limited to Splunk ITSI (IT Service Intelligence) and Azure, with Armis and Dynamics 365. These are different platforms, more on the application side of things. As for my experience in this domain as a Digitization Lead, I have eight years of experience. I would rate this product with an overall review rating of eight.

My use case for Splunk ITSI (IT Service Intelligence) involves getting raw data from the client, which we need to sort down into particular requirements like the device name, host name, the message body, and whatever errors we get from the particular client in a data source. That needs to be completely reorganized. Then we create a correlation search as per the data requirement or the data resource, how the client requires the incident to be created. After creating the correlation search, we create a notable event policy to align with what the client requires in his monitoring. Following that, we create tickets, or episodes. When an episode is created, a single alert is generated which can result in 50 to 60 alerts for the same message. After that, with many alerts for one episode, we create an incident that connects to ServiceNow.

The best feature I found in Splunk ITSI (IT Service Intelligence) is the ability to organize raw data we receive in a very particular manner as per the client's requirement, including the device name and message body. We can then create tickets by utilizing multiple data sources connected to a single correlation search, which we can integrate into notable events to identify which data sources are generating the highest severity alerts that need to be resolved as soon as possible. Notable event policy puts the episodes that highlight issues which require immediate attention, and these are then escalated to ServiceNow. This makes it very easy to clarify incidents and understand that there is an issue in a particular system. We can create a proper dashboard to monitor regular events occurring from a single data source. As per event occurrences, the data goes into correlation search to create episodes based on alerts or severity. If an episode indicates a high-risk issue, then it is moved into ServiceNow where the ticket is created immediately.

Regarding incident management in Splunk ITSI (IT Service Intelligence), it has helped the client transition from a different device tool to a cloud tool, with the complete data being moved to the cloud. During this transition, some data may go missing, which is where we use the heavy forwarder to capture that missing data and integrate it into the cloud. As per the client's issues, the events that might be missing are displayed on the dashboard, which will then go into correlation search. If any issue arises or presents a high risk, it is quickly escalated to notable events, episodes, and subsequently, an incident is created.

As per my analysis of Splunk ITSI (IT Service Intelligence), I do not see much room for improvement. My experience as a mid-level user suggests that deep knowledge is helpful to maximize the tool's potential, but overall, I do not identify any significant areas needing improvement.

I have been using Splunk ITSI (IT Service Intelligence) for the past one and a half years.

I would rate the stability of Splunk ITSI (IT Service Intelligence) as a perfect ten; it is an extremely stable tool.

Splunk ITSI (IT Service Intelligence) demonstrates good scalability, and I would rate it around 8 or 8.5 for its capacity to adapt and be utilized effectively.

I would rate Splunk ITSI (IT Service Intelligence) support at nine or 9.5 because it is a highly effective and handy tool. Although it is costly, the experience remains very positive.

Positive

For intelligent alerting in Splunk ITSI (IT Service Intelligence), whenever we miss any alert, the episode easily pops up in our emails. The incident created is notified immediately via email, which helps us understand that this alert requires immediate resolution.

Customizable dashboards in Splunk ITSI (IT Service Intelligence) allow us to tailor events based on specific data sources according to our requirements. We can use the SPL code language, which is a specialized programming language for Splunk, to meet client needs. For instance, we can customize dashboards to display the App ID, severity, impact, assignment ID, and origin of the data. This customization ensures that users monitoring the dashboard can easily understand the critical events sourced from specific data streams, including severity and impact, and prioritize their resolution accordingly.

In my experience with predictive analytics in Splunk ITSI (IT Service Intelligence), it provides complete analysis, and it promptly indicates issues that need to be resolved, ultimately channeled to ServiceNow for incident creation. It analyzes data swiftly, moving the information we acquire into the processes of correlation search, notable events, episodes, and incident creation without delay.

Regarding the pricing of Splunk ITSI (IT Service Intelligence), although it is expensive, it proves to be handy and significantly aids in resolving our issues effectively.

When comparing Splunk ITSI (IT Service Intelligence) with other solutions such as Grafana, we find that Splunk offers much more seamless dashboard creation. In Grafana, we are required to download plugins and import data, which is cumbersome. However, with Splunk, we directly input data into heavy forwarders that dispatch to the index, making it straightforward to identify specific data sources received from clients and continue with incident creation processes.

Splunk can be deployed flexibly as per our requirements; primarily, we deploy it on Azure, but it can also be utilized on other platforms.

In our organization, there are eight specialists who work with Splunk ITSI (IT Service Intelligence).

The client we serve is on an enterprise level.

For Splunk ITSI (IT Service Intelligence), we do not need to perform any maintenance such as updates, patching, or renewals since the data from the client's own devices is directly transmitted to Splunk utilizing a heavy forwarder, negating the need for any patching.

I would strongly recommend Splunk ITSI (IT Service Intelligence) to other users since it serves exceptionally for those transitioning from conventional devices to the cloud, allowing for regular updates and alert notifications about issues within their organization. Splunk offers a significant advantage in promptly addressing alerts for critical severity issues. However, a minor disadvantage is that alerts must occur multiple times before incidents are created; for instance, if the same event occurs only once or twice, an incident may not be generated immediately, whereas repeated occurrences will lead to prompt incident creation.

Although I recommend Splunk ITSI (IT Service Intelligence), I advise potential users to thoroughly understand what Splunk does and how it aligns with their requirements before adaptation. If their goal is only to migrate data to the cloud, it might not be the best choice, but if they need a monitoring tool to create and quickly resolve incidents, it proves beneficial. I would rate this review a nine overall.

Splunk ITSI (IT Service Intelligence) is primarily used for our applications like telecom and digital applications where we have online transactions, leveraging it for our observability of daily transactions to predict failures beforehand.

For instance, we have digital telecom applications for the UK where people conduct transactions on the website, and from there, we collect different feeds and input them into Splunk ITSI (IT Service Intelligence). We analyze these feeds, such as 10% or 20% of all those feeds, to predict service failures, allowing our team to rectify errors before they affect the application.

What I appreciate most about this use case is that Splunk ITSI (IT Service Intelligence) offers both an early warning system and a dashboard.

We use Splunk ITSI (IT Service Intelligence) to give more visibility into the health of our business service and infrastructure, mainly for AIOps in IT operations. We use AI-driven monitoring analytic solutions to combine infrastructure, application, and network data to gain valuable insights.

Splunk ITSI (IT Service Intelligence) definitely correlates the data, reduces alert noise, and predicts issues in a very short time. These are the three main features I find valuable.

Regarding the features, ease of use can be challenging for some newcomers, but once they become familiar, it offers great visualization capabilities and helps reduce MTTR from incident intelligence and AIOps. I particularly appreciate creating baselines for normal behavior, detecting anomalies, and dynamically adapting thresholds.

Splunk ITSI (IT Service Intelligence) positively impacts my organization by predicting many failures beforehand, helping us save money and preventing business disruptions by allowing us to address issues early.

While I do not have specific numbers right now, I can say it improves application failure rates and reduces MTTR by minimizing event noise, allowing us to focus only on issues that cause real problems.

To improve Splunk ITSI (IT Service Intelligence), we could enhance automatic discovery features, suggesting weightage for different levels based on templates users provide.

I believe more training is beneficial, such as visualization training for users, alongside clearer documentation and tutorial videos to assist them.

I have been using Splunk ITSI (IT Service Intelligence) for the last four years.

In my experience, Splunk ITSI (IT Service Intelligence) is stable, but we initially faced performance issues that improved after we increased the servers' GPUs, allowing us to handle more metrics and data collections effectively.

Splunk ITSI (IT Service Intelligence) scalability allows us to predict analytics such as service degradation and perform root cause analysis through metrics, logs, and traces, which can improve further by utilizing cloud servers.

Customer support is adequate, but it could be faster, especially with P1 issues, and having more instructional videos available would help.

Neutral

We previously used Dynatrace and AppDynamics before switching to Splunk ITSI (IT Service Intelligence).

Before choosing Splunk ITSI (IT Service Intelligence), we evaluated options such as AppDynamics and Dynatrace, ultimately finding Splunk ITSI (IT Service Intelligence) more useful for comprehensive data collection, response times, and cybersecurity strength.

I advise others looking into using Splunk ITSI (IT Service Intelligence) to explore all the available resources and videos before implementation.

Splunk ITSI (IT Service Intelligence) is a great product, and I encourage others to use it, but I believe adding more training videos and user-friendly resources would greatly enhance the experience. I would rate this product an 8 out of 10.

For the usual use cases for Splunk ITSI (IT Service Intelligence), we are using features like Service Analyzer and KPI models and we use it mostly for alert correlations. We analyze from Splunk ITSI and Splunk, and we correlate it to see whether that issue is correlating with any application issue or not. This helps us to quickly identify impacted services and KPI monitoring and allows us to monitor our overall infrastructure.

Currently, we are not using Splunk ITSI (IT Service Intelligence)'s incident management features because we are only using it for correlating, and after correlating, we do create an incident from the Splunk perspective. If we detect an issue from Splunk and we get to know that we have this information in Splunk ITSI (IT Service Intelligence), we correlate it, and if we find anything, then we are creating an incident from Splunk itself.

For alerting with Splunk ITSI (IT Service Intelligence), we are only alerting a very basic feature, such as emailing to our management the current statistics or current report, or we have a scheduled daily report. They can view daily impacted systems or how much time we have remediated it and what the current status is.

The most valuable features of Splunk ITSI (IT Service Intelligence) in terms of the KPI, like Key Parameters Index, are used mostly by our management. They do not prefer metrics only; they prefer graphs and visualizations. So they only see Splunk ITSI (IT Service Intelligence) dashboards and they use Service Analyzer. We directly explain to them that a particular service was in an outage and a specific issue was triggered and that was the issue. We can already show in the graph that there was a spike, such as CPU usage spike or disk spikes or memory leakage. We can directly show it to them without needing to manually calculate. Splunk ITSI (IT Service Intelligence) calculates the service health based on our KPIs and scores and it helps us to monitor services instead of just infrastructure. This provides more detailed analysis to our systems, and as I mentioned, for the alert correlation features in Splunk ITSI (IT Service Intelligence).

Splunk ITSI (IT Service Intelligence) helps manage alert fatigue within my team. In terms of alerts, we monitor multiple of our internal websites or endpoints, where teams were getting immediate notifications that a particular site was down. They were very proactive and they would remediate it immediately.

Splunk ITSI (IT Service Intelligence)'s customizable dashboards have really helped a lot in facilitating my team's ability to monitor critical business services. We can create our own custom dashboard where we like to show it to our management. As I mentioned, they don't prefer messy parameters or parameters that they actually don't understand. They want straightforward information on the dashboards, which they can use to decide factors about the business. We do have customized dashboards for that.

We mostly rely on health monitoring metrics within Splunk ITSI (IT Service Intelligence) such as CPU metrics, memory metrics, current service usage metrics, how many services are running, and what service is capturing what memory. We monitor our current usage of a particular endpoint or website, whether it is responding in a late time, what its response time is, and if it is responding, how much content it is responding with, what is the length of the response, and other related metrics.

I do not see much improvement needed for Splunk ITSI (IT Service Intelligence) as we are not facing any significant issues or haven't explored all the features. A small suggestion would be if there were more documentation of Splunk ITSI (IT Service Intelligence) to be easily configured by the end-user who does not really have a deep knowledge about Splunk ITSI (IT Service Intelligence). If they provide some tutorials on how to use it or give any user sessions where they explain their features and how they can use it in their organization, that would be really valuable.

I have been working with Splunk ITSI (IT Service Intelligence) for not very long, only around four months.

Splunk ITSI (IT Service Intelligence) is pretty stable for us. We have not faced any major issues or outages due to Splunk ITSI (IT Service Intelligence).

On a scale from one to ten, I would rate the scalability level of Splunk ITSI (IT Service Intelligence) as eight.

I have not personally communicated with the technical support and customer service of Splunk ITSI (IT Service Intelligence), but my colleague had an issue with Splunk ITSI (IT Service Intelligence) and he contacted Splunk support, and they were able to provide the solution. It was good, and we have had no specific issues with Splunk support; they are really good with their support.

There was no delay from Splunk ITSI (IT Service Intelligence)'s support; it was a straightforward solution, and they took around four and a half hours or half a day, and it was resolved.

Based on that experience, I would rate the technical support of Splunk ITSI (IT Service Intelligence) from one to ten as nine.

Before Splunk ITSI (IT Service Intelligence), we did not use a different solution for the same use cases. We were using our custom solutions, creating our own scripts to trigger or check some features on the system and alert, but it was failing because that service was running on that system. Due to that, we were looking for a service that will monitor from anywhere, and we found that Splunk ITSI (IT Service Intelligence) is what we can implement. Currently, we are in a trial and error phase in terms of that.

I was not part of the initial setup and deployment of Splunk ITSI (IT Service Intelligence), so I don't know much about it. I only used its services and configurations.

We did not evaluate any other technologies other than Splunk ITSI (IT Service Intelligence) before; we were using only our custom solutions.

I don't know the pricing of Splunk ITSI (IT Service Intelligence) as of now because we have recently purchased it and it was not purchased by me. However, as I understand, it is based on the indexing of our Splunk, so I would say it will not be that high because we were ingesting only limited data to Splunk ITSI (IT Service Intelligence).

As of now, we are not using Splunk ITSI (IT Service Intelligence) that much, so it is pretty good for our infrastructure and whatever use cases we are working on. I would rate this review an eight overall.

The main use case for Splunk ITSI (IT Service Intelligence) is monitoring events. I also use it for reporting on the availability of services.

One example of how I use Splunk ITSI (IT Service Intelligence) in my day-to-day work is monitoring the ejection rate of remote sites. I have equipment engineers log the data, and then I index the logs into Splunk ITSI (IT Service Intelligence). I use those indexed events to perform calculations and evaluate performance every 15 minutes. Whenever there is a drop in performance, I quickly take action. This enables me to avoid big incidents and major issues.

The best features that Splunk ITSI (IT Service Intelligence) offers are the real-time indexing. It is very powerful and has helped me tremendously.

Real-time indexing in Splunk ITSI (IT Service Intelligence) has helped me by requiring me to take actions as soon as possible before the customer even notices the issue. Splunk ITSI (IT Service Intelligence) offers excellent calculation options.

Splunk ITSI (IT Service Intelligence) has impacted my organization positively because it helps me take action before an incident happens. I use predictive maintenance-based analysis.

Before switching to Splunk ITSI (IT Service Intelligence), I didn't have any type of IT solution.

Splunk ITSI (IT Service Intelligence) can be improved because there are some events that get missed in indexing, especially on the stats and AC stats. If I could have 100% of events indexed in Splunk ITSI (IT Service Intelligence), that would definitely make my reports more accurate and help me take informed actions.

I have been using Splunk ITSI (IT Service Intelligence) for the past five years since I joined the company.

In my experience, Splunk ITSI (IT Service Intelligence) is very stable.

Contribution-wise, Splunk ITSI (IT Service Intelligence) is great and very much scalable. It can be used in various departments for various specific cases.

So far, the customer support for Splunk ITSI (IT Service Intelligence) is great. I haven't logged many tickets, but for the few ones that I have submitted, I have received good feedback.

Positive

Before predictive maintenance in Splunk ITSI (IT Service Intelligence) was implemented, I was working on planned maintenance that was time-based. With predictive maintenance, I now have all the sensor data coming from the printer, and I can predict that the printer is going to fail in about 20 to 30 minutes. Then I send the technicians on the page before an incident, and this helps me reduce the downtime.

I wasn't involved in the choosing process or evaluating other options before choosing Splunk ITSI (IT Service Intelligence).

I have definitely seen a return on investment with Splunk ITSI (IT Service Intelligence).

My advice to others looking into using Splunk ITSI (IT Service Intelligence) is to be creative with it. The power is huge, so be creative.

I use Splunk ITSI (IT Service Intelligence) specifically for monitoring and alert management with a logistics vendor. It provides auto-ticketing functionality with ServiceNow integration that automatically creates tickets when issues occur. Additionally, I monitor e-commerce checkout pages through an integrated dashboard where I check all components. We have a Service Analyzer where we examine this section as well. I monitor bookings in Splunk ITSI (IT Service Intelligence) and check the latency of transactions across booking service, checkout service, and hotels. I use Splunk ITSI (IT Service Intelligence) through the dashboard with auto-ticketing and implementations that include ServiceNow with bidirectional integrations.

Regarding incident management, I have implemented it with other third-party systems integrated with Splunk ITSI (IT Service Intelligence). For instance, I am implementing Splunk ITSI (IT Service Intelligence) with Zabbix. When Zabbix connects, it sends data to Splunk ITSI (IT Service Intelligence), and I use episode-based correlation in incident management. When latency happens in Zabbix, it correlates with a notable event being triggered. I need to check those episodes by examining first event correlation and then episode creation with that particular incident to manage things effectively. If the incident is coming from the same host with CPU higher than eighty percent, it will combine that particular incident within that ticket. If it is from a different host, then the episode breaks. This is how I manage those incidents.

I use the intelligent alerting feature in Splunk ITSI (IT Service Intelligence). Intelligent alerting helps in reducing alert fatigue by using adaptive thresholds and a dynamic alerting system that I use for breaches. I use machine learning within Splunk ITSI (IT Service Intelligence) where event correlation is created. Throughout the day, there is very less traffic in the morning time, and it peaks during US hours. Based on that, I create the adaptive threshold, and the intelligence helps me in creating that event correlation and breaking episodes according to the dynamic threshold. For anomaly detection, I check sudden traffic spikes and analyze deviations first to avoid false positives. For example, during a cyber attack, I send details to Splunk and map it in MITRE, where it checks how many times a login was attempted, matching it against the dynamic threshold and triggering alerts.

For health monitoring, my primary metrics involve CPU latency or errors. I set up a Splunk health analyzer where I check KPIs, focusing on different KPIs based on infrastructure needs, including CPU and latency errors. Key metrics include TP99 and TP95 alongside customized metrics like booking thresholds and transaction monitoring. Depending on the context, when I worked in logistics, I monitored ticket creation issues, I focused on CPU, memory, thread activity, and database errors.

I find predictive analytics to be a favorite topic of mine as it aids the decision-making process significantly. I use agent-based predictive analysis, particularly in case scenarios. Before issues arise that affect real customers, I can predict potential problems. I utilize Real User Monitoring (RUM) and other scripts for this analysis, checking data points gathered by agents installed in various locations. In Splunk ITSI (IT Service Intelligence), I leverage anomaly detections and forecast models based on historical data to identify potential service outages.

The best features of Splunk ITSI (IT Service Intelligence) are specifically for dashboarding, with the best being KPI monitoring. In my previous organizations, such as BMO, I needed to check how the data looked, and I appreciated the dashboard. The Service Analyzer part is where I get all that information on a single site. I also prefer the health score. Specifically, with any issue in Splunk ITSI (IT Service Intelligence), I can create a health score by using correlation searches, and then all those metrics are included. The auto-ticketing part is excellent, and I have used it.

Regarding customizable dashboards, they absolutely help me monitor critical business services. In my previous company, during resells every Friday, I checked whether there were real bookings or if it was a bot attack. I employ various methods, including radical buzz terminology in the dashboard, and I use drill-down, post-process methods, and token-based approaches. I also utilize glass table for dashboards, enabling drag-and-drop functionality, allowing me to highlight errors, latencies, and bookings while changing colors and backgrounds according to my needs.

Regarding areas for improvement, I see potential in enhancing smart alerting features and improving real user monitoring for better observability within Splunk ITSI (IT Service Intelligence). Splunk ITSI (IT Service Intelligence) could benefit from better handling of observed events, and it would be useful to receive notifications about outages and the ability to connect with servers for test execution directly from the Service Analyzer.

I have been using Splunk ITSI (IT Service Intelligence) since 2020.

I rate stability as an eight, recognizing there are still some issues to address.

Scalability is a bit challenging, mainly if high loads are encountered. I faced several issues with high thread usage, so I would rate it around seven to eight, particularly considering that scalability is crucial yet can be premium in cost.

I would rate the technical support as eight point five to nine, reflecting my extensive experience over the past fifteen years with Splunk ITSI (IT Service Intelligence).

Positive

I have explored many tools in the market including Datadog, Elastic, and Grafana. While working on a project for a significant company, I appreciate how Splunk ITSI (IT Service Intelligence) allows for automatic ticket creations and excellent integration with other platforms such as Zabbix, which significantly simplifies data management without manual intervention.

Regarding pricing, since Splunk ITSI (IT Service Intelligence) is a flavor of Splunk, there are no fixed prices as it depends on data volume. It is indeed a premium app within Splunk. The pricing reflects usage levels, and compared to others in the market, Splunk ITSI (IT Service Intelligence) provides a reasonable solution.

For those looking to implement Splunk ITSI (IT Service Intelligence), I recommend it specifically for service-centric monitoring and KPI indicators, although I would not recommend it for security purposes. I gave this product a review rating of ten.