Sumo Logic vs Rocana
When comparing Sumo Logic vs Rocana, 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 Rocana is ranked 15th. 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 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.
Pro Great "out-of-the-box" analytics
Beyond simple rules-based alerting, Rocana Ops creates statistical models for each of the metrics you want to track and evaluates as data streams in to provide nearly instantaneous feedback on how your systems are performing. Unique WARN (Weighted Analytic Risk Notifications) Scores indicate components that are trending to the good or bad. Users can create custom metrics, which get evaluated just the same as "out-of-the-box" metrics.
Pro Highly scalable
Collect and analyze multiple TBs of data per day, built on Hadoop components Rocana Ops is a highly-distributed system offering massive scalability using commodity hardware. Rocana has customers collecting 10+ TBs of log data per day.
Rocana One free option provides up to 1TB of daily data volume for free.
Cons
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.
Con No free version
Con Expensive
Appears to be an expensive solution.
Con Doesn't run on a laptop
Well, maybe you can squeeze Rocana Ops on a laptop, but it is designed as a highly-distributed, fault-tolerant system and requires a Hadoop distro as the underlying platform.