Splunk Enterprise

My main use case for Splunk Enterprise Platform  is to monitor and troubleshoot, perform incident analysis, and search and analyze applications and system logs to identify the root cause of issues. I create dashboards to monitor key metrics, configure alerts for critical events, and generate reports for the operation systems.

A specific example of how I used Splunk Enterprise Platform  to solve a problem occurred when users reported intermittent application failures in production. I used Splunk Enterprise Platform to search and correlate application and server logs using SPL. By filtering the logs based on timestamps and error codes, I identified repeated timeout exceptions that were caused by backend services. I created a dashboard to monitor these errors and configured an alert to notify the support team whenever the error count exceeded a threshold. This helped the team detect similar issues proactively and reduce troubleshooting time significantly.

In addition to troubleshooting and log analysis, I use Splunk Enterprise Platform for real-time monitoring of application and infrastructure, creating dashboards for operational visibility, configuring alerts for critical events, and generating reports for stakeholders. I use SPL to analyze trends, identify recurring issues, and support root cause analysis. Overall, Splunk Enterprise Platform helps me monitor system health, reduce incident resolution time, and improve operational efficiency.

Splunk Enterprise Platform offers numerous powerful features including powerful log search using SPL, real-time monitoring and alerting, interactive dashboards and visualizations, data indexing and fast search, centralized log management, role-based access control, scalability, and integrations with various data sources. These features help our organization monitor and troubleshoot our systems.

Out of those features, I find the combination of real-time monitoring and SPL search capabilities the most valuable in my day-to-day work. Real-time monitoring helps me identify issues as soon as they occur, while SPL allows me to quickly filter and analyze large volumes of logs to pinpoint the root cause. This significantly reduces the troubleshooting time. I also rely heavily on dashboards because they provide a clear view of application health, error trends, and system performance in one place. Centralized log management is another key advantage as it brings logs from multiple sources and servers together, eliminating the need to check each system individually. Overall, these features help me resolve incidents faster, improve system reliability, and reduce downtime.

An additional feature I truly appreciate is the flexibility of Splunk Enterprise Platform. It can ingest data from a wide variety of sources, such as application servers, operating systems, and network devices, and correlate all the information in a single platform.

In order to improve Splunk Enterprise Platform, there are a few areas that need improvement. The licensing model is based on data ingestion volume and can become expensive as organizations grow. The initial setup and configuration can also be complex for new users.

I would rate Splunk Enterprise Platform an eight because it is a powerful and reliable platform for centralized log management and real-time monitoring. It significantly improves our troubleshooting times. I did not give it a ten because the licensing costs can be high, the initial setup and administration can be complex, and there is a learning curve for SPL and advanced configurations.

I have been using Splunk Enterprise Platform for about two years.

Splunk Enterprise Platform is stable.

Splunk Enterprise Platform is highly scalable. It can handle increasing volumes of machine data by scaling horizontally, such as adding more indexes, search heads, and forwarders as an environment grows. This allows organizations to support more users, onboard additional data sources, and process large amounts of data.

I do not have direct experience managing Splunk Enterprise Platform at petabyte scale. However, based on my understanding, Splunk Enterprise Platform is designed to scale horizontally by adding indexes and search heads, which allows it to handle very large data volumes. For data sovereignty, it supports role-based access controls, encryption, and various deployment options.

My experience with customer support was great.

I have not previously used a different solution before Splunk Enterprise Platform; we directly adopted Splunk Enterprise Platform.

The initial setup and administration can be complex, and there is a learning curve for SPL and advanced configurations.

The setup was performed by our in-house team who are highly skilled in working with Splunk Enterprise Platform.

I definitely see the return on investment. Splunk Enterprise Platform improved our reliability, and the time to investment ratio has been excellent because the time we are spending solving incidents through Splunk Enterprise Platform has been great.

My experience with pricing, setup cost, and licensing indicates that the initial setup cost, and when the organization grows, the setup cost might increase significantly. The main costs considering Splunk Enterprise Platform are licensing, infrastructure, and setup. Since licensing is based on data ingestion volume, costs can increase as the organization generates more log data.

We did not evaluate other options before choosing Splunk Enterprise Platform; we directly chose Splunk Enterprise Platform as our first option.

