Splunk Observability Cloud Reviews

My main use cases for Splunk Observability Cloud include Application Performance Monitoring, synthetic monitoring, and dabbling in infrastructure and what comes along with it; however, we do already have a tool that does infrastructure. We're debating about just switching it all over to Observability.

The features of Splunk Observability Cloud that I prefer the most are its all-encompassing licensing model, which is comparatively better than others in the market. We're switching off AppDynamics, and the licensing model always constrained us, so that is our main reason for switching to observability, as the licensing is all-encompassing.

The benefits of these features for my organization are significant. The license is all in one, meaning infrastructure, APM, synthetics, RUM, and the logs are all under one license, allowing us to offer that to our application teams more so than we were ever able to do before. 

We're currently trying to implement RUM, Real User Monitoring, with two applications just to get a feel for it, which we were never able to do before, since it was a completely separate license that we needed to purchase. So we're able to offer more of a full suite, more of a one-stop shop sort of thing, versus what we were able to do before.

The user interface of Splunk Observability Cloud needs a lot of work. I have been known to describe it as slapping lipstick on a pig. The pretty colors draw in everybody, however, the actual functionality of it has a lot that you cannot do, and how the user interface is organized is very difficult to navigate. This is a driving factor for us not to use the product.

The next release of Splunk Observability Cloud should include a feature that makes it so that when looking at charts and dashboards, and also looking at one environment regardless of the product feature that you're in, APM, infrastructure, RUM, the environment that is chosen in the first location when you sign into Splunk Observability Cloud needs to stay persistent all the way through. There's no reason that a user should have to keep having to restart all of their filters and select their environment anytime that they switch to a different area of the tool.

I have been using Splunk Observability Cloud for one year exactly.

I have not experienced downtime, crashes, or performance issues with Splunk Observability Cloud yet.

Splunk Observability Cloud scales with the growing needs of my organization, however, we very quickly always run into hitting the limit for custom metrics. This is something we've discovered that we have to manually manage, which is not fun, especially for large applications such as our huge tracking system, since we're a logistics company, as well as the two main revenue-generating applications. We are probably going to hold off putting them into Splunk Observability as we're constantly bumping the limit already.

I would evaluate customer service and technical support as hit or miss as I get the impression that the support folks assigned to our account might be spread a little too thin. They are good people and do good work; however, I get the impression they're spread a little too thin. If we put in a ticket, we do get a response in a decent amount of time, so that's not a problem.

Prior to adopting Splunk Observability Cloud, I used several solutions. The solutions we used include Zabbix, Splunk Core, Grafana, Prometheus, and AppDynamics, so a whole suite of things.

The deployment has been fine for cloud applications. It is very tumultuous for on-prem. That is supposed to be getting fixed over the next year. Right now, it's not there. So I always tell my management we're a year and a half too early for this tool.

I have seen ROI for our cloud applications, as we've been able to fully integrate with one application, which is a big revenue producer for the post office, and it's something that they were not able to do before, so we have been able to see that. In terms of ROI, I would say 100%.

We don't currently use the out-of-the-box customizable dashboards provided by Splunk Observability Cloud to showcase IT performance to business leaders. 

I will say we have not expanded usage to other applications since we're still stuck where we are. 

My advice to other organizations considering Splunk Observability Cloud is to wait until next year. 

On a scale of one to ten, I would rate this solution five or six.

My main use case for Splunk Observability Cloud is application monitoring.

The features of Splunk Observability Cloud that I appreciate the most are ops intel and the community support. These features have benefited my organization because they help us find the root cause of any issue quickly and pinpoint the exact location where the issue exists.

We have not yet completely gone into production, so I do not have any metrics or data points to share. To evaluate the effectiveness of Splunk Observability Cloud in improving digital resilience within my organization, we have various client applications, such as the teller application and our online banking applications. 

Initially, before Splunk, we had a long time to resolve issues. Now, with Splunk Observability Cloud, we will be able to solve them quickly and know exactly where the issue is. Previously, we needed to go to the war room to find where the issue was. Now, with Splunk Observability Cloud and all its agents and data, we know exactly where the issue is located.

