Clear it all at once. For the messy, spring transaction extension mechanism

Programmer Xia ya 2021-08-08 21:54:54
clear once. messy spring transaction


I recommended him some distributed tracking frameworks ,skywalking,pinpoint. He read it and said , Perfect , But it's a bit expensive to build and implement . It's also about storage costs , The company's log service has been purchased by a third party . It's a bit of a hassle to connect . I'm afraid they don't agree with such a toss .

Nearly period of time , See such an open source framework in the open source community , Known as a lightweight log tracking artifact ,10 Minutes to connect , So I recommended it to my friends . After a few days , He told me that it was very appropriate for his pain point now , Now it's in production , The preliminary effect is that , Still very satisfied . It can position their logs and reduce the time cost .

Project features

Invited , So I'm going to analyze this framework . Give you an intuitive understanding .

This framework is called TLog, The project is hosted in Gitee On

gitee.com/dromara/TLo…

The main page looks like this , It's a thick dark system ...

I use it , To put it bluntly , Namely TLog Prefixes each line automatically , It's called a label . Tags are divided into system level tags and business type tags , Business label developers can customize . Draw a picture to make it easy to understand :

TLog Each line of log that is finally rendered , It's like the picture above . The system log , The information that can be displayed at present is 5 individual , Upstream information can let you know who called your system , link TraceId It is the only global link across microservices ID, Search for a Id, You can get the log of the same request in all systems . This one is still very fragrant !

About SpanId, The explanation on the official website is , This represents the position of this call in the whole call link tree , The specific demonstration borrows the picture of the official website , The explanation is quite clear :

Individual to SpanId The understanding is , This thing lets you know the hierarchy of the system in a call chain , If it's collected , Can pass spanId Generate a call link tree . I really hope TLog Can realize the display of this tree , Unfortunately, we still don't support .

“TLog The positioning of is to provide the simplest way to solve the problem of log tracking , It doesn't collect logs , There's no need for additional storage space , It just automatically tags your business log , Automatic generation TraceId A whole link through your microservice . And provide upstream and downstream node information . Suitable for small and medium-sized enterprises and companies that want to quickly solve the problem of log tracking .“

This is a repeat of the official website , In fact, when I was testing ,TLog The log provided is the log itself , In multi node micro Services , The logs are still scattered . It's just logically concatenated with the log to a certain extent . But at the same time ,TLog The document also suggests that , Use other schemes to do log collection . such as ELK, Alicloud log , Other paid log products and so on .TLog Just modifying the log , No new logs are generated . So docking with other log collection schemes , There is no problem at all , For companies that have linked log collection solutions , There's no need to change anything .

Supported logging framework

Every company uses a variety of log frameworks .TLog Claims to support the three main logging frameworks :log4j,log4j2,logback

In practice , Here 3 In a frame ,TLog They can also print out labels normally . Just in the process of access , The official access methods are 3 Kind of

Test it out ,javaagent It's not stable for some projects , Some complex projects will be ineffective . For the most stable log adaptation method , Tested the company's projects , It's really connected .

Access mode , Follow the documentation step by step .

Supported by RPC frame

Since it's log tracking across microservices , In terms of implementation, we should also focus on the common RPC Be supported .TLog Support Dubbo,SpringCloud,Dubbox Three commonly used RPC, That's a good point .

In practice , stay Spring cloud This piece of ,TLog Also supports the SpringCloud Of Gateway.

During the access process , Whatever it is RPC frame , stay springboot In the environment TLog It can also adapt automatically , You can assemble it automatically by introducing one . No additional configuration required . That's handy .

But in the native spring In the environment ( Not springboot), Still need xml The extra configuration of , But it's also relatively simple , The document also has special instructions .

Business tag

In addition to the labels given by the system , I find TLog Another feature is allowing developers to customize tags . Access is also very simple , for instance :

@TLogAspect({"str","user.name","user.userDetail.company","user.dddd"})
public void test(String str, User user){
log.info(" This is a custom expression tag ");
log.info(" This is the business log 1");
log.info(" This is the business log 2");
log.info(" This is the business log 3");
log.info(" This is the business log 4");
log.info(" This is the business log 5");
}

  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.
  • 9.

Just add a label to the method , So all the logs under this method , Including the following N A hierarchy , Will automatically add the label you defined

This function is in the layout and search of logs , You can add a lot of markers . This is great !

Even custom tags support logical processing of information , You can customize the class to handle this information

@TLogAspect(convert = CustomAspectLogConvert.class)
public void demo(Person person){
log.info(" Customize Convert Example ");
}

  • 1.
  • 2.
  • 3.
  • 4.

This specific effect , You can try . All in all, one tag can handle all custom tags .

Support for other scenarios

