Shulou(Shulou.com)06/03 Report--

A background introduction

System error exception management is a very important system module, which plays a very powerful role in our daily development, testing and online operation diagnosis. However, the traditional log system occurs when there is something wrong with the system, and engineers go backstage to look through the logs. The massive logs are unreadable to a certain extent, which brings a lot of useless work to the operation and maintenance of the system and troubleshooting errors. Is there a scheme that can automatically collect and classify the errors of the system and sort out the error information in the form of a report? Vicrab was born.

Brief introduction of two Vicrab

Vicrab log system is a very popular SAAS service framework for log monitoring and operation and maintenance. Vicrab mainly includes the following parts:

Vicrab admin: cloud-based saas service where users only need to sign up for an account and can easily manage and use their own application exceptions through simple configuration.

Vicrab SDK: the client program for vicrab. At present, the development team of vicrab has launched two client solutions of vicrab-sdk for java and vicrab-sdk for android, which can be integrated simply by introducing them into the project and configuring the log transfer path.

The introduction to Vicrab document:vicrab can be downloaded and used on github and on the official website.

3. Why use vicrab

At present, many companies adopt the traditional development model, and the front-end and back-end work is done by different engineers. In this development mode, maintaining a timely and complete error log system will greatly improve our work efficiency. In the traditional sense, the front-end engineer is in charge of the front-end, and the background developer is responsible for the background. When an exception occurs, everyone checks back or pushes forward from back to back, but the error log is scattered. And some errors can not be reproduced. I believe we all know that this method is difficult to ensure the timeliness of error repair, but will increase our communication costs. Vicrab provides us with a whole new way to track errors, so let's take a look at its advantages:

simplifies management, saas services, and management in a unified console.

integration is simple, and it takes only three simple steps to complete the integration without further changes.

high performance, asynchronous implementation based on the log system, good performance, no impact on the original system.

is cheap: the low cost of use is negligible to enterprises.

All these advantages explain why we use vicrab. Do you already have a strong interest in vicrab? Let's integrate and use vicrab in the Spring Boot project step by step. Let's start by preparing a Web project for Spring Boot.

Download vicrab

Vicrab integrates the system in the form of online warehouse, which is very convenient.

Official website address:

Https://www.vicrab.com

Online documentation:

Https://github.com/vicrab/vicrab-docs/blob/master/src/clients/java/modules/logback.md

Choose the right vicrab sdk

Select the appropriate sdk client for integration according to the implementation of your Syslog. Check out the help on the official website (https://github.com/vicrab/vicrab-docs/blob/master/src/clients/java/index.md). The following five kinds of SDK are currently available for everyone to use.

Android > > demo

java.util.logging > > demo

Log4j 1.x > > demo

Log4j 2.x > > demo

Logback > > demo

Android client is the best choice, it is the only one. The server of java will choose according to your log implementation, which can be divided into four forms: native util log,log4j1 and log4j2,logback. These forms are just different from the jar package introduced, and the other steps are the same.

Integration steps

Vicrab starts to provide support from java6.

1 create an account. Visit the official website and start to create http://vicrab.com.

When registering, you need to configure your project, select a development language, such as java, and enter project name, organization, and other information. Registration complete.

2 introduce sdk, which can be described in part 5, such as the log4j1 version

Using Maven:

Com.vicrab

Vicrab-log4j

1.1

If your project uses the springboot framework, you need to introduce another package to make the experience better.

Com.vicrab

Vicrab-spring-boot-starter

1.2

Using Gradle:

Compile 'com.vicrab:vicrab-log4j:1.1'

Using SBT:

LibraryDependencies + = "com.vicrab"% "vicrab-log4j"% "1.1"

3 configuration and use

Configure DSN and log files (the address of DSN can be provided in the console settings of vicrab, one for each user, independently). Log configuration supports both properties,xml formats. For more information, please see the online manual.

Dsn= https://94f35849a36ed14ded6539e0f5c86811@j.vicrab.com/17841

Seven integration cases

In this step we will prepare a basic Spring Boot project with the following structure

Write the LoggerTest.java class, and we implement an exception for testing.

Add dependencies:

Configure DSN and log4j

Run the test:

Console view error

Eight concluding remarks

This paper introduces the background and use of vicrab, as well as the integration of the project with log4j1. Through this article, we have a general understanding of vicrab, and there are many powerful functions to be explored and studied later. There will be more and more powerful functions to share with you in the future. Such as code positioning, AI code repair and so on. Please wait for it.

Nine reference materials

Online documentation:

Https://github.com/vicrab/vicrab-docs/blob/master/src/clients/java/index.md

Technical support email: support@vicrab.com

Https://vicrab.com/about?message=#

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.