Seven log management tools for Java Programmers (GO)

Splunk vs. Sumo Logic vs. LogStash vs. GrayLog vs. Loggly vs. Papertrails vs. Splunk>storm

English Original: The 7 Log Management Tools need to Know

Log management tools include Splunk, Sumo Logic, LogStash, GrayLog, Loggly, and Papertrails, among others. The logs are like oil, more than 20 years. We have been trying to get rid of it, but have not done it.

In order to handle the growing data, a large number of tools for analyzing and managing logs have emerged in recent years, and developers and managers can use these tools to understand the growing data. In this article, I will stand in the developer's perspective and analyze the features of these tools.

Splunk

As the largest tool in this field, I decided to make a separate classification of Splunk. This is not to say that the tool is the best, but to give certainty to the product because it creates a new field in nature.

Advantages

Perhaps the most complete feature in this area is the Splunk. It has hundreds of programs to analyze various forms of log information (I count 537)-from security leadership to business analytics to bottom-up monitoring. Splunk's search and charting tools are so rich that they don't get data through it (UI and API).

Disadvantages

There are two main disadvantages of Splunk. First, this factor may be subjective, and I think the solution is too complex. If you are deploying in a highly complex environment, you need to install and configure a dedicated cluster. As a developer, this is often not the first choice for this scenario.

The second drawback is that it is too expensive. To support a real-world software, you might spend more than $10,000, which probably means you need to cut your budget from somewhere else, so the development process is slow. If you've just got an app on the shelves, but get high-quality log analytics without compromising the development process-read on.

For more enterprise Log analysis tools, click here.

SaaS Log Analysis tool

Sumo Logic

Sumo is a SaaS version built on Splunk, which inherits some of the early features and visuals of Splunk. It has to be said that SL has evolved into a mature enterprise-level log management tool today.

Advantages

SL is capable of simplifying, locating, and charting data. It's probably the most powerful of the SaaS-type log analysis tools. Similarly, as a SaaS type, SL also has the advantages of simple installation and simple operation. The most appealing thing is that you can set up a baseline that you can receive dynamic notifications when an event (like a new version is first launched or a malicious request) makes some important metrics change.

Disadvantages

Since this is a SaaS-based log analysis, you have to upload a large amount of data to the server for analysis, which may cause some problems:

1. As a developer, if the logs to be analyzed involve sensitive information or PII, you need to make sure you're blocking.
2. There may be some conflicts between the time the log was generated and the time the log was uploaded to the service.
3. A few gigabytes of overhead on your machine is used to upload logs, but it depends on the throughput of your logs.

The purchase price of the Sumo service is not transparent, so it can be a hassle if you want to swipe your team's credit card to buy it.

The update --SL team just told us that you can buy the service directly from the free version of your credit card, although not as convenient as the web version, but it's pretty good.

Loggly

Loggly is also a robust log analysis tool that emphasizes simplicity and ease of use for developers.

Advantages

SL focuses on enterprise-level application and security, while Loggly focuses on helping developers find and fix operational issues. Because the interface is very user-friendly, customizing performance and developer Dashboards is a simple thing to do. And its price is transparent, easy to get started.

Disadvantages

Don't expect Loggly to have a proven architecture, security, and analytics solution. Loggly does not have a forensics and monitoring infrastructure, it is just a tool to help developers with application server data. There are other things you need to do on your own.

papertrails

Papertrails is good at finding logs from multiple machines and providing a consolidated window for easy use. Since you're tracking logs from the cloud, you're not too far from them.

Advantages

PT is such a tool. With it you can easily find logs on multiple machines from one window. The user action itself is like a log on your machine, and the search command is the same. It is dedicated to make log management simple, easy to use, and elegant to handle. And it's not too expensive.

Disadvantages

PT is a text-based format. If you need to support advanced integration, forecasting, and reporting capabilities, you're out of your league.

Splunk>storm

This is Splunk's brother, hosted on a Splunk server.

Advantages

Storm gives you the ability to experience the full version of Splunk without installing the software.

Disadvantages

Storm is not commercial, so your traffic is limited. You can see it as a limited version of Splunk and help with new product testing without deployment. Recently , a new service called Splunk Cloud is dedicated to providing the full experience of Splunk SaaS.

Open-source analytics software

Logstash

Logstash is an open source tool for collecting and managing logs. It uses a few other open source resources: Use ElasticSearch to index and find data, use Kibana tabulation, and visualize. They banded together to form a powerful log management solution.

Advantages

As an open source solution, Logstash allows users to have greater customization space and is cheap. Logstash uses three mature open source components-all well maintained-to form a powerful, extensible package. Due to open source, installation and use and very convenient.

Disadvantages

Since Logstash is essentially a stack of three parts, you need to face three different products. This means that the expansion is also becoming complex. Logstash's filter is written in Ruby, Kibana is written in pure Javascript, and ElasticSearch has its own REST interface and JSON template.

When you turn to a product, you also need to deploy three different tools to the server, without a doubt adding complexity.

Graylog2

A recently emerged Nova--GL2, supported by MongoDB and ElasticSearch, is used to store and search log errors. It is dedicated to helping developers find and fix bugs in their programs.

In this regard, fluentd and Kafka are also focused on storing logs. See! We have so many choices!

Takipi for Logs

Although this article is not about TAKIPI, it has a feature that you might find relevant to the log.

For the log Analysis tool, the biggest drawback is that you have to have logs to analyze. From the perspective of the integrated development environment, if there is no exception report, or no error message data, you can not know where the problem, so that any tool in the world can not help you! The Debug is stuck here. :(

One of the advantages of TAKIPI is that you can skip log files and go to debug messages. This way you can see the actual source code and the variable of the error range. Learn more click here.

TAKIPI will report all exceptions and errors and tell you what went wrong, even if it was multithreaded or on multiple machines. Installs within 1 minutes, less than 2% of maintenance costs-deploy Taikipi.

Translation: importnew.com - Rai Shintao

Link: http://www.importnew.com/12383.html

http://www.open-open.com/news/view/286196

Seven log management tools for Java Programmers (GO)