My advice to others looking into using Splunk Enterprise Platform is that if there is an organization which is about to scale to large numbers, I would highly suggest Splunk Enterprise Platform. However, I would ask them to carefully check and ingest valuable data only for cost efficiency. I would rate this recommendation an eight out of ten.

My team and I use Splunk Enterprise Platform  for security monitoring, including collecting logs from firewalls, endpoints, servers, and cloud platforms, then compliance reporting, such as generating compliance reports for PCI DSS, SOC 2, and GDPR, log management including centralized logs from thousands of devices, infrastructure monitoring which includes monitoring CPU usage, memory utilization, disk space, and application monitoring including tracking application errors and response times, and various other purposes that arise day to day.

The most critical use case for Splunk Enterprise Platform  is security monitoring and threat detection because we can detect cyberattacks in real-time, correlate logs from multiple sources including firewalls, EDR, IDS, IPS, and Active Directory, which enables SOC analysts to identify suspicious activity quickly. For example, about one week ago, an attacker tried to exploit a SharePoint  vulnerability where Splunk Enterprise Platform detected multiple POST requests to suspicious SharePoint  endpoints, then execution of powershell.exe by the SharePoint service, then the creation of unknown DLL files. We detected that potential SharePoint exploit affecting the server SP Web 01, with indicators including suspicious PowerShell execution, web shell creation, and multiple failed authentication attempts.

Every day, we use Splunk Enterprise Platform to check security dashboards by logging into the platform and reviewing SOC dashboards for critical alerts, failed login trends, and malware detections, then monitor real-time alerts by continuously watching for alerts such as multiple failed login attempts, privilege escalation, or data exfiltration. When an alert is triggered, we investigate it by searching logs and identifying the affected user or device, and we follow up by reviewing authentication logs and correlating events. Instead of looking at one log source, we correlate multiple sources including VPN logs, DNS logs, and CrowdStrike EDR. We also conduct threat hunting by proactively searching for suspicious behavior when there are no alerts, respond to incidents by creating or updating an incident ticket, inform the incident response team, isolate the affected endpoint, and continue monitoring and generating reports as part of our day-to-day workflow.

Splunk Enterprise Platform handles massive petabyte-scale environments well, but asserting strict data sovereignty such as complying with localized regulations that prohibit data from crossing borders requires deliberate architectural planning. The strengths I can mention include decoupled storage, and by leveraging smart store, we can separate our high-compute indexer nodes from our storage tier to allow us to scale to multi-petabyte levels without inflating our compute costs and ensures our cold data resides within our approved geographic borders. There is also distributed search, allowing us to query vast quantities of historical data stored in different geographic nodes or sites without needing to centralize all the raw data into one massive physical repository. The challenges we face include the complexity of cross-border queries; while we can keep data locally sovereign, querying datasets across international or inter-regional boundaries can strain bandwidth and increase search latency while relying on distributed federated searches.

The use of Splunk's Federated Search has evolved from a troubleshooting fix into a deliberate architectural strategy for reducing ingestion costs and managing compliance constraints. Initially, it served as a way to occasionally bridge distinct geographical Splunk Enterprise Platform clusters, but today it acts as an active data fabric layer that queries multi-cloud data lakes and external remote environments in place without moving raw data.

My experiences with maintaining granular control over data using a trusted control plane within Splunk Enterprise Platform reflect a major architectural shift, moving data governance from a retrospective cleanup activity to an in-flight policy enforcer. In-flight governance at the edge uses a centralized cloud control plane executed locally on-premises or within region-specific infrastructure which allows us to control data before it leaves our boundaries, employing granular filtering, masking, and smart in-flight routing. My experience with provider-level access control for Federated Search involves using granular control to manage data sovereignty; Splunk Enterprise Platform's introduction of provider-level role-based access control enhances our experience and data management capabilities.

In consideration of new use cases including agentic AI architectures, Splunk Enterprise Platform's governance and RBAC transition from a passive security checklist into active execution guardrails. The crucial role they play in managing access to operational data for these use cases involves limiting the blast radius. An agent utilizes the permissions of the service accounts assigned to it. Strict RBAC ensures an agent designed for network troubleshooting cannot access sensitive HR logs or financial transactions. Governance  structures prevent LLMs from scanning unvetted data sources, stopping attackers from using prompt injection to trick an agent into exposing restricted system data. Access to operational data is managed through least privileged service accounts, whereby agents are assigned to highly specialized Splunk Enterprise Platform roles mapped to narrow indexes and limited data models. Real-time data masking using Splunk Enterprise Platform algorithms or ingest-time transformations strips PII and credentials before data hits the index, ensuring agents cannot interact with forbidden raw strings.

