When comparing Logentries vs LogZilla, the Slant community recommends Logentries for most people. In the question“What are the best log aggregation & monitoring tools?” Logentries is ranked 1st while LogZilla is ranked 16th. The most important reason people chose Logentries is:
Alerts can be created based on tags or by setting criteria via the intuitive and powerful [search](https://logentries.com/doc/search/) capabilities of LogEntries. To not flood notifications it's possible to specify limitations for alerts, such as how many times an hour an event has to happen for it to trigger a notification. Notifications can be sent by email, mobile messaging or via [webhooks](https://logentries.com/doc/webhookalert/) (webhooks are sent server in real-time, so there's no need for polling for changes).
Ranked in these QuestionsQuestion Ranking
Pro Real-time alerts
Alerts can be created based on tags or by setting criteria via the intuitive and powerful search capabilities of LogEntries. To not flood notifications it's possible to specify limitations for alerts, such as how many times an hour an event has to happen for it to trigger a notification. Notifications can be sent by email, mobile messaging or via webhooks (webhooks are sent server in real-time, so there's no need for polling for changes).
Pro Supports a diverse set of programming languages
Including Java, .Net, Ruby, PHP, node.js, Python.
Pro Free up to 5 GB
Logentries free product allows uploading up to 5 GB of logs a month and has a 7-day retention period. The free product is available after the 30-day trial ends.
Pro Works with multiple PaaS and IaaS
Logentries works with Amazon Web Services (AWS), Heroku, AppFog, Engine Yard and other platform as a service (PaaS) providers, along with Amazon Web Services, Rackspace, Microsoft Azure and other infrastructure as a service (IaaS) providers.
Pro Event and search updates can be viewed in real-time
In Live Tail mode events and searches update in real-time. Live Tail mode can be used in Aggregate View, that allows selecting a combination of logfiles to be viewed together, and with any log groups created. These events are supplemented with tags to allows getting an overview of current events quickly at a glance.
Pro Supports the most popular programming frameworks
Supports the most popular programming frameworks, including Ruby and node.js.
Pro Offers an easy way of visualizing data via graphs
LogEntries allows each logfile to have a separate dashboard of various graphs & widgets put together for visualizing data. A dashboard is put together by dragging & dropping graphs and widgets into place. Graphs and widgets include charts, tables, gauges, event counts among other forms of data visualization.
Pro Real-time tagging makes reading logs easier
Colored indicators can be set that highlight events in a log in real-time based on given criteria. Criteria are set via intuitive and powerful search capabilities of LogEntries.
Pro Easy to set up
Logentries can be set up quickly and with relative ease.
Pro Great search
LogEntries has human readable, intuitive and powerful search with support for logical expressions, comparison expressions, regular expressions and ability to search based on field, group based on approximations over time, use functions such as count, sum, average and unique as well as save searches.
Pro Timestamps are displayed in the local time zone
Unlike Loggly, LogEntries displays timestamps in your timezone. You don't even have to configure anything.
Pro Excellent documentation
LogEntries has comprehensive documentation that's easy to read and understand and includes lots of screenshots and examples.
Pro Good technical support
Answer incidents pretty quickly.
Pro Prepared viewlets
Easy to get information fast with integrated dashboards. Also I can change as I want easy by rewriting query
Pro Average repair time is heavily reduced by scripted responses
Proactive, automated remediation of problems that always take way too long to find and solve are easily and actively repaired by using scripted responses.
Pro Integrates with many third-party services
They have a "Trigger" interface which lets you set alerts, send to email, send to Slack (Webhooks) and also can send to scripts which lets you do just about anything imaginable such as looking up other sources of information about an event (device info, last 5 logins, change management, etc.).
Pro The dashboards are great
You can see the data in real time and choose what you want to see. You can also create several dashboards (easy to create) to get all the views of your data, allowing you to be proactive with your network.
Pro Easy to install
LogZilla can be installed with a single command and usually takes less than ten minutes to install.
Pro Great usability
Logzilla gives users the ability to pull real time data sorted by host severity and lets users watch actual network events come through.
Pro Relatively low cost
Pro Unlimited retention
Patented deduplication means that 120TB of data may be as little as 6 TB (95% reduction) with zero bytes lost.
Pro Lets you create custom reports
LogZilla lets you create lots of customized reports including Top Hosts, Top Errors, Top Security Violations, etc. It is also useful for generating compliance reports to support PCI, HIPAA and other auditable requirements.
Pro Log spike flooding does not take down the logging system
There have been instances where the flood increased almost 17,000 more logs per second with no performance degredation.
Pro Automated Remediation
Automated Remediation was added a few months ago. It's amazing. Any data can be parsed using a simple script, and arbitrary responses can be created. Problems are identified in millisecond real-time, and solved a few seconds later. Any NetOps team can be proactive about the network, rather constantly chasing problems. The pre-loaded dashboards can be chosen or deleted as needed. Kuddos to LogZilla. There is nothing that is this simple to use, and certainly nothing this powerful.
Con Confusing interface
The interface is packed with features and options, many of them I'm not sure what they do at all.
Con Limited search capabilites
Compared to Elasticsearch and other competitors, search syntax has few features, apart from regexp and NOT/AND/OR combining. E.g. has no syntax to determine if a field is absent.
Con Character limit for each log entry
Currently log entries are limited to 8192 characters, if your log entry runs over this amount then it will be truncated where the excess log will be a new entry in the UI. This can easily cause a problem JSON structure with java stacktraces.
The average plan is over $1.5 per GB, which can get very expensive for any sort of reasonable volume.
Con Short retention
The retention is very short (14 - 30 days).
Con There's a limit of 100 logs per server
Should you have a webserver that hosts many sites, you'll hit this undocumented limit. The token-based alternative solution is inconvenient to set up and maintain.
Con Can't track the source of errors in 3rd party libraries
Con Insufficiently secure web client logger
No progress since this was reported in September 2013.
Con Grouping is unsorted and limited
Eg. you can't really check what browsers people use, because the report is limited to 40 unique strings.
Con Blocked by ad blockers by default
https://easylist-downloads.adblockplus.org/easyprivacy.txt includes logentries
Con Signing up requires phone number
Con No CDN for the web client logger
Con TypeErrors (X is not a function) are not tracked
Loggly catches them by default. LogEntries doesn't seem to catch them even if
catchall is set to
true. See the GitHub issue.
Con Poor customer support
Support is lacking and not as responsive as would be desirable.
The system is self-hosted and complicated to setup.
You must purchase a license that is based on the number of messages sent. This quickly becomes more expensive. Additionally, the pricing is not public, you have to reach out to them to get pricing for your specific setup.
Con Interface is hard to use
The interface is very data centric, which is good, but it is hard to use and often confusing. Many times actions result in no data or errors.