Splunk Observability Cloud Reviews

Right now, I am using the infrastructure monitoring module. It's mostly for monitoring the infrastructure workloads. We can monitor our server, database and networks. It's mostly metric-based monitoring. 

The time to go live is very fast. It takes mere minutes for the sys admin to set up the solution.

The features are pretty much ready out of the box. 

The visualization is very user-friendly.

It is stable.

The solution scales well.

The pricing is very reasonable. 

We can't really configure the solution. 

The UI enhancements could be a way to improve the solution in the future. 

We'd like the solution to be better integrated with Splunk Cloud. 

I've used the solution for almost a year. I haven't used it for that long.

The solution is pretty stable. There are no bugs or glitches. It doesn't crash or freeze. It is reliable. 

This is a very scalable solution. You can have different deployment modules. It's flexible. 

I've never contacted technical support. We don't take care of that aspect of the product. 

This offers a very easy setup.

The deployment is fast. It was very quick. It does depend on how fast your infrastructure is. 

The solution is reasonably priced compared to the competition. We do not find it very expensive at all. 

I'm an end-user and customer.

We're using the SaaS deployment. We don't have visibility into the version number. 

I'd recommend the solution. We've had a good experience firsthand. It's a very simple solution to grasp and understand from an end-user perspective. You just might need a bot of configuration to visualize the data. 

I'd rate the solution nine out of ten. 

I am using Splunk APM mostly for telemetry and logs.

The Splunk APM proves to be extremely useful for troubleshooting production issues. We rely heavily on its detectors to monitor the traffic flow between microservices, and any sudden deviations in traffic, whether due to errors or changes in inflow, trigger alerts. This allows us to quickly investigate the source of the traffic and identify bottlenecks in the microservice ecosystem. once we have a problem, we are looking through the logs, and it has really helpful filters. We are able to find what we want quickly.

When an issue arises, we search through the logs using the highly effective filters that are provided. This enables us to quickly locate the required information with ease.

The most beneficial aspect of Splunk APM is the ATM, which is the map displaying the inbound and outbound relationships of the microservices, as well as the traffic between these dependencies. This feature provides us with valuable insights and helps us understand the interactions between different microservices.

Primarily, the logs in Splunk APM can be challenging to navigate and comprehend, making it difficult to understand the details within each log. Compared to other tools like LogDNA, which are more intuitive in this aspect, the logs in Splunk APM can require more effort to understand.

It would be beneficial to have a feature that addresses the scaling of microservices. At times, issues with microservices may not be related to the code, but rather to the available resources. Therefore, it would be useful to have a feature that indicates the status of the microservices, including their scaling status and any relationship between the two.

I have been using Splunk APM for approximately one year.

The metrics in Splunk APM may not always be accurate as they depend on the computer generating the report. If the reporting machine is underperforming, it can show lower metrics, which can be misleading. Therefore, it's important to be cautious when relying solely on Splunk APM for accurate metrics.

I rate the scalability of Splunk APM an eight out of ten.

The scalability of the solution is good.

We plan to increase our usage because new features of the solution are coming out.

I rate the scalability of Splunk APM an eight out of ten.

I have not used the support. I did not have any problems.

I have previously used LogDNA for logs and Newrelic for telemetry .

The initial setup of Splunk APM was straightforward.

We have received a return on investment after switching from our previous solution to Splunk APM.

The price of Splunk APM is less than some of its competitors.

We choose Splunk APM over other solutions because of the cost benefits.

If you're planning to use Splunk APM, my suggestion is to exercise caution, especially if the machines you're using are under heavy load with graphics or other resource-intensive tasks. In such scenarios, the data you get from Splunk APM may not be entirely reliable. Nonetheless, it's an excellent tool that can provide a comprehensive overview of your system if you integrate it into all aspects of your operations. With Splunk APM, you can easily identify bottlenecks and improve your programs, making it an incredibly useful tool.

I rate Splunk APM an eight out of ten.

We primarily use the solution in order to monitor the servers as well as the VM infrastructure.

We are now able to monitor our infrastructure and get the information in real-time should anything happen. In terms of the hard drive hitting the threshold, then we'll get notified and the technician can attend to it. It reduces the time to attend to the incidents and allows you to be aware of our infrastructure as the status of our infrastructure is visible via dashboards.

The monitoring and the reporting tools are great. It can monitor, get the data, and then report on the data. 