Regarding the no-sample tracing feature, all the data fed by the agents to Splunk Observability Cloud means we do not have to worry about missing any issues during sampling. We have not yet explored the AI-powered analytics feature, but we have partially explored MLTK.

My teams have utilized the ability to enrich data with custom metrics by writing custom agents in Java and Python to collect those custom metrics and feed them into Splunk Observability Cloud. This is particularly useful for applications without direct Splunk agents.

The out-of-the-box customizable dashboards are helpful in showcasing IT performance to business leaders. They provide guidance on requirements we may not have visualized and help us build custom dashboards to include our company-specific metrics. We have not yet expanded usage since we haven't started using it extensively.

To improve Splunk Observability Cloud, we need more applications to be included in the observability so that more applications can have agents to monitor them and bring that information to the cloud. 

Splunk Observability Cloud has not yet completely improved our operational performance for our company's resilience as we are just starting out, however, it will help us ultimately to reduce incident time.

I have been using Splunk Observability Cloud for one year now.

In my experience until now, I have not experienced any stability issues with Splunk Observability Cloud.

Splunk Observability Cloud scales effectively with the growing needs of my organization. As we are a growing company transitioning all our applications to the cloud, and with the increasing number of cloud-native applications, Splunk Observability Cloud will help us achieve digital resiliency and reduce our mean time to resolution.

I would evaluate customer service and technical support as excellent, as Splunk has been quite responsive to our service requests, with their team providing good support.

Positive

Prior to adopting Splunk Observability Cloud, we were using Splunk Enterprise, and we had custom monitoring tools developed in-house.

The installation of Splunk Observability Cloud worked smoothly once we figured out the initial issues. The agents do not consume many resources, and the type of metrics they collect is helpful.

Since we have not progressed far into the implementation of Splunk Observability Cloud, I cannot comment on the return on investment at this time.

I am not involved in the experience with pricing, setup cost, and licensing.

I rate Splunk Observability Cloud eight out of ten.

My main use case for Splunk Observability Cloud is end-to-end tracing of business processes.

Splunk Observability Cloud has helped improve my operational performance and my company's resilience.

What I appreciate most about Splunk Observability Cloud is the correlation feature, specifically the ease of correlating logs and issues to those traces to see where within the path of the business function is failing. 

One significant way these features benefit my organization is through mean time to resolution. Taking away that first instinct of where we're trying to figure out what's wrong will drop that time significantly, so rather than a few hours, potentially we're looking at a few minutes before we can start resolving an issue.

In terms of operation performance and resilience, I have experienced improvements in mean time to resolution and the ability to detect issues that we weren't detecting ahead of time. I can give a specific case scenario; while we were in a POC situation, it was able to find issues we were having with servers just by random chance. We implemented it and it happened to let us know about an issue before our NOC even knew that it was occurring.

My teams have utilized the ability to enrich data with custom metrics in Splunk Observability Cloud during the implementation process, and we're definitely seeing a huge difference in what data we have, and the teams are extremely excited by the new amount of data we're getting in. I find the out-of-the-box customizable dashboards provided by Splunk Observability Cloud extremely beneficial since they give you a lot of information already, and the ability to customize and do your own is even better.

I ran into a small security incident. Splunk Observability Cloud was able to help us with that along with Splunk's core process or core offering. Between the two, we were able to use it for correlations, which helped with mean time to resolution and getting us back up and running much faster.

Splunk Observability Cloud could be improved with better integration with AppDynamics, as we know that's coming, however, it is an issue we've had between the OpenTelemetry and the AppDynamics collector. We saw a complete difference in what data was being brought in, however, we know that issue is being resolved and that's a big one for us.

I would assess the stability and reliability of Splunk Observability Cloud as okay. We've been experiencing an issue with the cloud console, and we're working with support to get through that. We're assuming it's just a growing pain at this point. Particularly what we're having is disconnection from the cloud console, where we will be working in it and receive a message saying that we've been disconnected and have to wait for it to come up. It's been painful and seems to be a new issue, and they're trying to figure out what's going on,however, I haven't heard of anybody else having that issue.

Splunk Observability Cloud seems to be scaling quite well with the growing needs of my organization.

I would evaluate the customer service and technical support for Splunk Observability Cloud as fantastic. On a scale of 1 to 10, the customer service and technical support deserve a 10.