Among the best features that Splunk Enterprise Platform offers are real-time incident monitoring, real-time threat detection, the ability to investigate endpoints, a powerful Search Processing Language (SPL) which allows analysts to search and investigate huge amounts of data quickly, real-time alerts, dashboards, and data visualizations that greatly convert raw logs into graphs, charts, and reports. It also supports scalability, handling terabytes to petabytes of daily log data. It provides role-based access control which restricts data access based on user roles. It also features a machine learning toolkit that allows users to perform anomaly detection and predictive analytics. These features are critical for SOC analysts.

The most important feature for Splunk Enterprise Platform is SPL, which is the Search Processing Language, because it helps us search billions of events within seconds. It powers threat hunting and forensic investigations. It is used to create dashboards, alerts, and reports and almost every advanced feature relies on SPL. Strong SPL skills are among the most sought-after abilities for Splunk Enterprise Platform administrators and SOC analysts. For example, when a user reports that their account is compromised, with SPL we can quickly find all login events for that user, check failed login attempts, identify source IP addresses, see which systems were accessed, correlate activity with firewall, VPN, and endpoint logs, and build a timeline for the incident. A single SPL query can answer questions that would otherwise require checking multiple systems manually.

There are some useful features that Splunk Enterprise Platform users sometimes overlook, including data model acceleration which speeds up searches on large datasets, and this is very useful for SOC teams that need quick investigation results. There are also scheduled searches and automated reports which automatically run searches at set intervals and deliver reports to stakeholders without manual effort. Scalability is also important; whether we ingest a few GB or several TB of logs per day, Splunk Enterprise Platform's distributed architecture allows it to scale with enterprise needs. Role-based access control allows different teams to access only the data they need, which improves both security and compliance. These features highlight the capabilities that distinguish Splunk Enterprise Platform from basic log management tools and show its practical value in enterprise environments.

Splunk Enterprise Platform has had some of the biggest positive impacts on our organization, including improvements in incident response time. Before using Splunk Enterprise Platform, analysts needed to manually search logs across multiple systems, but with Splunk Enterprise Platform, we can centralize logs with real-time alerts and dashboards which improved our incident response times to be 50 to 80% faster in many SOC environments. In terms of threat detection, before using Splunk Enterprise Platform, threats were detected after a significant delay, but Splunk Enterprise Platform helps us continuously monitor and correlate rules detecting attacks within minutes which impacts earlier containment and reduces business impact. In terms of efficiency, we used multiple tools and manual log collection before Splunk Enterprise Platform, but with Splunk Enterprise Platform we have a single platform we can use for searching, monitoring, and investigations, allowing us to investigate more incidents with less effort. For compliance and auditing metrics, before using Splunk Enterprise Platform we needed to manually collect evidence and compile auditing reports, but with Splunk Enterprise Platform we can automate reports for compliance frameworks which save hours of manual work and improve audit readiness. These are the key improvements we have seen with using Splunk Enterprise Platform.

While Splunk Enterprise Platform is widely regarded as a powerful SIEM  and observability platform, users across enterprises commonly report recurring challenges including licensing and data ingestion costs. Splunk Enterprise Platform's licensing is often based on the volume of data ingested, and as our organization grows, costs can increase significantly, and our teams may need to carefully decide which logs to ingest, which can limit visibility. A suggested improvement would be more flexible licensing options, better built-in recommendations for optimizing data ingestion, and smarter data compression or tiered pricing. There is also a steep learning curve where beginners can find SPL difficult. A suggested improvement would be more AI-assisted SPL generation, interactive tutorials, and guided dashboard creation with additional pre-built templates for common SOC use cases. These are the main areas for improvement that I can see: licensing flexibility, reducing the learning curve for new users, simplifying development, improving performance for very large datasets, and providing more AI-assisted features to reduce manual effort.