You have the dashboard to see your different items. You create the dashboard to see if there was any incident as well; it creates incident reports for you. For example, if the hard drive goes beyond a certain limit, you can get notified. You can look at your CPU utilization or memory as well. You can set thresholds and monitor for all different types of information.

The solution is stable and reliable.

Technical support is helpful. 

We have witnessed an ROI while using it. 

Overall, I cannot think of any features that are missing.

The deployment can be quite complex. 

I've been using the solution for two years now. 

The solution is stable and reliable. There are no bugs or glitches. it doesn't crash or freeze. 

We have about 100 people on the solution. Some of them don't use the solution directly, however, they benefit from the solution.

Technical support is fairly good. We are satisfied with their assistance. 

I used other solutions before, which were LiveAction, and Cisco Prime. They were used to monitor.

Currently, I'm using PRTG for network monitoring, to monitor the network devices. With Splunk, we monitor servers, and with PRTG, we monitor the network devices such as routers, IPs, and switches.

The initial setup is very straightforward. That said, the configuration and all those things you need to do to make it work according to what you want, you need to deploy some apps, and some that part is what is not straightforward about the setup.

The deployment took about three months.

There are three of us that handle deployment or maintenance. 

We are an integrator team; we actually had help from Splunk themselves to implement the solution.

We have seen an ROI.

It's affordable when you compare it to HPSA - the HP Server Administration.

You get the things according to your data - the data that you need to report on. The capacity of the data that you need to report on. Right now, it's set to 100GBs. We've got the license for 100GBs.

There are different companies or customers that we support within the company. Whichever product they have that's what we go with. For example, we might use AlgoSec, Cisco Prime, or LiveAction as the customer that was using it. We don't evaluate other solutions, we use what is already there.

I did not handle the choice of Splunk. I got into the stage where the system or the application was already implemented. I did not participate in the stage where we had to choose which solution to pick or how to implement it.

We partner with Splunk. We use the product to deliver it to our customers. We're an integrator. We're just using the product to service our customers.

I'd advise new users that it is a very good product, however, you need to have some knowledge and do some training on the product in order to gather knowledge so that you can understand and implement it effectively. 

I'd rate the solution a nine out of ten.

Splunk Infrastructure Monitoring provides end-to-end visibility into our cloud-native environments. It is very important for us.

Splunk Infrastructure Monitoring has helped reduce our mean time to resolve.

It is digitalized. It has been beneficial for our IT infrastructure.

The security could be better.

I have been using Splunk Infrastructure Monitoring for 11 years.

I usually use the community site. I find that helpful.

We did not use any other solution previously.

We set it up ourselves.

I would rate Splunk Infrastructure Monitoring a ten out of ten.

We use this solution to monitor all our FaaS workloads.

This solution is very quick to deploy as it is a SaaS solution and integrates with tools like ServiceNow.

The monitoring of workloads when using SignalFx could be improved. 

We have used this solution for more than 20 years. 

This is a stable solution. 

This is a scalable solution. 

We have received good technical support when needed. 

Positive

I would rate this solution an eight out of ten. 

Splunk sends security alerts. It's being used on two levels. One for the analysis of the data by the data scientists. Two, for the engineers to troubleshoot if there are any issues happening, like any security bugs, or anything that needs to be addressed and never mediated across. 

In terms of the application performance security, application performance tooling has been a key factor for me using Splunk. We are also looking into options, like other third parties or even open-source tools that help the capturing the application performance, fine-tuning, which leads to the security aspect.

We haven't faced any problems yet. It's working as expected. We are using the enterprise-grade, strong products and we're just paying a lot for it right now.

People intend to go for automation. We are following the works process and we are inculcating the engineers to ensure everything is automated. Whatever needs to be mitigated, has to be followed up on ticketing tools, this tool would come in. It handles the issues going on and what needs to be remediated in this single tool.

We need multiple tools in order to accomplish what we need. It's kind of a medium across multiple products. It would be better if we have a dedicated tool, that takes care of the entire work process, including automation as well.

They do not have all the features that I expect right now.

I have been using Splunk for three years. 

We haven't really experienced any glitches or bugs. It depends on the use cases and so far I haven't seen any as of now.

It is scalable.

They're good. They're quite good at providing the service for technical engineers as well.

I would say that the setup is pretty straightforward because they have their own documentation that you can follow. It takes an associate's capability in order to accomplish it. They have good documentation and dedicated support to take care of any issues that come forward.