Positive

I have seen a return on investment with Splunk Observability Cloud.

I would advise other organizations considering Splunk Observability Cloud to definitely POC it to see if it's going to work for their situation. It may not be for everybody. That said, definitely give it a chance and see what it can do for you and the kinds of new information it can bring in for you.

On a scale of one to ten, I rate Splunk Observability Cloud nine.

My main use cases for Splunk Observability Cloud include retail analytics.

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.

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.

I have been using Splunk Observability Cloud for three years.

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.

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.

I would evaluate customer service and technical support as fantastic; nobody is better.

Positive

During the deployment, we only had some challenges when we switched on unified access. However, they were just teething problems.

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.

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.

I use Splunk Observability Cloud for network logging analysis.

I prefer the dashboard building and search features of Splunk Observability Cloud the most. Splunk Observability Cloud has helped improve my operational performance. 

Previously, we used Elastic for similar purposes as Splunk Observability Cloud, and this has allowed us much more visibility into what we're working on with usable dashboards and metrics, which has been awesome.

The only strain point we've encountered with Splunk Observability Cloud is that the search times can be lengthy for some things. We have a large environment, so that's expected. That's the only complaint I've had so far.

I have been using Splunk Observability Cloud for approximately three months.

I experience slow searches occasionally with Splunk Observability Cloud, but there are no outages or anything in that regard, so it is pretty stable and reliable.

Splunk Observability Cloud scales with the growing needs of my organization effectively. As a large organization, we find it impressive that our volume has been handled with only occasional slow searches.

I haven't worked with customer service and technical support directly, however, another engineer on the team has shared positive feedback about their experiences.

Positive

Prior to adopting Splunk Observability Cloud, I was using Elastic. Support was a significant factor that led to switching to Splunk Observability Cloud. The previous solution wasn't fully supported by their team, and there weren't adequate integrations or visibility needed for some of our applications. Additionally, it was a legacy installation set up by former employees, so this was an opportunity to start fresh with people who are actively involved.

We haven't had Splunk Observability Cloud long enough for me to make substantial comments on its effectiveness in improving digital resilience within my organization.

I wasn't involved in the licensing. 

We haven't used the no-sample tracing feature in Splunk Observability Cloud specifically for eliminating blind spots in data collection. We haven't implemented the AI-powered analytics and guidance features provided by Splunk Observability Cloud either.

Our main security architect has done extensive work utilizing the ability to enrich data with custom metrics in Splunk Observability Cloud by setting up specialized dashboards and searches for our various integrated apps, including ISE and Palo firewall logging.

I haven't extensively used the out-of-the-box customizable dashboards provided by Splunk Observability Cloud as we're still using our custom ones. I wasn't involved in the pricing, setup, cost, and licensing. I enjoy using Splunk Observability Cloud, but I'm not familiar with the cost aspects.

Access to Splunk Observability Cloud has been reliable for all users. On a scale of one to ten, I rate Splunk Observability Cloud an eight. 

I recommend spending time working on your own dashboards and searches to fit your business needs, as that's where you'll get the most value out of Splunk Observability Cloud.

We are using the Splunk Observability Cloud for monitoring purposes and troubleshooting, and we are using that infrastructure in real time, in which we have infrastructure monitoring, application monitoring, log observer, and RUM synthetic monitoring. For troubleshooting purposes, we are installing the open telemetry collector agent on some of the servers, including Intel, Windows, and UNIX servers. 

I have also worked on the agent upgrade from version 0.103 to 0.1113, which is ongoing right now.

We are also using the dashboards and detectors in Splunk Observability Cloud. For client needs, we are creating dashboards, reports, and detectors as well. For the detectors, we mostly work on host-down situations. When a server is down, we troubleshoot using the detector infra host down and identify the root cause of the failure, such as why it was down or not reporting to Splunk Observability Cloud. We find out the root cause by using that detector when the alert gets triggered and cleared.

We use the tracing features in the Splunk Observability Cloud, primarily for application performance monitoring. It helps us figure out service maps for root cause analysis. It provides visibility and helps address blind spots in data collection.

