We performed a comparison between Amazon CloudWatch and Splunk APM based on real PeerSpot user reviews.
Find out what your peers are saying about Splunk, Datadog, Wazuh and others in Log Management."What I found most valuable in Amazon CloudWatch is that it gives you detailed information, which I found helpful because it can even provide you with data for the past one minute, which is quite granular. That was what helped me most in terms of finding the root causes. Task automation is another valuable feature of Amazon CloudWatch."
"Amazon CloudWatch's best feature stems from its ability to monitor app performance."
"I can put it in a simple term, its simplicity is always there."
"The initial setup is easy."
"The monitoring features are valuable."
"You can enable alarms and metrics, and it has robust integration with AWS services. You can also trigger events. For example, if the CPU utilization is above 80%, it can launch a new instance for you."
"The most valuable feature of Amazon CloudWatch is intrusion prevention."
"The product can be integrated with AWS very easily."
"Splunk's dashboards are great."
"This solution is very quick to deploy as it is a SaaS solution and integrates with tools like ServiceNow."
"I like the fact that Splunk APM makes it easy to connect to the application database and run queries against the data."
"The solution's service map feature allows us to have a holistic overview and to see quickly where the issues are."
"Detectors are a powerful feature."
"The solution is stable and reliable."
"The features are pretty much ready out of the box."
"Splunk APM has helped us to standardize logging and monitoring procedures."
"Improvement of SSSD logs would be beneficial."
"There could be further enhancements through CloudWatch's partnerships."
"The dashboard of Amazon CloudWatch is not very customizable right now."
"Amazon CloudWatch's pricing needs improvement."
"The configuration capabilities could be better."
"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."
"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."
"Amazon CloudWatch needs improvement. The main thing is we have noticed missing logs."
"Splunk APM should include a better correlation between resources and infrastructure monitoring."
"The cardinality is pretty low."
"Primarily, the logs in Slunk 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 Slunk APM can require more effort to understand."
"The licensing model is expensive. We need to monitor the amount of data ingested because the cost is based on the data collected."
"The monitoring of workloads when using SignalFx could be improved."
"I've been using the Splunk query language, and it can be a bit time-consuming to set up the queries I need."
"They can improve the flow system and the keyword language. It has predefined keywords, but they can be improved."
"We currently lack log analysis capabilities in Splunk APM."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Splunk APM is ranked 14th in Application Performance Monitoring (APM) and Observability with 12 reviews. Amazon CloudWatch is rated 8.0, while Splunk APM is rated 8.2. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of Splunk APM writes "Provides great visibility, analysis, and data telemetry". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and SolarWinds NPM, whereas Splunk APM is most compared with Splunk ITSI (IT Service Intelligence), Sentry, Elastic Observability, Monte Carlo and Grafana.
We monitor all Log Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
