Amazon CloudWatch vs Splunk Infrastructure Monitoring comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Amazon CloudWatch
Ranking in Cloud Monitoring Software
9th
Average Rating
8.0
Number of Reviews
40
Ranking in other categories
Log Management (12th)
Splunk Infrastructure Monit...
Ranking in Cloud Monitoring Software
14th
Average Rating
8.2
Number of Reviews
24
Ranking in other categories
IT Infrastructure Monitoring (15th), Container Management (11th)
 

Market share comparison

As of June 2024, in the Cloud Monitoring Software category, the market share of Amazon CloudWatch is 8.0% and it increased by 0.6% compared to the previous year. The market share of Splunk Infrastructure Monitoring is 0.8% and it increased by 126.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Monitoring Software
Unique Categories:
Log Management
1.8%
IT Infrastructure Monitoring
0.4%
Container Management
0.3%
 

Featured Reviews

Alex Kabugo - PeerSpot reviewer
Aug 21, 2023
A cloud solution for monitoring the devices with a scheduling feature
When you set up CloudWatch, you can't even take a lot without checking on them or without going through the whole configuration because we're configuring. It's not a frequent feature you always work on. The integration requires a lot of permissions and the tool delays in providing notifications. Sometimes, receiving a notification after an update takes a long time. So, we prefer using a monitoring tool like New Relic or Grafana. Another area of improvement is scheduling. CloudWatch is complicated when it comes to scheduling. If you want to monitor the component, the configuration is not straightforward. You need good knowledge for something to be added there.
MA
Aug 3, 2023
User-friendly, offers good visibility through the logs, and helps identify issues in our environment
We use Splunk Infrastructure Monitoring because it is a durable solution for our environment Splunk Infrastructure Monitoring is easy to use. The dashboards are good. Splunk Infrastructure Monitoring has helped improve our operational performance and efficiency.  Splunk Infrastructure Monitoring…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The monitoring feature is valuable."
"The tool's UI is good. One can scroll through the logs very easily."
"Every time we get an alarm or have an incident, CloudWatch is always there. We use it not only for resources we've spun up in the cloud, but also for some of our on-premises resources."
"We can create events and alerts. We use the information to dive down into the infrastructure performance."
"The product helps us collect and store various metrics to set test alarms."
"Scheduling is a valuable feature."
"The most valuable feature of Amazon CloudWatch is reliability."
"Setting up this product was easy. I found data analytics as its most valuable feature."
"The most valuable feature in this solution is the log searching."
"Splunk Infrastructure Monitoring gives us complete visibility without the need for storage."
"The tool is efficient in collecting, monitoring and evaluating logs."
"The solution's most valuable aspect is its ability to get information about all of the security measurements in my environment."
"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."
"Great monitoring of network devices."
"It's a very easy-to-use solution."
"The vibrant dashboards are valuable."
 

Cons