Splunk Observability Cloud offers a transparent, customized tool with real-time visibility. We use AWS, ReactJS, Python, and Java for tracing. It helps create customized dashboards and service maps based on customer requirements. It has AI that automatically generates visualizations, allowing us to create more reports based on customer needs. My seniors are primarily working on creating dashboards, reports, and for monitoring purposes.

Their technical team is performing well. About a year ago, Splunk Observability Cloud was slow and lacked features compared to now. It didn't provide exact details for any searched server in the metrics, but the situation has improved significantly, and we can now retrieve complete data on when servers were down or up.

The best features in Splunk Observability Cloud are the metrics; I can see any logs or anything related to the server or services we want to monitor, and the metrics are a good function. It provides exact details. It offers unified visibility for logs, metrics, and traces.

In Splunk Observability Cloud, I notice room for improvement in synthetic monitoring. It does not provide output based on server names. It only gives a response when we input a URL. I'm not sure if this issue is specific to my organization, but it would be beneficial if server details could be retrieved directly in synthetic monitoring.

I have been using this solution for two years and two months.

I would rate its stability an eight out of ten.

I would rate its scalability an eight out of ten.

Around 100+ users access Splunk Observability Cloud in my organization, including the cloud SRE team, Windows Intel team, Linux team, and AD team.

My client base primarily consists of enterprise financial services.

If any issues arise, we can raise a vendor case, and resolutions are provided in a timely and accurate manner. 

Positive

In my organization, we also work with Sentry, Datadog, PagerDuty, and Dynatrace. Splunk Observability Cloud offers more features than Datadog, which also provides APM monitoring, log observer, and metrics, but does not match the feature set of Splunk Observability Cloud.

It is a bit complicated. For deploying Splunk Observability Cloud, we first need an access token, after which we connect to our AWS Cloud account and provide the access token. We must set up CloudWatch or AWS Lambda and forward the metrics or logs from all sources to AWS.

The implementation took about 45 days.

The return on investment varies based on requirements; for smaller tasks, we can leverage our team's capabilities effectively, so I can estimate around a 20% efficiency gain.

Currently, we are providing outputs to clients within the required time frames. If a client requests any dashboard, logs, APM monitoring, or synthetic monitoring, we have been able to deliver output on time, achieving approximately an 80% efficiency in response.

Splunk Observability Cloud is expensive.

For operational performance, we created monitoring within the Splunk Observability Cloud for most servers with agent installation. We upgraded the open telemetry collector from version 0.82 to 0.103, then again to a newer version, enhancing visibility and use cases, especially after the upgrade, which has improved operational purposes.

My impressions of Splunk Observability Cloud for focusing on business-critical initiatives are positive. I manage six tools, but Splunk Observability Cloud is one of my favorites, and I aspire to build my career specializing in it because it has great features, more attention in the market, and is a relatively new tool with promising growth.

I would recommend Splunk Observability Cloud to other users for its accurate data fetching, dashboard creation, report generation, and synthetic monitoring capabilities.

I would rate Splunk Observability Cloud a nine out of ten.

We primarily use Splunk Real User Monitoring to analyze performance bottlenecks and application transactions. It allows us to see how applications are experienced on the user side, making it easy to capture any bottlenecks or performance issues.

The most valuable features include user time tracking and the ability to analyze application load times. Splunk provides advanced notifications of roadblocks in the application, which helps us to improve and avoid impacts during high-volume days. It is very useful for identifying performance bottlenecks.

It would be beneficial to have more enhanced features with capabilities to adapt more integrated applications. Improvements in dashboard configuration, customization, and artificial intelligence functionalities are desired. There is room for improvement in customer support due to delays and standard feedback responses.

I have been working with Splunk Real User Monitoring for almost two years.

In terms of stability, I would rate it a nine out of ten. It is a very stable solution.

Splunk Real User Monitoring is definitely scalable. I would rate its scalability a nine out of ten.

Technical support is rated an eight. There is some delay in their in-depth responses and standard answers to questions.

Positive

I worked with Splunk alongside Dynatrace. Before Splunk, I did not use any other services.

It takes about an hour to set up the client for real-time monitoring.

We have a separate team for deployment, consisting of about three to four people.

We have achieved a return on investment between 10% to 20% as it helped in removing roadblocks, which could lead to more savings with wider usage.

