A lightweight distributed log tag tracker

A lightweight distributed log tag tracker

2022-09-02 0 907
Resource Number 38026 Last Updated 2025-02-24
¥ 0USD Upgrade VIP
Download Now Matters needing attention
Can't download? Please contact customer service to submit a link error!
Value-added Service: Installation Guide Environment Configuration Secondary Development Template Modification Source Code Installation

The TLog recommended in this issue is a lightweight distributed log tag tracking artifact, which can be connected in 10 minutes and automatically tag logs to complete microservice link tracking. Support log4j, log4j2, logback three log frameworks, support dubbo, dubbox, springcloud three RPC frameworks.

A lightweight distributed log tag tracker插图

Introduction to TLog

1.TLog labels logs to trace enterprise-class microservices. It does not collect logs, is simple to use, and produces globally unique tracking codes. In addition to tracking codes, TLog also supports the addition of SpanId and upstream and downstream service information tags.

2.Designed for user convenience, it provides a completely zero-intrusion access mode, automatically probes the RPC framework and log framework used in the project, and performs bytecode injection to complete the addition of system-level log labels.

3.TLog ADAPTS to the mainstream RPC frameworks on the market: dubbo, dubbox, spring cloud’s open feign.

4.TLog provides Javaagent, bytecode injection, and log framework to adapt to three access modes, which ensure no performance loss. Supports uninterrupted tracing in service asynchronous threads, thread pools, and log asynchronous output scenarios.

Project characteristics

1.Lightweight microservice log tracing by labeling logs

2.Three access modes are provided: javaagent completely non-intrusive access, bytecode one-line access, and configuration file based access

3.Support common log4j, log4j2, logback three log frameworks, and provide automatic detection, complete adaptation

4.Supports Spring Cloud Gateway and Soul Gateway

5.http call label passing for HttpClient and Okhttp

6.Support for three task frameworks, JDK TimerTask, Quartz, XXL-JOB

7.Supports the configuration of a custom log label template, and provides multiple options for system-level buried point labels

8.Supports asynchronous thread tracing, including thread pools, multi-level asynchronous threads and other scenarios

9.Almost no performance loss, fast and stable, after pressure test, the loss is 0.01%

Installing TLog

TLog provides two different dependencies on springboot and spring native, which rely on only one package and pass in the required packages.

springboot dependency

<dependency>
  <groupId>com.yomahub</groupId>
  <artifactId>tlog-all-spring-boot-starter</artifactId>
  <version>1.3.4</version>
</dependency>

spring native dependency

<dependency>
  <groupId>com.yomahub</groupId>
  <artifactId>tlog-all</artifactId>
  <version>1.3.4</version>
</dependency>

Log framework adaptation (example Log4j framework adapter)

Synchronous logging: Just change the layout implementation class

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration>
    <appender name="stdout" class="org.apache.log4j.ConsoleAppender">
        <!--change for AspectLog4jPatternLayout-->
        <layout class="com.yomahub.tlog.core.enhance.log4j.AspectLog4jPatternLayout">
            <param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss,SSS} [%p] %m  >> %c:%L%n"/>
        </layout>
    </appender>
    <appender name="fileout" class="org.apache.log4j.DailyRollingFileAppender">
        <param name="File" value="./logs/test.log"/>
        <!--change for AspectLog4jPatternLayout-->
        <layout class="com.yomahub.tlog.core.enhance.log4j.AspectLog4jPatternLayout">
            <param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss,SSS} [%p] %m  >> %c:%L%n"/>
        </layout>
    </appender>
    <root>
        <priority value="info" />
        <appender-ref ref="stdout"/>
        <appender-ref ref="fileout"/>
    </root>
</log4j:configuration>