Parameters & Time consuming printing support :

Last

Do everything with your heart , Pay great attention to details . It looks insignificant 、 If the tedious work is done thoroughly, it will have unexpected value .
Of course, to become a technical bull, you also need a certain ideological pattern , Thought determines which direction you want to go in the future , I suggest reading more books on life planning , Learn more about the ideological pattern of celebrities , In the future, you will go further .

I've done a collation of more technical point mind maps , It covers the most popular Internet at present 99% Technical points , Here I share this map , And a set of interview system for golden nine and silver ten , Up to collection , Down to distributed microservices

How to obtain this set of high-quality information ?

Java Interview selection questions 、 Structure the actual document delivery gate : Get it free of charge here

版权声明
本文为[Programmer Xia ya]所创,转载请带上原文链接,感谢
https://javamana.com/2021/08/20210808215437461o.html

  1. 【计算机网络 12(1),尚学堂马士兵Java视频教程
  2. 【程序猿历程,史上最全的Java面试题集锦在这里
  3. 【程序猿历程(1),Javaweb视频教程百度云
  4. Notes on MySQL 45 lectures (1-7)
  5. [computer network 12 (1), Shang Xuetang Ma soldier java video tutorial
  6. The most complete collection of Java interview questions in history is here
  7. [process of program ape (1), JavaWeb video tutorial, baidu cloud
  8. Notes on MySQL 45 lectures (1-7)
  9. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  10. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  11. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  12. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  13. 【递归,Java传智播客笔记
  14. [recursion, Java intelligence podcast notes
  15. [adhere to painting for 386 days] the beginning of spring of 24 solar terms
  16. K8S系列第八篇(Service、EndPoints以及高可用kubeadm部署)
  17. K8s Series Part 8 (service, endpoints and high availability kubeadm deployment)
  18. 【重识 HTML (3),350道Java面试真题分享
  19. 【重识 HTML (2),Java并发编程必会的多线程你竟然还不会
  20. 【重识 HTML (1),二本Java小菜鸟4面字节跳动被秒成渣渣
  21. [re recognize HTML (3) and share 350 real Java interview questions
  22. [re recognize HTML (2). Multithreading is a must for Java Concurrent Programming. How dare you not
  23. [re recognize HTML (1), two Java rookies' 4-sided bytes beat and become slag in seconds
  24. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  25. RPC 1: how to develop RPC framework from scratch
  26. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  27. RPC 1: how to develop RPC framework from scratch
  28. 一次性捋清楚吧,对乱糟糟的,Spring事务扩展机制
  29. 一文彻底弄懂如何选择抽象类还是接口,连续四年百度Java岗必问面试题
  30. Redis常用命令
  31. 一双拖鞋引发的血案,狂神说Java系列笔记
  32. 一、mysql基础安装
  33. 一位程序员的独白:尽管我一生坎坷,Java框架面试基础
  34. Clear it all at once. For the messy, spring transaction extension mechanism
  35. A thorough understanding of how to choose abstract classes or interfaces, baidu Java post must ask interview questions for four consecutive years
  36. Redis common commands
  37. A pair of slippers triggered the murder, crazy God said java series notes
  38. 1、 MySQL basic installation
  39. Monologue of a programmer: despite my ups and downs in my life, Java framework is the foundation of interview
  40. 【大厂面试】三面三问Spring循环依赖,请一定要把这篇看完(建议收藏)
  41. 一线互联网企业中,springboot入门项目
  42. 一篇文带你入门SSM框架Spring开发,帮你快速拿Offer
  43. 【面试资料】Java全集、微服务、大数据、数据结构与算法、机器学习知识最全总结,283页pdf
  44. 【leetcode刷题】24.数组中重复的数字——Java版
  45. 【leetcode刷题】23.对称二叉树——Java版
  46. 【leetcode刷题】22.二叉树的中序遍历——Java版
  47. 【leetcode刷题】21.三数之和——Java版
  48. 【leetcode刷题】20.最长回文子串——Java版
  49. 【leetcode刷题】19.回文链表——Java版
  50. 【leetcode刷题】18.反转链表——Java版
  51. 【leetcode刷题】17.相交链表——Java&python版
  52. 【leetcode刷题】16.环形链表——Java版
  53. 【leetcode刷题】15.汉明距离——Java版
  54. 【leetcode刷题】14.找到所有数组中消失的数字——Java版
  55. 【leetcode刷题】13.比特位计数——Java版
  56. oracle控制用户权限命令
  57. 三年Java开发,继阿里,鲁班二期Java架构师
  58. Oracle必须要启动的服务
  59. 万字长文!深入剖析HashMap,Java基础笔试题大全带答案
  60. 一问Kafka就心慌?我却凭着这份,图灵学院vip课程百度云