In terms of adding more improvements, there are frequently discussed areas including easier third-party integrations. While Splunk Enterprise Platform supports many integrations, onboarding new security tools sometimes requires custom configurations or add-ons. A suggested improvement would be more plug-and-play integrations, faster support for new vendors, and then simplified administration. Administrators often manage indexes, forwarders, user roles, and cluster health, so a suggested improvement would be easier administration dashboards and automated health checks. These are suggestions that acknowledge Splunk Enterprise Platform's strengths while highlighting areas where many enterprise users see opportunities for further improvement.

The primary areas for improvement that I see are licensing flexibility, simplifying administration, expanding plug-and-play integrations, and adding more AI-driven assistance for searches and investigations. These improvements would significantly simplify our tasks and help us solve more incidents in a lesser amount of time, making it flexible even for beginners.

I have been working for about 15 to 16 months in my current role, in the same project, in the same security domain only.

In my experience, Splunk Enterprise Platform has been a stable and reliable platform for day-to-day security monitoring and log analysis. It has consistently handled large volumes of data. The dashboards, searches, and alerting capabilities have performed reliably, though occasional issues such as slow searches or delays during peak data ingestion can occur. Overall, the platform has been dependable for security operations.

Splunk Enterprise Platform is highly scalable in my experience, efficiently handling increasing volumes of log data, users, and security events by scaling horizontally with additional indexers and search heads. As our environment grows, the platform continues to perform well with the right infrastructure configuration, but scaling requires proper planning for storage, compute resources, and licensing to maintain optimal performance.

I have not needed to contact Splunk Enterprise Platform support directly as the platform has been stable in our day-to-day operations. Most routine issues are handled internally by our team using Splunk Enterprise Platform's documentation and knowledge resources. Based on my current experience, I have not encountered major problems that required escalation to Splunk Enterprise Platform support.

Splunk Enterprise Platform delivers a measurable ROI by reducing manual effort, minimizing downtime, and improving security operations. When it comes to time saved, security analysts spend significantly less time searching logs and investigating incidents. In terms of employee productivity, the same SOC team can handle more alerts due to automation, dashboards, and correlation searches. Money saved includes faster incident detection and response, reducing the cost of security breaches, data outages, and compliance failures. For our enterprise, the key impact areas are generally time saved in investigations, higher analyst productivity, lowered costs of security incidents due to faster detection and response, and reduced manual reporting effort.

Regarding my experience with Splunk Enterprise Platform's pricing, it is a powerful but premium platform requiring deliberate optimization to manage high upfront costs, including high initial setup costs and then complex shifting licensing. While unit costs are high, the platform's ability to consolidate siloed tools into a single pane of glass provides immense value justifying the premium cost if the architecture is tightly managed.

I would recommend others to highly use Splunk Enterprise Platform because of its day-to-day usability, alert investigation capabilities, the time saved, and its highly accurate, scalable, and reliable support in day-to-day SOC operations. Splunk Enterprise Platform has greatly assisted in our day-to-day activities, and I would like to thank the Splunk Enterprise Platform team for providing us with a highly accurate and reliable platform that facilitates the maintenance of our day-to-day SOC operations. I would rate my overall experience with Splunk Enterprise Platform as a nine out of ten.

I mostly use Splunk Enterprise Platform  for monitoring and investigating alerts in the Infoblox environment.

When I receive an alert for excessive failed login attempts, I assign that alert to myself and start looking at the logs through drill-down searches where I check who the user is, what the failure reason is, and their event codes such as 4624 and 4625. I analyze those details.

Most of the time I monitor the environment and use the search capability of Splunk Enterprise Platform  for log analysis.

The best features for my use case are query changes and searches, through which we can detect multiple suspicious activities in the environment. There is risk-based alerting and Threat Intelligence Frameworks that Splunk Enterprise Platform provides, as well as MITRE ATT&CK mapping.

I mostly use the Threat Intelligence Frameworks, which match known malicious IOCs including IPs, URLs, domains, and file hashes while correlating the alert.

Risk-based alerting is also a strong feature that Splunk Enterprise Platform provides because it assigns a risk score to the particular user or system instead of triggering alerts on every suspicious event, which reduces alert fatigue.

I have worked on ArcSight in the past, but ArcSight has different components such as the logger and the ESM. Splunk Enterprise Platform provides everything in one single platform. We do not have to log in to two different environments repeatedly. It also provides a centralized log management system where we can put all logs for faster threat detection. This reduces the mean time to detect and respond to alerts in the environment. Additionally, we use the log management capacity of Splunk Enterprise Platform for compliance purposes including HIPAA and PCI DSS.

