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.
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.
Primarily, our organization uses the solution to implement proper infrastructure in our campus environment.
The solution's basic visibility is one of its most valuable features. So, it is a solution that is easy to use.
The solution's stability is an area that has room for improvement. It needs to provide constant stability to its users. Also, the price of the license for the solution could be a bit better.
I have been using Splunk Infrastructure Monitoring for ten years. Also, I am using the solution's latest version.
It is a pretty stable product. Stability-wise, I rate the solution an eight out of ten.
It is a scalable solution. Scalability-wise, I rate the solution a seven out of ten. Around fifty to a hundred people are working on the solution. Also, the solution is extensively used in my organization. Currently, our company has no plans to increase the number of users using the solution.
The solution's initial setup process was straightforward. It took our company a week to complete the deployment process.
I implemented the solution in our organization.
I have seen an ROI using the solution in my company, especially in terms of increased visibility and productivity. Also, there is a commercial cost with increased visibility.
The solution's pricing is competitive. There is a need to make yearly payments for the licensing part. I rate the solution's pricing a seven out of ten. The price of the solution could be cheaper.
I would tell those planning to use the solution that they probably need to consider setting it up in a lab before deploying it.
Overall, I rate the solution a seven out of ten.
We primarily use the solution for monitoring.
The solution has a lot of features.
It's a good traditional monitoring platform.
The solution is stable and reliable.
It can scale well.
It's a little bit technical.
The cardinality is pretty low. They need to expand their reach.
I've been using the solution for three or four years.
The stability is good. I'd rate it eight out of ten. There are no bugs or glitches, and it doesn't crash or freeze.
The scalability of the solution is pretty good. I'd rate the ability to expand at an eight out of ten.
I'm not sure how many people are using the solution in our company.
Technical support has not been an area of the solution I've dealt with.
We previously used open-source solutions previously and found SignalFx to be better.
I wasn't directly involved in the deployment of the solution.
I have not looked into the ROI. I can't say if we have seen ROI or not.
I haven't dealt with the pricing and licensing aspects of the solution.
I don't know which version of the solution I'm using.
I'd rate the solution seven out of ten overall.
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.
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.
I primarily use Splunk APM for logging and metrics.
Splunk APM has helped us to standardize logging and monitoring procedures.
Splunk APM's most valuable feature is the application performance monitor.
Splunk APM's performance could be improved - at the moment, it's very slow and takes forever to give me what I want. Its documentation and accessibility to end-users could also be better.
I've been using Splunk APM for a year and a half.
I would rate Splunk APM five or six out of ten for stability.
Splunk APM scales well.
I would give Splunk APM a rating of four out of ten.
We primarily use the solution for event management. We have a baseline that we monitor, and if anything goes wrong, we manage it.
I haven't really used the solution too much, so I'm not sure if I can speak to the best features on the solution.
Without having used the solution too much, I don't really have any suggestions for feature improvement.
It would be useful if they provided some help pages. If you don't know too much about the tool, there should be more documentation readily available. It would be useful if they had a help button embedded in the solution so you could ask questions and get answers.
The solution should provide for some entry-level training.
We have a customer working on the solution. I haven't used the solution that much myself.
I haven't seen any issues with stability, however, I don't use it too much, so I wouldn't be able to make a very good judgement on if it was extremely stable or not.
I've never been in touch with technical support. I don't know how reliable they are, and would not be able to rate them.
The initial setup was straightforward. We didn't find it to be too complex.
I was able to handle the implementation myself. I didn't need the assistance of an integrator or consultant.
I did compare a few other tools, however, we are using Splunk because that is what the customer preferred. They made the decision after I described this solution and a few other tools to them.
I would definitely recommend the solution. I'd rate it eight out of ten.
I don't believe we have a business relationship with Splunk, but we do have a large number of licenses with them.