TrustRadius Insights for Splunk Observability Cloud are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
Splunk Infrastructure Monitoring, formerly known as SignalFx, has been widely used across organizations for continuous monitoring of cloud resources and application statuses. Users have relied on Splunk Infrastructure Monitoring to aggregate data from various areas and correlate them to pinpoint problem areas. Different applications within organizations have used Splunk to monitor core infrastructure, back-end app servers, front-end servers, databases, and other parts of the application. Splunk Infrastructure Monitoring has helped track hundreds of device endpoints, providing visibility into each device and the ability to customize the data received from them.
The monitoring capabilities of Splunk Infrastructure Monitoring have helped detect device problems and automatically remediate them in some cases. Users have determined custom logs to capture, noted their locations and hosts, and gathered sample log files for Splunk ingest. Splunk Infrastructure Monitoring has been used to monitor AWS infrastructure, troubleshoot issues, and provide visualizations of different data types. It has also been used to monitor Azure and on-prem resources, as well as application health. The product has served as the primary monitoring and alerting solution for infrastructure and application metrics, helping maintain uptime on systems and address business problems related to system monitoring.
Splunk Infrastructure Monitoring has delivered real-time monitoring and troubleshooting across various platforms, enabling instant visualization, alerts, insights, and troubleshooting steps. It has provided observability over a distributed higher education environment and helped build an infrastructure map for steering decisions. The product has been used for incident detection and prevention, monitoring logs, and saving logs for all necessary cases. Splunk Infrastructure Monitoring has been used as a primary monitoring tool in Cloud Infrastructure, managing dashboards and incidents. It has offered deep insights into system and network activities, monitored applications, and alerted when applications go down. The product has helped monitor service health, diagnose issues, and show data in a manner that exposes the desired information. It has been used to monitor infrastructure and services, set baselines, and analyze logs for trends, issues, improvements, and reporting.
Customers have found value in the proactive monitoring features of Splunk Infrastructure Monitoring, allowing them to take action based on metrics like CPU utilization and disk space. Reviewers have praised the product's ability to alert users about system issues and take proactive measures to maintain system uptime. Overall, Splunk Infrastructure Monitoring has proven instrumental in monitoring different environments, including production, UAT, development, Linux virtual machines, AWS infrastructure, Azure resources, on-prem resources, and application health. By providing real-time insights, visualizations, and alerts, Splunk Infrastructure Monitoring empowers organizations to make informed decisions and address business problems related to system monitoring effectively.
So we use Splunk Observability Cloud for APM, Traces, Logs and Monitoring of our cloud resources and our application performance. So the main problem it solves is troubleshooting our engineers spent a lot time in troubleshooting but after using this everything is easy and automated we got alert of incident and also with same alert we get link of traces and logs so for our engineers it saves a lot time.
Pros
Troubleshoot errors
Optimize application
Monitor cloud resources
Centralized Incident Alerting
Cons
Advance dashboards are bit learning curve for user
Advance monitoring need more add ons means more cost
They need to give more out of the box dashboards so even small team can start with
Likelihood to Recommend
So i think if your team is spending more time on troubleshooting, if your team struggling with performance issue and you dont even know what it is, if your product have so many microservices calling each other and if one call fails and you dont know which fails and you dig in to all microservices so in these scenarios Splunk Observability Cloud is the best tool to start with
We use it mainly to monitor infrastructure and application performance across multiple environments, but also as part of our broader security and compliance visibility stack. It helps us detect performance issues, and unusual activity before they turn into incidents. It helps with problem of fragmented monitoring and limited visibility across systems that have to meet regulatory requirement especially for HIPAA and PCI data . We use infrastructure monitoring, alerting, and real-time dashboards that support both IT operations and security response teams.
Pros
Realtime visibility across infrastrucrte and applicaitons
Excellent traceability of data to get us to root cause
Dashboard are very flexible and customizable.
Easy integrations with the rest of our tech stack
Cons
Unnecessarily complicated licensing
UI needs and update. It's overly cluttered and difficult to learn
Big correlations for logs and traces can be slow and time consuming.
Likelihood to Recommend
Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.
VU
Verified User
Director in Information Technology (1001-5000 employees)
I use Splunk Observability Cloud to monitor mainly my Cloud Infrastructure, FrontEnd and Backend applications. In our Organization, through the help of Splunk Observability Cloud multiple teams can easily troubleshoot their applications and infrastructures through the help of theri metrics and logs which helps us to reduce the MTTD and MTTR. It solves so many problems like End to End Visibility, Real time correlations to reduce MTTD etc.
Pros
The first one is its Kubernetes container monitoring.
I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.
Cons
It can improve its pricing models as per its competitors as I have it is a bit costly as compare to others.
It can improve on its OTEL based integration part as currently to integrate OTel based application we need a good knowledge of OTel SDKs.
Likelihood to Recommend
I hav eused it in different scenarios som eof them are The K8s environment monitoring. If you have 100+ microservices running on K8s cluster and you want to monitor each microservice calls trace and wants to trac eit completely then Splunk Observability Cloud is the best choice.
Real time incident detection and Root cause analysis . due to this feature you can easily reduce this mttd and mttr.
In our organization, Splunk Observability Cloud is a critical component of our end-to-end monitoring and observability strategy. We use it to gain deep visibility into the health, performance, and reliability of our cloud-native applications and infrastructure in real time.
Pros
Data security
Custom Dashboards & Alerts
Log Management
Cons
Having the AI within Splunk Observability Cloud and let the users use human language and retrieve the data from it without the knowledge of SQL Splunk queries.
Likelihood to Recommend
Splunk Observability Cloud is well-suited for increased uptime and reliability for critical business services.
Reduced noise from alert fatigue thanks to smarter alert routing and correlation. Our team shifted from reactive firefighting to proactive performance tuning.
In our organization, We're using Splunk Observability Cloud to augment our onprem Splunk infrastructure. Splunk Observability Cloud gives us telemetry into our hybrid infrastructure.
Pros
real-time monitoring
scalability
unified observability
Cons
I think there is room for improvement in Splunk Observability Cloud with cost optimiazation
I think there is room for improvement in Splunk Observability Cloud with complexity
I think there is room for improvement in Splunk Observability Cloud with customizations
Likelihood to Recommend
I think I am likely to recommend Splunk Observability Cloud to a colleague for Seamless integration across the data center and could using Splunk forwarders
VU
Verified User
Director in Information Technology (1001-5000 employees)
The leading scope for using Splunk is log parsing and proactive monitoring. Combining logs from multiple sources, discerning trends for display on dashboards, and acting on specific triggers (errors, etc.).
Pros
Querying over multiple sources.
There are a lot of ad hoc possibilities, including clearly structured query language.
Creating dashboards and shareable reports.
Cons
You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.
Likelihood to Recommend
The query language is relatively easy and flexible when looking into an application's problems. These queries can then be used for alerts, reports, and dashboards. I believe Splunk is a platform that can help a system grow into its proactive application management, using incidents to add insights as needed without trying to work out every scenario in advance.
VU
Verified User
Professional in Information Technology (1001-5000 employees)
We monitor our campus firewall , for auditing, troubleshooting, and changes with 3rd party vendors infra. We also collect logs from our servers and analyze it for trends, issues, improvements, as well as reporting.
Pros
Aggregate data in a simple way
Versatile search and correlation interfaces
fast
Cons
Finding the correct app for the use case can be tedious
natural language searches can be very helpful as well as results
integration of suggestions \ autocomplete
Likelihood to Recommend
Serve as a central data lake from a lot of different sources
correlation can be tricky.
VU
Verified User
Engineer in Information Technology (10,001+ employees)
1.
Determine what custom logs you wish to capture.
2.
Note and document the paths that the logs are located.
3.
Note and document the hosts that contain those logs (IP, short hostname,
FQDN)
4.
Gather sample log files
5.
Check for application guidance for Splunk ingest (i.e. iis
logs require a specific configuration so that logs are readable inside Splunk,
some application can utilize http event collector, etc.)
Pros
Logging
Log Forwarding
Monitoring
Cons
Improve search latency
Ability to export data using other apps
Ways to remove IP's when exporting data
Likelihood to Recommend
These scenarios walk you through monitoring, investigation, and detection scenarios for security incidents using Splunk Enterprise Security
I work as an admin to support Splunk users with their application onboarding, and consultancy to provide the best solution for their use cases. Splunk is a monitoring tool that helps the user to create alert dashboards based on their logs. Splunk helps the user monitor their application and search in their log for failure and error. Splunk SPL is very strong and powerful.
Pros
Monitoring
Alerts
Dashboard
Cons
Price
Onprem application onboarding.
Likelihood to Recommend
Splunk can perform very well if we want to monitor the application and create an alert/dashboard based on that. But if we go for the price, it is very costly Apm tools. There is no url monitoring on splunk, so we want to monitor the url we have to go to any other apm tool that can do this task.
Identify issues and deep dive when there is an issue. Also good to correlate the data between Splunk Core and Splunk 0lly. For the e2e view, it’s good to refer to the data sources onboarded and enable the correlation searches. Use Orel collectors to send metrics and traces, which could be populated to a dashboard.
Pros
Identify slowness.
Rca
Reduced MTTR.
Improve MTTI.
Cons
Documents.
Video
Custom metrics.
Likelihood to Recommend
Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.
VU
Verified User
Advisor in Information Technology (10,001+ employees)