We mostly use Splunk Enterprise Platform scheduled correlation rules, which we run on a scheduled basis rather than in real-time, which reduces the load on the system. It also provides a good amount of time to respond to alerts. Analysts can investigate alerts faster using the single platform.

One area for improvement is the high licensing cost that Splunk charges.

I have been working in this field for 2.7 years.

Splunk Enterprise Platform is very stable.

I give it a rating of 10 because it is really scalable and provides great capability for scaling.

The customer service is really good. I received the solution within 24 hours.

I did not particularly switch from another solution, but I found my previous platform complicated. I was working on a project where we were using ArcSight, but it is more complicated because it has a different ESM tool and different logger. We have to access those in different environments and log in two times when accessing them. Splunk Enterprise Platform provides everything in one place.

Licensing relates to indexing the data that is ingested on a daily basis. The setup cost depends on the platform being acquired and the logs being ingested.

I would advise that Splunk Enterprise Platform is really user-friendly and provides many functionalities. It is also integrating AI, which is helpful. I give this review a rating of 9 out of 10.

My main use case for Splunk Enterprise Platform  is using it for security monitoring.

In security monitoring, we are using Splunk Enterprise Platform  for multiple log sources which come from different devices including Active Directory, VPN, Defender, and EDR. We are receiving these logs from these devices and onboarding them on Splunk Enterprise Platform. We have written many alerts, and we are getting those alerts on Splunk Enterprise Platform and performing analysis on that.

Regarding my main use case with Splunk Enterprise Platform, we have written numerous security alerts and monitoring rules according to the log source requirements. We have obtained different alerts from Azure  security, cloud security, and EDR, and we perform analysis on many alerts, closing them on Splunk Enterprise Platform after the analysis. We have integrated Splunk Enterprise Platform with ServiceNow , utilizing automation, and we use SOAR  Phantom  with Splunk ES. All these generate alerts and send them to Phantom , where we have written many playbooks to take actions based on those playbooks.

In my experience, the best feature of Splunk Enterprise Platform is its excellent data searching capability. Whenever we want to search long data or export heavy logs, we can easily export them from Splunk Enterprise Platform. Other tools do not offer this level of functionality; they have limited capabilities.

The searching feature in Splunk Enterprise Platform stands out because, for example, if I want to export multiple GB of logs, we can easily do so. In other tools, we do not have much functionality; they impose limitations on exporting large log sources. Splunk Enterprise Platform has a very good functionality called lookup, which allows us to add many elements into the lookup and expand it significantly, unlike other tools that have restrictions affecting formatting upon updates.

I find the visualization feature in Splunk Enterprise Platform to be very good, as well as reporting and dashboards, which we can customize based on SPL queries to see more detail in visualization. Additionally, the log ingestion and exporting capabilities are much better than other tools.

Splunk Enterprise Platform has positively impacted our organization by improving our security posture, and our team performs good analyses since there is no need to select any log source; we just input the necessary fields and obtain the details.

As for specific outcomes, we also achieve a good reduction in false positives because we can create lookups and assign permissions to our analysts based on requirements. We have many custom permissions we can add.

One area for improvement in Splunk Enterprise Platform is the issue we face when writing Regex; it would be beneficial to have a tool that can automatically generate Regex.

I have been using Splunk Enterprise Platform for eight years.

I find Splunk Enterprise Platform to be steady.

The scalability of Splunk Enterprise Platform is good.

Customer support is good. I rate customer support a 10.

We used a different solution previously, though those decisions were made by higher management rather than by me.

I find the pricing, setup cost, and licensing of Splunk Enterprise Platform to be fine based on our usage and integrations.

Before choosing Splunk Enterprise Platform, we evaluated QRadar and found that its licensing cost was higher than that of Splunk Enterprise Platform.

I rate Splunk Enterprise Platform a 10 based on my experience with multiple tools.

I choose to rate it 10 because Splunk Enterprise Platform helps ingest many logs, and we can perform extensive searches and large data exports easily.

Regarding Splunk Enterprise Platform's AI capabilities, I find its governance and capability to be good, with many apps available that we can integrate with Splunk ES to obtain results.

We can manage data sovereignty at a petabyte scale within our environment easily.