Splunk is a little expensive, however, it is in line with the current market pricing. I would rate the pricing an eight on a scale of one to ten, as it reflects the going rate in the market.

I would recommend this product to other users because of its capabilities in monitoring and analytics. 

I rate the overall solution eight out of ten, considering the comparison with other products like Dynatrace.

For the retail sector, we are building a solution for customer stores in order to know how the products are sold.

The feature of Splunk Observability Cloud that I prefer most is the easy deployment on the cloud. The benefit of that feature for my organization is to optimize the deploys and implementation and the response to our customers, to quickly make a demo. Splunk Observability Cloud has helped improve our operational performance, especially for our customers.

My experience with the out-of-the-box customizable dashboards provided by Splunk Observability Cloud is that they are effective in showcasing IT performance to business leaders. For the initial point of contact, it helps and works nicely as a star point. Then, you have the basics and use that as a framework to deploy others, so they are very helpful.

Splunk Observability Cloud can be improved. In terms of additional features I would want to see in future releases, since Cisco acquired Splunk, more Cisco integration could be beneficial.

I have been using Splunk Observability Cloud for the last two years.

I have not experienced any downtime, crashes, or performance issues.

Splunk Observability Cloud scales very well with the growing needs of my organization, as we just need to add a license or data ingestion.

I would evaluate customer service and technical support for Splunk Observability Cloud as good. They respond effectively and in time.

Positive

Prior to adopting Splunk Observability Cloud, we used other solutions to address similar needs, such as Dynatrace and ElasticSearch.

It is easy to deploy on the cloud.

I have not seen a return on investment with Splunk Observability Cloud yet, as we are relatively new to it.

My experience with pricing, setup cost, and licensing of Splunk Observability Cloud is that it is somewhat expensive, considering I am from Mexico and the market in Mexico is very different from the market in the USA. It is expensive, especially when there are other vendors that offer something similar for much cheaper.

The factors that led me to consider the change to Splunk Observability Cloud include performance and cost, and it depends on the customer. If the customer is a network user or partner with all Cisco solutions, Splunk Observability Cloud fits perfectly.

However, if we have a new customer that doesn't have any Cisco products, it might be better for them to use another solution that is easier to deploy and not as complete as Splunk Observability Cloud, especially if they only need one or two features.

My advice to other organizations considering using Splunk Observability Cloud is that if you want a comprehensive, consistent tool or solution, it is one of the leaders in the market because it integrates with the network side of their organization, including Cisco solutions. Regarding customers who don't come from the Cisco world, it is a good choice, depending on their use. However, for small customers or those that are not large companies, Splunk Observability Cloud may not be the best fit, as it is a comprehensive tool. In Mexico, we observe that customers claim they only need APM or infrastructure monitoring, a very basic requirement, and don't require the entire Splunk portfolio.

On a scale of one to ten, I rate Splunk Observability Cloud a nine.

Splunk is primarily used for log monitoring, where I collect all my security logs, system logs, and application logs into a centralized place. This helps me customize my monitoring models.

Splunk has provided me with a centralized platform to manage multiple features. Instead of using various products, Splunk offers everything in one solution, which adds value to my organization.

The most valuable feature is the ability to customize dashboards based on my queries or any other customization I may need.

I'm still experiencing some features of the product. However, in future updates, I would like to see more predefined monitoring query solutions, which could be more effective.

I have been using Splunk Synthetic Monitoring for almost five years, primarily focusing on log monitoring.

Overall, the product is stable, and I would rate it an eight out of ten.

For scalability, I would give it a nine out of ten.

Technical support is good but could be improved, particularly concerning the time taken for ticket resolution.

Neutral

The main reason for choosing Splunk over other products is its comprehensive capabilities and flexible customization options. It is widely used and provides cloud solutions.

The initial setup was quite straightforward, and agent installation can be done quickly. However, the entire setup process might involve multiple people due to organizational policies.

The implementation process involved around five to ten people due to our organization's processes and need for multiple approvals.

Using Splunk has saved my organization about 30% of our budget compared to using multiple different monitoring products.

Splunk is a bit expensive since it charges based on the indexing rate of data. However, considering the features it provides, the pricing is quite affordable compared to other monitoring solutions.

