When comparing Logentries vs jKool, the Slant community recommends Logentries for most people. In the question“What are the best log aggregation & monitoring tools?” Logentries is ranked 1st while jKool is ranked 31st. 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 Subscriptions to real-time updates
Subscriptions to real-time updates from infrastructure systems gives users proactive detection of application anomalies, as well as performance, availability and capacity issues. This enables users to capture perishable insights into application issues that they would normally miss.
Pro Offers free option
JKool offers free option limited by daily data volume and retention. Easy to sign up and try. No commitment or credit card required to signup.
Pro Simple English-like query language
jKool uses JKQL (english like query language) to search real-time and historical events, metrics and transaction streams. It includes verbs like GET, SUBSCRIBE, COMPARE, etc. Compare allows comparison of events, activities and metrics.
Pro Open source connectors
jKool offers open source connectors available hosted on GitHub: syslog, log4j, slf4j, logback, jmx, Spark, HDFS, JMS, MQTT, Logstash etc.
Pro Analyze logs: syslog, log4j, logback and others
You can use the jKool log collectors to stream syslogs and other logs to a jKool and be able to view and analyze your logs in a graphical oriented way. jKool can show error rates, anomalies, exceptions, groups, time buckets, time windows, aggregations and apply math functions across all your logs.
Pro Supports Logstash as a datasource
jKool can consume incoming streams directly from Logstash. Combine Logstash with other streams to deliver a unified application view. Logstash integration is open source.
Pro True multi-tenancy
Supports concepts of data repositories, organizations, teams and users which allows logical data separation and access control.
Pro Real-time search
Search for events, transcations, metrics streams in real-time before data is indexed.
Pro Automatic anomaly detection
Helps to proactively detect potential anomalous behavior and prevent problems from occurring.
Pro Unique Visualization
Visualization is generated dynamically based on a data query as opposed to the typical canned views that have nothing to do with the specific query.
Pro More than log analyzer
jKool does much more than just log analysis. Examples: end-user monitoring, application performance, transaction tracking, business metrics and IoT. Developers can use APIs (java, REST) to build extensions for streaming, visualization. jKool provides a unified model for all time series machine data.
Pro Simple, easy to use, great UI
There are really only 2 things a user needs to do to show charts, graphs: 1) create a dashboard 2) Create viewlets. Each viewlets is bound with a JQKL query. JQKL queries can be typed in or built via a query builder for beginners. Pretty easy to get up and running without learning JQKL. There is also a UI tutorial once you logon to jKool.
Pro Self service dashboard for users with different responsibilities.
Provides situational awareness to users from their own perspective. The benefits are translated to reduction of support calls and visibility for each user, from their own angles into root causes of problems within a couple of clicks.
Pro Unified analytics support
Combines analytics for events, metrics (name, value pairs) and transactions with real-time and historical analytics in a single platform.
Pro Transaction Tracking & Discovery
jKool is able to automatically connect/stitch multiple events coming from multiple sources into a business transaction(s), measure performance, completion, progress. Transactions can be grouped into user defined sets (payment, claims, etc).
Pro Simple model: Stream Data->Run Queries->Analyze
Easy to use cloud based log and application analytics supporting standards such as Syslog, log4j, log files, end-user monitoring, transaction tracking. No schemas to define, agentless, no servers or storage to setup. Provides true transaction stitching and analytics -- track all transactions, 100% of the time. On-premise and cloud based (docker support available).
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 Doesn't seem to be very popular
JKool is a relatively new tool, as such, there don't seem to be many third party guides and tutorials other than from official sources from the JKool team.