Asynchronous logging: Just replace the implementation class of the appender

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration>
    <appender name="stdout" class="org.apache.log4j.ConsoleAppender">
        <layout class="org.apache.log4j.PatternLayout">
            <param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss,SSS} [%p] %m  >> %c:%L%n"/>
        </layout>
    </appender>
    <appender name="fileout" class="org.apache.log4j.DailyRollingFileAppender">
        <param name="File" value="./logs/log4j-dubbo-provider.log"/>
        <layout class="org.apache.log4j.PatternLayout">
            <param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss,SSS} [%p] %m  >> %c:%L%n"/>
        </layout>
    </appender>

    <!--Replace here with AspectLog4jAsyncAppender-->
    <appender name="asyncFileout" class="com.yomahub.tlog.core.enhance.log4j.async.AspectLog4jAsyncAppender">
        <appender-ref ref="fileout"/>
    </appender>

    <root>
        <priority value="info" />
        <appender-ref ref="stdout"/>
        <appender-ref ref="asyncFileout"/>
    </root>
</log4j:configuration>

Task framework support (example XXL-JOB framework)

Starting with version 1.3.0, TLog supports the open source framework XXL-JOB.

In the springboot environment, you don’t need to make any changes. You only need to introduce a dependency package to take effect.

In the spring native environment, you need to configure an extra line

<bean class="com.yomahub.tlog.springboot.lifecircle.TLogXxljobEnhanceInit"/>

TLog architecture diagram

A lightweight distributed log tag tracker插图1
资源下载此资源为免费资源立即下载
Telegram:@John_Software

Disclaimer: This article is published by a third party and represents the views of the author only and has nothing to do with this website. This site does not make any guarantee or commitment to the authenticity, completeness and timeliness of this article and all or part of its content, please readers for reference only, and please verify the relevant content. The publication or republication of articles by this website for the purpose of conveying more information does not mean that it endorses its views or confirms its description, nor does it mean that this website is responsible for its authenticity.

Ictcoder Free source code A lightweight distributed log tag tracker https://ictcoder.com/kyym/a-lightweight-distributed-log-tag-tracker.html

Share free open-source source code

Q&A
  • 1, automatic: after taking the photo, click the (download) link to download; 2. Manual: After taking the photo, contact the seller to issue it or contact the official to find the developer to ship.
View details
  • 1, the default transaction cycle of the source code: manual delivery of goods for 1-3 days, and the user payment amount will enter the platform guarantee until the completion of the transaction or 3-7 days can be issued, in case of disputes indefinitely extend the collection amount until the dispute is resolved or refunded!
View details
  • 1. Heptalon will permanently archive the process of trading between the two parties and the snapshots of the traded goods to ensure that the transaction is true, effective and safe! 2, Seven PAWS can not guarantee such as "permanent package update", "permanent technical support" and other similar transactions after the merchant commitment, please identify the buyer; 3, in the source code at the same time there is a website demonstration and picture demonstration, and the site is inconsistent with the diagram, the default according to the diagram as the dispute evaluation basis (except for special statements or agreement); 4, in the absence of "no legitimate basis for refund", the commodity written "once sold, no support for refund" and other similar statements, shall be deemed invalid; 5, before the shooting, the transaction content agreed by the two parties on QQ can also be the basis for dispute judgment (agreement and description of the conflict, the agreement shall prevail); 6, because the chat record can be used as the basis for dispute judgment, so when the two sides contact, only communicate with the other party on the QQ and mobile phone number left on the systemhere, in case the other party does not recognize self-commitment. 7, although the probability of disputes is very small, but be sure to retain such important information as chat records, mobile phone messages, etc., in case of disputes, it is convenient for seven PAWS to intervene in rapid processing.
View details
  • 1. As a third-party intermediary platform, Qichou protects the security of the transaction and the rights and interests of both buyers and sellers according to the transaction contract (commodity description, content agreed before the transaction); 2, non-platform online trading projects, any consequences have nothing to do with mutual site; No matter the seller for any reason to require offline transactions, please contact the management report.
View details

Related Article

make a comment
No comments available at the moment
Official customer service team

To solve your worries - 24 hours online professional service