Overall, I would recommend Splunk to anyone seeking a monitoring solution, thanks to its extensive capabilities and features.

I'd rate the solution nine out of ten.

Splunk Observability Cloud monitoring consists of spans and traces from applications, events or logs for applications, and infrastructure metrics, along with synthetics. Splunk Observability Cloud includes open-source features such as OpenTelemetry because it has the backend of OpenTelemetry. It behaves as an integrator between various receivers, exporters, and processors, thus providing end-to-end monitoring solutions for microservices and applications.

By using Splunk Observability Cloud, we were able to migrate our current metric system from Splunk Core to the observability platform that has reduced the impacted costs exponentially. Along with that, we have been able to integrate it with other platforms such as Xmatters or Splunk, indirectly creating an observability system for our NOC, as well as business teams to be able to view their insights about their applications and hosts and inventory on a single platform.

The first valuable feature is the backing of open source OpenTelemetry and GitHub. Then the continuous product improvement roadmaps. The great support and involvement by the product team is also valuable. Newer features are getting added on a regular basis.

The CNCF backing has enabled us to get the Splunk vendor to add more features to their own offering for Splunk Otel Collector, as well as us getting more insights into how we can go to a vendor-agnostic platform. OpenTelemetry and observability is still a new and niche skill in the market, and we are trying to get as much as possible into the product and ease the lives of operations teams as well as provide end-to-end monitoring to the business stakeholders.

One thing that has kept Splunk Observability Cloud offering a little bit behind their competitors is the ability to have a config management tool for all their OpenTelemetry collectors. Though it seems that it is already in the roadmap, however, the official release has not yet happened and also does not yet comprise of all the features that a config management tool should have.

Splunk can go ahead and integrate a GUI using the OpAMP protocol so that we are able to manage our fleet of collectors remotely, perform the upgrades of the collectors, perform restarts when required, or change of configurations via Splunk OLLY UI itself.

I have been using Splunk Observability Cloud since almost three years.

I have experienced stability issues.

Splunk Observability Cloud scales beautifully. We are able to scale it as per our requirements.

Customer support is good. The product team always has open arms for any of the newer features that we would like to request. They take feature requests in a constructive way. Whenever there are newer features that we would like Splunk Observability Cloud to have, they consider them. The generic Splunk vendor support is also good.

For observability related use cases, we did not use any previous solutions. Splunk Observability Cloud is something new that has been added as a newer offering to our wider teams and stakeholders.

Splunk Observability Cloud is a vendor purchase.

I am not certain how we would rate on the investment side of it. However, there have been a lot of teams that have started coming on board to our product from the operation side. Everyone does see a return on investment on this particular observability monitoring solution.

I am not familiar with the pricing model. Our architect or the relevant team may have more insights into it.

We did not evaluate other options. Splunk Observability Cloud had everything that we required it to be. The team who had discussions on their pricing and the monetary value of it were also happy with the product offering.

On a day-to-day basis, my task is to create more synthetic tests for endpoint monitoring that comprise various steps. These can span uptime tests or browser tests or also digital experience for real user monitoring. I am also responsible for monitoring and onboarding new hosts or Kubernetes clusters to monitor their infrastructure metrics or any instrumentation for application ranging from Python, Java, or manual code instrumentation.

It is very important because ours is a payment-facing application. We need to be informed in case any services related to the payment are not working or the payments are failing anywhere or at the back end, the infrastructure has any limitations or capacity restraints which is causing the services not to run as intended.

It has been a really great journey so far with Splunk Observability Cloud and we are keen to go ahead with the journey and with the vendor and the product. At the same time, we are also looking at vendor-agnostic solutions because it is an open-source backed application. For scalability of the organization, it has greatly affected and helped us out in terms of adding more and more hosts that are being monitored.

The value was visible to the relevant audience as soon as we started the implementation. Where it took the people a lot of manual efforts and time to diagnose their systems, they were able to get automated insights as an available feature within Splunk Observability Cloud.

Most of the dashboards and detectors that are out of box are great. I would say that dashboards are excellent. Detectors not so much because there are custom use cases that need to be built. Dashboards are definitely great, though. I would definitely recommend going for Splunk Observability Cloud. I would rate this review as a 9 out of 10.