My experience in maintaining granular control over data using the trusted control plane within Splunk Enterprise Platform is good.

As my organization considers new use cases including Agentic AI, Splunk Enterprise Platform's governance and role-based access controls help us onboard Agentic AI logs on Splunk Enterprise Platform and write rules based on requirements.

My advice for others considering Splunk Enterprise Platform is that it works very well for handling long data and very large datasets. My overall rating for Splunk Enterprise Platform is 10.

My main use case for Splunk Enterprise Platform  is security monitoring and incident detection. I use Splunk Enterprise Platform  to collect and analyze logs from servers, endpoints, firewalls, and network devices. I monitor security events, investigate alerts, troubleshoot issues, and support incident response through dashboards and log search.

One example of how I have used Splunk Enterprise Platform for security monitoring and incident detection was when Splunk Enterprise Platform generated multiple failed login alerts for a privileged account from different IP addresses in a short period. I used SPL to review the authentication logs, correlating them with firewall and Windows Event Logs. I confirmed it was a password spraying attempt rather than normal user activity. I escalated the incident, the account was secured, and the source IPs were blocked.

In addition to security monitoring, I use Splunk Enterprise Platform for operational monitoring and troubleshooting. It helps me quickly search logs from Windows and Linux servers, network devices, and security tools to identify the root cause of issues. I have also used dashboards to monitor system health and create alerts for critical events, which improves response time and reduces manual log analysis.

The best features Splunk Enterprise Platform offers are its log analysis and its powerful log search capabilities using SPL. Centralized log collection, real-time monitoring, alerting, customizable dashboards, fast troubleshooting, and the ability to correlate events from multiple data sources are all valuable. It also scales well for large environments and integrates with many security and IT tools, making incident investigation much more efficient.

Splunk Enterprise Platform has improved visibility across the environment by centralizing logs from multiple systems. It has reduced the time needed to detect, investigate, and respond to security incidents, streamlined troubleshooting, and helped my team respond to issues more quickly. Overall, it has improved operational efficiency and reduced downtime.

One area for improvement for Splunk Enterprise Platform is the learning curve. Splunk Enterprise Platform and SPL can take time for new users to master. Licensing and data ingestion costs can also become expensive as log volumes grow. Additionally, simplifying the initial deployment and providing more out-of-the-box dashboards and use cases would help organizations get value more quickly.

I have been working for three or more years in my current field.

The feature I rely on the most day-to-day is SPL, Search Processing Language. It allows me to quickly search and filter large volumes of logs, investigate alerts, and troubleshoot issues instead of manually checking logs on multiple systems. I can correlate events from different sources in one place, identify root causes faster, and respond to incidents more efficiently.

One thing I particularly appreciate about the features is the flexibility of Splunk Enterprise Platform dashboards and alerts. They can be customized for different teams and prioritized, making it easier to monitor critical events without constantly searching through logs. That saves time and helps focus on the most important issues.

Although we have not measured exact KPIs, Splunk Enterprise Platform helped reduce the time required to investigate incidents. Instead of manually checking logs across multiple systems, we could quickly search centralized logs and identify the root cause much faster. For many incidents, the initial investigation time was reduced from around 30 to 45 minutes to approximately 10 to 15 minutes, which improved our overall response time.

Regarding Splunk Enterprise Platform's AI capabilities, from my experience, it provides strong governance and security through role-based access control, audit logging, encryption, and integration with enterprise identity providers. These features help ensure that access to data and AI-assisted capabilities is controlled and traceable. As AI capabilities continue to evolve, I would appreciate seeing even more transparency around AI-generated results and more granular governance controls.

From my experience, Splunk Enterprise Platform's AI-assisted capabilities are generally accurate and can help in prioritizing alerts, summarizing information, and speeding up the investigation. However, I do not treat the output as definitive. I always validate AI-generated insights against the underlying logs and other evidence before making a decision. Overall, I would describe the accuracy and reliability as good, but human verification is still important.

My advice for those looking into using Splunk Enterprise Platform is to clearly define your logging and security monitoring objectives before deployment. Start with your most critical data sources. Invest time in learning SPL and build dashboards and alerts that align with your operational needs. Additionally, plan your data ingestion carefully to manage licensing costs and get the best value from the platform. I rate this product a nine out of ten.