When comparing Cloudlytics vs Sumo Logic, the Slant community recommends Sumo Logic for most people. In the question“What are the best log management, aggregation & monitoring tools?” Sumo Logic is ranked 12th while Cloudlytics is ranked 16th. The most important reason people chose Sumo Logic is:
Sumo logic is entirely cloud based and very scalable.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Traffic analysis is provided using CloudFront logs
CloudFront analytics allows tracking what content is accessed and organize requests based on origin, amount, data transfered, OS/device/browser used, time, etc.
Pro Allows analyzing CloudTrail's API calls
Cloudlytics can be used to analyze CloutTrail's API calls to understand the geographical origin of requests and identifying unauthorized access attempts.
Pro Helps manage expenditure
Provides tools for analyzing bills.
Can schedule turning EC2 instances on and off to optimize resource cost.
Allows setting expenditure threshold values that will trigger an alert if a bill of a service has consumed 80%, 100% or more of set threshold.
Pro Provides AWS ELB insights
Cloudlytics provides insight into requests made to load balancer, including average response time, request path, server responses and client IP addresses.
Pro Allows scheduling when certain EC2 instances should be turned on or off
Usage of development and test environments can be optimized via scheduler. EC2 instances can be turned off when not needed.
Pro A free trial is available
The free trial lasts a month and allows uploading 200 MB of logs.
Pro Comprehensive log analytics solution for AWS Cloud
Cloudlytics can gather logs from Amazon's S3, CloudFront, CloudTrail and ELB services and provide insight into access patterns, API calls, requests made to load balancer as well as identify unauthorized access attempts, spam attacks, and help manage expenditure.
Pro AWS cloud audit allows identifying unauthorized access attempts
Cloud audit can be turned on via CloudTrail. It allows identifying unauthorized access attempts, IP addresses and request statuses.
Pro Allows identifying spam requests
Spam Reports can be used to identify possible spam requests and the IP address making them.
Pro Custom reports
Custom reports can be used to get insights for specific needs. For example, it's possible to add filters for parameters like edge locations, status, URL query etc. on various available fields like total requests, edge result type.
Pro Scalable
Sumo logic is entirely cloud based and very scalable.
Pro Flexible licensing model
Licensing cost is primarily determined by daily ingest of logs, however this is averaged out over 30 days instead of locking a user out of their own data after an arbitrary number of license breaches.
Pro Truly multi-tenant
Sumo Logic is truly multi-tenant, a single instance running on the server can serve multiple groups of users.
Pro A large set of supporting Apps
Allows customers to quickly setup and start getting actionable insights from their infrastructure by using Apps that integrate with various different platforms out of the box.
Cons
Con No Free Plan
Only 200 MBs are free for just the 1st month.
Con AWS services only
Highly focussed on AWS Cloud & if you are looking for analytics about your Cloud Infrastructure then this is your go to SaaS tool
Con Useless need for collectors
You have to install a plugin on each host to collect logs, the collector is 89MBs and is written in Java. there's no reason to install a Java tool to send syslog data when Linux already does that natively. The memory footprint for Java-based apps is way too high and, in this case, completely unnecessary.
Con Does not support structured data
They don't support RFC5424 standard events
Con Install is very painful
Con Search is very difficult
Here's an example:_sourceCategory=*windows* _sourceName=Security (4771 OR 4768 OR 4776 OR 4625) | parse regex "EventIdentifier = (?<event_id>\d+?);" | parse regex "ComputerName = \"(?<hostname>.+?)\"" | parse regex "(?:Result|Failure|Error) Code:.+?(?<result_code>0x[A-Fa-f\d]+)\b" nodrop | where result_code !="0x0" AND event_id in ("4771", "4768", "4776","4625") | count by hostname
Con Indexing and search are very slow
Sending around 45000 events to it may take more than 3 minutes to show up in the interface.
Once they show up, a search may take up to 32 seconds to return results. On only 45000 events, the search should return in milliseconds.
Con Difficult / Confusing Interface
The service and interface are very confusing.
Con There can be issues with smaller vendors
There may be some issues when using devices and services for smaller vendors which are not officially supported by Sumo Logic.