"The dashboard of Amazon CloudWatch is not very customizable right now."
"There is room for improvement in terms of stability."
"The product should provide more features."
"I found several areas for improvement in Amazon CloudWatch. First is that it's tough to track issues and find out where it's going wrong. The process takes longer. For example, if I get an exception error, I read the logs, search, go to AWS Cloud, then to the groups to find the keyword to determine what's wrong. Another area for improvement in Amazon CloudWatch is that it's slow in terms of log streaming. It requires an entire twenty-four hours for scanning, rather than just one hour. This issue can be solved with Elasticsearch streaming with Kibana, but it requires a lot of development effort and integration with Kibana or Splunk, and this also means I need a separate developer and software technical stack to do the indexing and streaming to Kibana. It's a manual effort that you need to do properly, so log streaming should be improved in Amazon CloudWatch. The AWS support person should also have a better understanding of the logs in Amazon CloudWatch. What I'd like added to the solution is a more advanced search function, particularly one that can tell you more information or special information. Right now, the search function is difficult to use because it only gives you limited data. For example, I got an error message saying that the policy wasn't created. I only know the amount the customer paid for the policy, the mobile number, and the customer name, but if I use those details, the information won't show up on the logs. I need to enter more details, so that's the type of fuzzy matching Amazon CloudWatch won't provide. If this type of search functionality is provided, it will be very helpful for businesses and companies that provide professional services to customers, like ours."
"I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing."
"The drill-down aspect on the dashboard of the solution needs improvement. We get a very good high-level overview, but when we drill down, it becomes a little less clear. We have given this feedback to AWS as well and hope they will improve this in the future."
"There could be further enhancements through CloudWatch's partnerships."
"There's a learning curve with Amazon CloudWatch since we have to learn to write the queries to extract the keys and logs."
"The price has room for improvement."
"The deployment can be quite complex."
"It's a bit difficult to use. It takes some time to get into it and to get it to do what you would like it to do. It is not straightforward to use it."
"We have both on-prem and cloud, and the challenge is getting all our log data aggregated or streams aggregated so that it is real-time. We do a pretty good job of that, but our organization is not using it as a security platform when it can do a great job of that."
"The end-to-end visibility is lacking because Splunk cannot directly monitor network devices."
"There is a lot of room for improvement with the automation."
"The product collects a lot of data but it does not assure that it collects all of it."
"Splunk could be better integrated with configuration manager solutions so we can automatically resolve issues without human interference."
 

Pricing and Cost Advice

"What's were using is the free service of Amazon CloudWatch, so they're not charging us. As for hidden fees, we're not aware of them because we're using what our clients provided us."
"Amazon CloudWatch has very cheap pricing, and it hardly costs my company $25-$30 a month for fifty systems, so it's pretty affordable."
"It’s an open-source solution."
"It is a free-of-charge service."
"The pricing model is pay-as-you-go so you have to be mindful of usage to manage costs."
"The price is okay for me."
"We have monthly licensing costs. The licenses are probably in the vicinity of about $300 - $350/month."
"The pricing is average."
"Splunk has been fairly expensive, but it has been predictable."
"It is expensive."
"The solution's pricing is competitive. I rate the solution's pricing a seven out of ten. The price of the solution could be cheaper."
"I am not in that circle, but we are currently licensing based on our queries. That is working out for us. Previously, it was by volume of data, and now, we can store as much data as we want."
"This is an expensive solution."
"The product is a bit expensive considering the competition but the company may negotiate the price."
"Splunk's infrastructure monitoring costs can be high because our billing is based on data volume measured in terabytes, rather than the number of devices being monitored."
"I would rate the price of Splunk Infrastructure Monitoring as an eight out of ten, with ten being the most expensive."
report
Use our free recommendation engine to learn which Cloud Monitoring Software solutions are best for your needs.
787,226 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
17%
Manufacturing Company
6%
Government
6%
Financial Services Firm
17%
Computer Software Company
14%
Government
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Amazon CloudWatch?
CloudWatch doesn’t monitor disk throughput by default. It is part of EC2. If EC2 forwards the logs, then we can do it.
What is your experience regarding pricing and costs for Splunk Infrastructure Monitoring?
Splunk's infrastructure monitoring costs can be high because our billing is based on data volume measured in terabytes, rather than the number of devices being monitored. Replacing legacy systems w...
What needs improvement with Splunk Infrastructure Monitoring?
The main drawback of Splunk for network monitoring is its limited agent deployment. Splunk excels at collecting data from servers and databases where agents can be installed. However, it cannot dir...
 

Also Known As

No data available
Splunk Insights for Infrastructure
 

Overview

 

Sample Customers

AirAsia, Airbnb, Aircel, APUS, Avazu, Casa & Video, Futbol Club Barcelona (FCBarcelona), National Taiwan University, redBus
Entrust Datacard
Find out what your peers are saying about Amazon CloudWatch vs. Splunk Infrastructure Monitoring and other solutions. Updated: May 2024.
787,226 professionals have used our research since 2012.