As a newbie, I wouldn't prefer Splunk. The reason being that it's a completely enterprise-grade solution. As a startup, you don't implement Splunk for the first time. We'd put an open-source product. With us, we have many of the Italian products, which proves to be a good open-source solution. In the end, people intend to go for enterprise support for the vulnerability patching, report generation, and enterprise support. People go for licensing based on that. I wouldn't refer any newbies to go for a weak enterprise-grade solution as they barge into any technology.

I would rate Splunk a seven out of ten. 

The data from Splunk is used for network monitoring, apart from that, they are using another tool with this kind of logic as well. Splunk is not the primary tool. The database I'm using for real-time data for our client. We have only about 3-4 users on this solution.

It's only the monitoring solution that we are using. I'll find that to be a great feature.

Splunk would be better if some tools were integrated to be able to take action on security or network concerns. People in the IT field are looking for a single tool that can do everything. Not separate tools for monitoring and fixing.

We have been using Splunk Insights for infrastructure for about one year.

I have not had any problems with stability.

Nothing is straightforward in data technology. You have to know about the technology. Even when chatting about the virtual image for a window, we need to know how to do things. If you know how the technology works, it's really simple.

I need a tool that can deal with all the security solutions, that will find security monitoring compliance requirements. So, I'll stick to BigFix over Splunk, because I'm not that big a fan of Splunk, to be honest. Apart from monitoring, in BigFix you can mitigate the issues, mitigate what the vendor is doing, and continue monitoring our clients. If any machine, any hardware in the department is vulnerable to any threat, with BigFix we can go ahead and take action, and mitigate that vulnerability within a couple of minutes.

I would rate Splunk Insights for Infrastructure at a seven out of ten.

The solution is primarily used as security correlation and event correlation. It's a place for all of your logs to go so that you can have all those logs co-ordinated during security events. 

The solution brings all the events into one platform so that you don't have to hunt down multiple sources to figure out what's going on.

The ability to create custom dashboards is one of the best features and that's typically why most people deploy Splunk. Users can create dashboards for just about anything.

The solution has been improving its offering for the past year. It's in constant development.

The cost needs to be re-examined. It's extremely expensive to run. It's also expensive to expand. That's the number one complaint all of my customers have when it comes to Splunk. It's way too expensive compared to other solutions.

The integration of their cloud solution, which came out a couple of years ago, and the ability to now integrate Phantom, needs to be improved. 

It would be ideal if there was a more automated process for finding and identifying data sources that a user wants to bring into the solution. Right now, it's all manual.

I've been selling the solution for quite a long time. I'd say I've sold it for five years. I've been involved in deployments and I've been involved in configuring it and managing it, but I don't actually use it for my company.

The solution is extremely stable. We haven't run into issues that would make us concerned.

The solution is very scalable. However, companies must be aware that expanding the solution is very expensive.

I'd rate technical support eight out of ten. They're responsive due to the fact that clients need to pay in order to access technical support.

The initial setup is not straightforward. It's quite complex. 

The storage backend requires touching all of your events sources. It requires a lot of planning and configuration. It's not something you just put out there and deploy. You have to have someone who's an expert in it.

The deployment typically takes, from beginning to end, less than three months. However, it really depends. It depends upon how many log sources you have, if you have staff on-site that are capable of actually running it, or if you have to make network configuration changes, etc. There's a whole list of things that you have to go through to figure it out. 

The number of people needed to deploy the solution varies upon the size of an organization and the use cases. You're going to want at least two dedicated people to deploy at a medium-sized organization.

These individuals have to understand searching and creating dashboards. They have to have network skills and security skills. There is a wide range of things they have to be a part of. Most people who become Splunk Engineers start off doing something else in their business and they learn about networking, and then security and programming. When they start to deploy Splunk, they become experts.

The solution requires the assistance of a specialist. There needs to be an expert involved to help implement it.

Licensing is paid on a yearly basis.

We work with a few different solutions. As a SIEM, there are many other solutions out there and which is best really depends upon what the company wants to achieve.  As a logging server, there really aren't any other really good solutions that compete as well with Splunk. LogLogic might be the closest.

We're a Splunk partner and reseller.

Typically, the solution is on-prem for the most part because it requires a very heavy lift in storage and the storage is very expensive. Most companies deploy it on-premise and then add on the cloud solution as well later on.

I'd warn other organizations that want to use the solution that they need to be prepared to spend a lot of money.

I'd rate the solution seven out of ten due to the fact that it's extremely complex to run and deploy.