Sold by: Splunk
Deployed on AWS
Splunk Observability Cloud is the only fully integrated, turn-key solution for DevOps teams to conquer the complexity caused by modern applications and infrastructure. It powers high performing applications to deliver world-class customer experiences by eliminating operational blindspots. You can quickly find, analyze and resolve incidents anywhere in your stack with all the answers in one place. Unlike other vendors, with Splunk Observability Cloud you only need to instrument once with OpenTelemetry to get unified metrics, traces and logs collected in real-time, without sampling for full-stack, end-to-end visibility. AI-driven pattern detection proactively identifies and alerts on issues in seconds, drastically lowering MTTR. One tightly integrated modern UI powered by the most advanced capabilities means reduced tool sprawl, centralized management, cost control, and one seamless and streamlined workflow for monitoring, troubleshooting, investigation and resolution.
4.2
Overview
Splunk Observability Cloud is the only fully integrated, turn-key solution of all the tools DevOps teams need to monitor any stack at any scale. One seamless UI provides end-to-end visibility, context rich workflows and lets you drill down to root cause in seconds.
Splunk Observability Cloud includes:
Infrastructure Monitoring - Splunk Cloud Infrastructure Monitoring provides DevOps, CloudOps, and SRE teams with real-time, full-stack visibility across all layers of their environment. With hundreds of out-of-the-box integrations, streaming analytics, pre-built dashboards, intelligent problem detection, programmability, and Service Bureau capabilities, Splunk Infrastructure Monitoring provides the fastest, most flexible visualization and accurate alerting for enterprise DevOps teams to meet or exceed Service Level Objectives (SLOs) by quickly detecting, triaging and resolving performance issues.
Synthetic Monitoring - Splunk Synthetic Monitoring helps teams proactively eliminate customer-facing issues and optimize web and API performance to deliver better digital experiences. Our solution goes beyond basic uptime monitoring and incorporates filmstrips and screen recordings of user experience, OOTB benchmarks and customizable performance metrics, and seamless connectivity to a suite of observability solutions to help teams quickly understand and prioritize performance defects wherever they originate, and collaborate to quickly resolve these issues to deliver digital experiences that delight customers.
APM (incl. Always On Profiling) - Splunk APM is the industry's most advanced Observability solution to troubleshoot issues and optimize performance for modern applications. It includes:
100% data capture: Never miss an issue or anomaly across in your code or traces with Full-Fidelity, NoSample data capture to ingest and contextualize all your telemetry data, and code profiling to identify performance bottlenecks Directed troubleshooting: easily identify, scope, and resolve issues with guided troubleshooting that automatically correlates and contextualizes system performance to find root cause faster OpenTelemetry standardization: engineering teams receive flexible instrumentation to build and measure data from new code in services, with no proprietary vendor lock in
Real User Monitoring - Splunk RUM connects ALL front-end traces with their backend tracing, providing unmatched visibility that enables DevOps teams to understand exactly how their backend services impact user experience, thereby simplifying troubleshooting and resource allocation. With streaming analytics, SREs and developers are alerted within seconds of any user issue, and powerful AI capabilities coupled with high cardinality analysis enable them to bring the issue to speedy resolution. OpenTelemtry-based instrumentation provides maximum flexibility and ensures customers are never locked in.
Log Observer Connect - Consolidate your tools by unifying the logs from Splunk Enterprise and Splunk Cloud, with our best-in-class metrics and traces. Log Observer Connect lets observability users explore the data you're already sending to your existing Splunk instances with Splunk Log Observer's intuitive no-code interface for faster troubleshooting, root-cause analysis and better cross-team collaboration.
Splunk Observability Cloud suite starts at $15 per host, per month, billed annually. Minimum host quantities pricing apply.
Highlights
- Full-stack, end-to-end visibility: with a tightly integrated modern UI and seamless, context- rich workflows for full stack monitoring, troubleshooting and investigation of the unknown unknowns. Splunk Splunk Observability Cloud lets you drill down to root cause in seconds. You can easily integrate your existing monitoring tools to bring full context to alerts behind every incident.
- NoSample™ full fidelity tracing: no more dead end investigations using a NoSample™ full fidelity approach to capture and visualize all data, in context, making sure no anomalies get missed. Find the backend root cause of any front-end issue. When troubleshooting backend issues, full fidelity tracing helps finding any issue, even those that do not result in system errors, and issues that no one anticipated.
- Monitor any stack at any scale: Great for on-prem, hybrid and multicloud environments. Splunk Observability Cloud is a future-proof observability investment with a solution that will scale with customers and can meet the needs of any cloud-native environment, no matter how large (up to petabytes of ingest per day) or how complex (multiple cloud environments all integrated into one system of record), without compromising performance.
Details
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/12 months |
|---|---|---|
OBSCloud: Infrastructure | Real-time visibility for infrastructure health. 200 hosts included | $36,000.00 |
OBSCloud: App & Infra | All the data you need to adopt microservices. 100 hosts included | $72,000.00 |
OBSCloud: End-to-End | Troubleshoot O11y with ease to create the best UX. 100 hosts included | $90,000.00 |
Vendor refund policy
All purchases are final, no returns or refunds.
Custom pricing options
Request a private offer to receive a custom quote.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Splunk offers a variety of support options to help ensure your success. support@splunk.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
Top
10
In Data Anonymization, Data Security and Governance
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Telemetry Collection
Unified metrics, traces, and logs collection using OpenTelemetry with real-time data ingestion without sampling
Performance Monitoring
Full-stack visibility across infrastructure layers with streaming analytics, pre-built dashboards, and intelligent problem detection
Application Performance Management
Full-fidelity data capture with 100% trace ingestion and code profiling to identify performance bottlenecks
Troubleshooting Capabilities
AI-driven pattern detection and directed troubleshooting with automatic correlation of system performance data
User Experience Monitoring
Front-end and back-end trace connection with streaming analytics and high cardinality analysis for comprehensive performance insights
Data Collection and Indexing
Real-time collection and indexing of machine-generated data from diverse sources and locations
Event Correlation
Advanced correlation capabilities including time-based, transaction-based, sub-searches, lookups, and joins across multiple data sources
Scalability
Capability to collect and index tens of terabytes of data per day with distributed computing architecture
High Availability
Clustering technology ensuring continuous data availability and system reliability during scale-out operations
Machine Data Analysis
Comprehensive platform for searching, analyzing, and visualizing massive streams of machine data from physical, virtual, and cloud infrastructures
Data Processing Engine
"Vendor-neutral processing engine for centralized parsing and processing of event data from multiple sources"
Data Routing Capabilities
"Ability to route, optimize, reformat, enrich, and structure data for different destinations in real-time"
Authentication Mechanism
"Supports external authentication through LDAP, Splunk, and OpenID Connect identity providers"
Worker Infrastructure
"Configurable worker groups, worker processes, and edge nodes with scalable deployment options"
Data Optimization
"Advanced data stream reduction capability, capable of trimming up to 50% of unused log and metric data"
Standard contract
No
No
Customer reviews
reviewer2787105
Log insights have boosted uptime and now drive automated remediation and pattern-based alerts
Reviewed on Dec 17, 2025
Review provided by PeerSpot
What is our primary use case?
I am using Splunk Observability Cloud as a log-based monitoring tool for my databases. We have ingested our database logs and OS system logs into Splunk Observability Cloud and are creating dashboards and alerting features over those alerts. One of my major use cases is that all kinds of databases I am currently working with have database logs that capture all information, warnings, and error messages. These database logs are moving to Splunk Observability Cloud. The first use case is that I no longer need to maintain a long list of flat files on my server for all those logs. Those can be directly ingested into Splunk Observability Cloud. The benefit I am seeing from here is that I can get pattern-based analysis of what kind of errors I am commonly getting and what the date patterns of those errors are. I can get dashboards over that and I can also create alerts. I can also incorporate those alerts with some back-end Git workflow for automatic remediation. This is one of the solutions.
Another use case for Splunk Observability Cloud that we are seeing is that there are multiple times when there is a requirement to publish some kind of data. So instead of publishing an alert if those data breaches occur or if some kind of dashboard needs to be created, instead of sending data directly to the users, if that data is not PII, we are also ingesting that into Splunk Observability Cloud in a JSON format and then again, dashboards and other alerting can be created. These two are the main major use cases for which I am using Splunk Observability Cloud.
How has it helped my organization?
With the help of the alerting and observability mechanism, resiliency, and automatic automation of issue remediation based on alerts and workflows, it actually reduces the cost and increases the uptime of my system and customer satisfaction. There are multiple indirect benefits I am getting when using Splunk Observability Cloud.
Currently, with the growth of the organization, I am seeing an increasing use of Splunk Observability Cloud in a more dynamic way. We are continuously creating new dashboards, ingesting logs in JSON, and trying to bring the best value out of it. I am seeing a dynamic and drastic increase in the use of Splunk logs and the Splunk data we are ingesting.
There are two aspects to expanding the usage. Organic growth of the environment actually puts new systems into Splunk Observability Cloud, and exploring new opportunities for what all can also be ingested into Splunk Observability Cloud. Previously, I can see that memory dumps are there. We are also looking at whether we can ingest memory dumps so that if the system is about to crash, those memory dumps can be captured into Splunk Observability Cloud so that it can create alerts over that and I can also perform analysis. I can also see if any other system is facing the same kind of memory dump issues. So that maybe it is one alert for one system for me, but for the complete farm, there may be different servers with different teams or business units facing the same issues. When I have Splunk Observability Cloud on all systems, I can actually create a consolidated report and see that this is the pattern which particular farms are having this kind of issues, and maybe something is broken. This is the way the plan is to increase the availability or the usage of Splunk Observability Cloud.
What is most valuable?
The performance and speed are valuable. Previously when Splunk offered the enterprise solution, I needed to install Splunk and maintain my local server. There was a limitation that only a certain number of servers could be supported in one instance and I would need to have multiple instances if I was in an enterprise system setup. When I am in the cloud, a single instance can support N number of systems. It is pretty fast, no matter how much data is there. Dashboards are pretty good with multiple functions available. The alignment or integration that can trigger automatic solutions with the workflow for automatic remediation of the alerts is the best thing. These three or four things are the best Splunk Observability Cloud features that I am seeing.
The point in time alerting, the point in time data capture, and automatic remediation with the integration of good workflows or Ansible workflows is definitely the key to any resiliency and increasing the uptime of any system.
After moving to Splunk Observability Cloud, it is almost zero downtime. We never face downtime because when I was in the enterprise setup, I needed to maintain my servers and maintain hygiene of vulnerabilities, patches, and all. Now when I am in the cloud, everything is automatic. Almost zero downtime plus the perfect alerting feature and log-based analysis are available. Metrics alerting is also there in Splunk Observability Cloud through queries. This is one of the features that keeps me updated with the current health of my system and helps me to keep my system up and running fine and available for my customers.
Splunk Observability Cloud incorporated a new AI agent feature that is really good. Sometimes I need to create queries and Splunk queries for filtering the data and some pattern-based analysis. This agent is really good in helping me and suggesting the queries. This means I do not need to have a Splunk expert or Splunk query expert. I can just ask that agent that I need pattern-based analysis or I need to create this kind of filters for this kind of data and it can suggest to me. Once it suggests a sample query to me, I can do the tweaking and I can have my data ready. It actually reduces my time to perform my analysis and to reach the conclusion about what exactly is causing issues in my system and what are the repetitive issues in my system. This AI feature really helps for newcomers to Splunk Observability Cloud to perform deep diving analysis with the data captured by it.
Custom metrics are valuable. In Splunk Observability Cloud, some infra-level metrics are not available, but through custom metrics, I can achieve it. This is an add-on feature that Splunk Observability Cloud is providing and without any additional monitoring tool. If that feature was not there, then I would need to plan some other monitoring tool for metrics-based alerting, but this custom one helps me to achieve it in the same monitoring tool. The consolidation and integration of metrics-based alerting and log-based alerting in a single tool is actually the lovable feature. I do not need to worry about or look for multiple tools. I can have my own data and own health available in a single tool, in a single view.
What needs improvement?
The dashboards are good, but the only limitation I see currently is that they need particular formats only to create a dashboard. They need to have a particular JSON format or time series format. This sometimes creates additional work for me so that when I am ingesting logs in Splunk Observability Cloud, it should be in a specific format. Either Splunk Observability Cloud should have multiple formats available or multiple dashboards available for different kinds of formats. At least Splunk Observability Cloud has everything available at a Splunk level. They can do some kind of analysis and see what are the major top ten or top twenty types of logs they are getting and they can have dashboards according to those logs. Instead of forcing customers to design their logs in the way of Splunk Observability Cloud, Splunk Observability Cloud can create dashboards based on the customer requirement. This will actually ease things up for the end users.
The current dashboards are good. The feedback is that Splunk Observability Cloud is forcing me to modify my logs that I am ingesting in Splunk Observability Cloud in a specific format. If Splunk Observability Cloud can leverage it and make it open for any format, that would be great. If that is not feasible, at least the top ten or top twenty logs that Splunk Observability Cloud is getting should be readable by Splunk Observability Cloud without any changes. That actually is one of the major feedback items I can provide which can actually ease the life of the end users or any layman. As a newcomer to Splunk Observability Cloud, I may not know JSON. I now need to hire someone or I need to look for someone who knows JSON and who can convert my logs into JSON format and then I will ingest them into the logs if I want to create a dashboard. If I do not want to create a dashboard, that is okay. On the other hand, Splunk Observability Cloud is giving me a usability and easy to go interface, but for a dashboard, I need to have an understanding of JSON so that I can ingest the log in JSON format. That is a dilemma that they have and they should work on.
Currently, Splunk Observability Cloud is not the only solution which any organization is using. There is also Grafana and PagerDuty. If Splunk Observability Cloud can plan some kind of integration with PagerDuty and Grafana , then those things can be controlled from a single position and if something else is happening at one location, it can update things at all levels. That can also bring great value to the users. Currently, I have to maintain three systems separately, but if some kind of integrations can be developed with these three vendors, then that can be a great thing because all these three have now become the industry pillars or industry standards for observability and resiliency.
For how long have I used the solution?
I have been working with it for the last two years. Before that, it was an enterprise solution. Now it is cloud-based.
What do I think about the stability of the solution?
I cannot relate any stability issues to my experience with Splunk Observability Cloud.
What do I think about the scalability of the solution?
Scalability is pretty smooth. I just need to deploy the Splunk forwarder and the config file that specifies which servers it should connect to and it will get connected. My data will start populating. It is pretty straightforward. I do not see any challenges there, even when it was in enterprise and now when it is in the cloud. The deployment and onboarding of new servers and ingesting the logs is pretty straightforward. Anybody can learn it within a day without having any prior knowledge.
How are customer service and support?
We have raised multiple questions when we face any issues. Our support is prompt and usually within a day, I will get my answers.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously I was on Splunk Enterprise. I have been using Splunk for seven to eight years before we moved to the cloud in the last eighteen months.
How was the initial setup?
The initial setup is pretty smooth. I just need to deploy the Splunk forwarder and the config file that specifies which servers it should connect to and it will get connected. My data will start populating. It is pretty straightforward. I do not see any challenges there, even when it was in enterprise and now when it is in the cloud. The deployment and onboarding of new servers and ingesting the logs is pretty straightforward. Anybody can learn it within a day without having any prior knowledge.
What other advice do I have?
I appreciate that your organization collects reviews about the product so that it can be shared with the vendor or the product owner as appreciation or as feedback for improvement. Everything has been smooth in my experience. I would rate this product a ten out of ten.
MihaiHristache
Monitoring has improved operational visibility and supports fast, customizable alert dashboards
Reviewed on Dec 17, 2025
Review from a verified AWS customer
What is our primary use case?
I work for a managed service provider, so I have different clients that require help in assessing various tools. I work with Splunk, ScienceLogic , and Nagios most frequently because I have small clients as well.
We have Splunk Observability Cloud for some customers. The dashboards are good, and everything is nice, but unfortunately, it doesn't have long-term storage of the logs. So you need to use a data lake to store the logs.
I would like to see agentless deployment and better integration with ticketing systems like ServiceNow , which is the biggest.
We utilize the ability to enrich data with custom metrics in Splunk Observability Cloud to create tickets in ServiceNow . It is integrated with ServiceNow, but we enrich the tickets by putting the logs in the tickets and things of that nature, so it helps us. However, even that is a mixed approach. From Splunk Observability Cloud, you cannot put the logs directly in the tickets. Instead, it will create a ticket and send you an email with the logs. That integration could be improved.
What is most valuable?
Splunk Observability Cloud has helped me improve my operational performance and my customer's operational performance because we use alerting, so we find when things are not working.
I think it is very good for evaluating the effectiveness of Splunk Observability Cloud in improving digital resilience within my customer's environment.
It does provide some return on investment. It is beneficial in terms of finance to use it.
The dashboards in Splunk Observability Cloud are amazing. If you configure them correctly, they are amazing, and it is quite fast as well.
That is a very good feature of Splunk Observability Cloud because it helps us and it gives more trust in the alerts.
What needs improvement?
There are not complexities with the installation of Splunk Observability Cloud, but with the configuration of alerts and everything because Splunk has its own language in the background. You need to know Splunk in order to configure everything that you want.
It requires some in-depth knowledge of the product. It should be more plug-and-play, similar to ScienceLogic . ScienceLogic uses whatever it finds. You can use PowerShell, you can use scripts that you make. Splunk is more on the old style. It uses agents, and you have to deploy the agents.
The out-of-the-box customizable dashboards provided by Splunk are okay, but usually, I have to create new dashboards because every user wants to see something else. The out-of-the-box dashboards help to get started faster, but in the end, I will have to redo them.
I would like to see agentless deployment and better integration with ticketing systems such as ServiceNow, which is the biggest.
We utilize the ability to enrich data with custom metrics in Splunk Observability Cloud to create tickets in ServiceNow. It is integrated with ServiceNow, but we enrich the tickets by putting the logs in the tickets and things of that nature, so it helps us. However, even that is a mixed approach. From Splunk Observability Cloud, you cannot put the logs directly in the tickets. Instead, it will create a ticket and send you an email with the logs. That integration could be improved.
For how long have I used the solution?
I have been working with Splunk Observability Cloud for about two years.
What do I think about the stability of the solution?
I cannot speak to lowering the cost of unplanned digital downtime using Splunk Observability Cloud because the client will get the bills. However, it reduces the downtime for systems. It improved visibility when you do changes and you do patching and you do emergency changes, so you can see if they were applied correctly or not, if the servers are still down.
What do I think about the scalability of the solution?
If it is a new deployment and you have a medium client with about 2,000 users or computers or servers, it will take about six months just to install and configure.
How are customer service and support?
The technical support is very good with Splunk.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I worked with ScienceLogic before actually working with Splunk.
How was the initial setup?
There are not complexities with the installation of Splunk Observability Cloud, but with the configuration of alerts and everything because Splunk has its own language in the background. You need to know Splunk in order to configure everything that you want.
What about the implementation team?
I do not spend any time personally because I have a team that does it. I have 27 people in my team.
What was our ROI?
It does provide some return on investment. It is beneficial in terms of finance to use it.
What's my experience with pricing, setup cost, and licensing?
I think the pricing for Splunk Observability Cloud is still at a good price. If you are looking at Dynatrace , it is way higher.
Which other solutions did I evaluate?
I am familiar with the Dynatrace operator but I am not actually working with them. I am just looking into differences and tooling and what will benefit my clients better.
What other advice do I have?
You need to know Splunk in order to configure everything that you want.
The out-of-the-box customizable dashboards provided by Splunk are okay, but usually, I have to create new dashboards because every user wants to see something else. The out-of-the-box dashboards help to get started faster, but in the end, I will have to redo them.
We utilize the ability to enrich data with custom metrics in Splunk Observability Cloud to create tickets in ServiceNow. It is integrated with ServiceNow, but we enrich the tickets by putting the logs in the tickets and things of that nature, so it helps us. However, even that is a mixed approach. From Splunk Observability Cloud, you cannot put the logs directly in the tickets. Instead, it will create a ticket and send you an email with the logs. That integration could be improved.
I would rate this product an 8 overall.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Abhimanyu S.
Splunk Observability Cloud - A good product in "making"
Reviewed on Oct 01, 2025
Review provided by G2
What do you like best about the product?
Splunk observability cloud often referred as O11y, is a good product in terms of metrics observability and the part that I really liked about it is the integration with Splunk Cloud for logging needs so all in all, each and every key performance indicators about the application metrics-logs are visible under single plane.
What do you dislike about the product?
Splunk O11y Cloud seriously lacks in terms of graph and query customization, the visual customization are very limited which hinders in creating a dashboard with exactly what a user/consumer needs.
What problems is the product solving and how is that benefiting you?
It is way ahead from it competitors in terms of handling huge amount of data and providing it to the end user. The main issue any observability instrument faces is the storage and fetching of huge data in reasonable amount of time. Given Splunk's expertise, atleast the metrics/logs fetching for long data intervals is comparatively faster than any other platform in the market currently.
MoatazElsayed
Improves network visibility through real-time telemetry but pricing continues to be a challenge
Reviewed on Sep 23, 2025
Review provided by PeerSpot
What is our primary use case?
The main use case with Splunk Observability Cloud is to capture the logs from the SD-WAN in order to check the health of the network and the flow of data from different sources to the central place.
What is most valuable?
The best feature of this product is the latency and processing of all the telemetry that is being received, which gives full visibility at the right time.
One cannot protect and operate what they don't know. When there is this observability, it helps to see exactly what is present, the problems that may exist, and hence, it increases digital resilience by having proactive actions ahead, which increases the availability of the service.
The teams have utilized the ability to enrich data with custom metrics, as this enrichment is one of the key aspects used to have a clear understanding of which assets are being attacked, enabling necessary actions to be taken. The data has been enriched by adding customized information from customers' databases from different sources.
What needs improvement?
The pricing would be one area for improvement.
For how long have I used the solution?
I have used the SIEM solution since 2019 and have had experience with Splunk Observability Cloud for the last year.
How are customer service and support?
I would rate their customer service and technical support an eight out of ten.
How would you rate customer service and support?
Positive
What about the implementation team?
I work for SI, and we deliver to different organizations based on their requirements. We are responsible for implementation, so we implement and they see the value out of it.
What was our ROI?
Splunk Observability Cloud has improved the operational performance of our clients.
What's my experience with pricing, setup cost, and licensing?
It is expensive.
What other advice do I have?
The AI component is one of their strengths; currently, most competitors are moving in the same direction. As SI professionals, we are seeing different improvements in the AI domain for different products, and they are at the leading edge with many vendors following them.
My overall rating for Splunk Observability Cloud would be a seven out of ten.
Aleem Cummins
Synthetic monitoring increases availability and reduces downtime
Reviewed on Sep 10, 2025
Review from a verified AWS customer
What is our primary use case?
My main use cases for Splunk Observability Cloud include retail analytics.
What is most valuable?
The feature I appreciate the most about Splunk Observability Cloud is Synthetic Monitoring. These features have benefited my organization by increasing availability and decreasing downtime, providing assurance that makes you feel good, and ultimately enhancing well-being.
The out-of-the-box customizable dashboards are very effective. At the same time, we also use Splunk Cloud to enhance them. The Splunk Cloud is a better dashboarding experience.
Our teams have utilized the ability to enrich data with custom metrics in Splunk Observability Cloud. We've been doing a lot of that with event management and linking that into IT as well. So we're using that to be able to tie systems together. The integration we have between Observability Cloud and ITSI for event management is where we're using that type of stuff.
What needs improvement?
Splunk Observability Cloud could be improved by having more integration with Splunk Cloud because at the moment they're two separate products. They're making great moves on what they call unified access; tighter integration is always a good thing.
For how long have I used the solution?
I have been using Splunk Observability Cloud for three years.
What do I think about the stability of the solution?
I would assess the stability and reliability of Splunk Observability Cloud as generally good. We have experienced the odd bug; however, nothing too serious, and Splunk has been quite good in terms of resolving issues; it's just routine stuff and nothing bad.
What do I think about the scalability of the solution?
Splunk Observability Cloud scales incredibly with the growing needs of my organization. It just means the more we use it, the more expensive it is, but there are no issues reported.
How are customer service and support?
I would evaluate customer service and technical support as fantastic; nobody is better.
How would you rate customer service and support?
Positive
How was the initial setup?
During the deployment, we only had some challenges when we switched on unified access. However, they were just teething problems.
What was our ROI?
I have seen a return on investment with Splunk Observability Cloud as we have averted some things that may otherwise have resulted in downtime. We have had it avert potential problems, and the first time it happens is a return on investment. The second time, nobody notices, making measuring business value a challenge.
What other advice do I have?
I would advise other organizations considering this solution to give careful attention to the use cases they have and how they plan to proceed in terms of their roadmap over the next two to three years, as there are alternatives. Having an idea of where you want to go will help you make a better-informed decision.
Additionally, it's good advice to have a customer reference call to learn from someone's experience and avoid pitfalls.
On a scale of one to ten, I would rate Splunk Observability Cloud overall as a good eight; as soon as it's all integrated neatly together, then it's up in the high numbers.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)