CN107818024A - A kind of request ID transmission methods and system based on spring blockers - Google Patents

A kind of request ID transmission methods and system based on spring blockers Download PDF

Info

Publication number
CN107818024A
CN107818024A CN201711171790.XA CN201711171790A CN107818024A CN 107818024 A CN107818024 A CN 107818024A CN 201711171790 A CN201711171790 A CN 201711171790A CN 107818024 A CN107818024 A CN 107818024A
Authority
CN
China
Prior art keywords
request
blockers
spring
user
dubbo
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201711171790.XA
Other languages
Chinese (zh)
Inventor
刘俊艳
张振
沈桐
阎志军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
State Grid Agel Ecommerce Ltd
BEIJING HUITONG JINCAI INFORMATION TECHNOLOGY Co Ltd
State Grid Corp of China SGCC
Original Assignee
State Grid Agel Ecommerce Ltd
BEIJING HUITONG JINCAI INFORMATION TECHNOLOGY Co Ltd
State Grid Corp of China SGCC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by State Grid Agel Ecommerce Ltd, BEIJING HUITONG JINCAI INFORMATION TECHNOLOGY Co Ltd, State Grid Corp of China SGCC filed Critical State Grid Agel Ecommerce Ltd
Priority to CN201711171790.XA priority Critical patent/CN107818024A/en
Publication of CN107818024A publication Critical patent/CN107818024A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention provides a kind of request ID transmission methods based on spring blockers, including:Receive the request that user is sent by application terminal;Request is intercepted and captured based on integrated spring blockers in the application, based on request generation log chain unique request mark request ID;Request ID are put into threadlocal threads;Spring blockers obtain the recalls information of user's request;At the end of user's request call, srping blockers obtain request call ending message, and the log information for being identified with request ID is printed in daily record.The present invention for each application by unifying configuring request blocker, for generating unique request ID and collecting solicited message, the call chain daily record details entirely asked can be inquired by request ID, inquiry and statistical efficiency are improved, it is very convenient quick for investigation exception, fast positioning.The invention also discloses a kind of request ID transmission systems based on spring blockers.

Description

A kind of request ID transmission methods and system based on spring blockers
Technical field
The invention belongs to technical field of software engineering, more particularly to a kind of request ID based on spring blockers to pass Pass method and system.
Background technology
The complexity for expanding increasingly due to the scale of software systems and thus bringing, can produce substantial amounts of log information, this A little daily records needs are stored in case inquiring about and analyzing, and traditional relational database is stored to daily record, inquired about, the ability of analysis has Limit.For example, log information is generally stored sequentially in time, a request can form a plurality of day in processing procedure is responded Will information, the log information of difference request mixes storage in database, in the case where log information amount is very huge, to day When will file is analyzed, it is difficult to isolate log information caused by some specific request.
Therefore, how effectively daily record to be managed is a urgent problem to be solved.
The content of the invention
In view of this, the invention provides a kind of request ID transmission methods and system based on spring blockers, , can for generating unique request ID and collecting solicited message by unifying configuring request blocker for each application The call chain daily record details entirely asked are inquired by request ID, improve inquiry and statistical efficiency, it is different for investigating Often, fast positioning is very convenient quick.
To achieve these goals, the present invention provides following technical scheme:
A kind of request ID transmission methods based on spring blockers, including:
Receive the request that user is sent by application terminal;
The request is intercepted and captured based on integrated spring blockers in the application;
Based on the request generation log chain unique request mark request ID;
The request ID are put into threadlocal threads;
The spring blockers obtain the recalls information of user's request;
At the end of user's request call, the srping blockers obtain request call ending message, will be identified with Request ID log information is printed in daily record.
Preferably, the spring blockers obtain the recalls information that user asks and included:
When application integration during dubbo, request ID are passed to dubbo filters, while obtain dubbo recalls informations.
Preferably, the spring blockers obtain the recalls information that user asks and also included:
When application integration during Sql DruID connection pools, request ID are passed to druID filters, while obtain sql's Recalls information.
Preferably, the dubbo recalls informations include:Dubbo Service names, method name, allocating time and call parameters.
Preferably, the recalls information of the sql includes:
Sql sentences, parameter and execution time.
A kind of request ID transmission systems based on spring blockers, including:
Receiving module, the request sent for receiving user by application terminal;
Interception module, for intercepting and capturing the request based on integrated spring blockers in the application;
Generation module, for based on the request generation log chain unique request mark request ID;
Storage module, for the request ID to be put into threadlocal threads;
Acquisition module, the recalls information of user's request is obtained for the spring blockers;
Print module, for user's request call at the end of, the srping blockers obtain request call ending message, The log information for being identified with request ID is printed in daily record.
Preferably, the acquisition module is used for:
When application integration during dubbo, request ID are passed to dubbo filters, while obtain dubbo recalls informations.
Preferably, the acquisition module is additionally operable to:
When application integration during Sql DruID connection pools, request ID are passed to druID filters, while obtain sql's Recalls information.
Preferably, the dubbo recalls informations include:Dubbo Service names, method name, allocating time and call parameters.
Preferably, the recalls information of the sql includes:
Sql sentences, parameter and execution time.
It can be seen from the above technical proposal that the invention provides a kind of request ID biographies based on spring blockers Method is passed, receives the request that user is sent by application terminal first, is then based on integrated spring blockers in the application Request is intercepted and captured, based on request generation log chain unique request mark request ID, request ID are put into In threadlocal threads, spring blockers obtain the recalls information of user's request, at the end of user's request call, Srping blockers obtain request call ending message, and the log information for being identified with request ID is printed in daily record.This Invention for each application by unifying configuring request blocker, for generating unique request ID and collecting solicited message, The call chain daily record details entirely asked can be inquired by request ID, improve inquiry and statistical efficiency, for row It is very convenient quick to look into exception, fast positioning.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, drawings in the following description are only this Some embodiments of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can be with Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 is a kind of side of the request ID transmission methods embodiment 1 based on spring blockers disclosed by the invention Method flow chart;
Fig. 2 is a kind of side of the request ID transmission methods embodiment 2 based on spring blockers disclosed by the invention Method flow chart;
Fig. 3 is a kind of knot of the request ID transmission systems embodiment 1 based on spring blockers disclosed by the invention Structure schematic diagram;
Fig. 4 is a kind of knot of the request ID transmission systems embodiment 2 based on spring blockers disclosed by the invention Structure schematic diagram.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, rather than whole embodiments.It is based on Embodiment in the present invention, those of ordinary skill in the art are obtained every other under the premise of creative work is not made Embodiment, belong to the scope of protection of the invention.
As shown in figure 1, implement for a kind of request ID transmission methods based on spring blockers disclosed by the invention The flow chart of example 1, methods described include:
S101, receive the request that user is sent by application terminal;
When being managed to daily record, it is necessary to generate request ID, when generating request ID, user passes through first Application terminal sends request, then receives the request that user is sent by application terminal.
S102, intercepted and captured and asked based on integrated spring blockers in the application;
The Spring blockers due to application integration, initially enter spring blockers, Spring when there is request to come Blocker is intercepted and captured to the request that user sends.
S103, log chain unique request mark request ID are generated based on request;
After request is intercepted, the unique request ID of log chain are generated according to the request of intercepting and capturing.
S104, request ID are put into threadlocal threads;
Then the request ID of generation are put into threadlocal threads.
S105, spring blocker obtain the recalls information of user's request;
Then spring blockers obtain the recalls information of user's request, wherein, recalls information includes application name, method name Deng.
At the end of S106, user's request call, srping blockers obtain request call ending message, will be identified with Request ID log information is printed in daily record.
After user's request terminates, srping blockers are re-introduced into, while request ID can be also passed into, so It is time-consuming by what is entirely asked afterwards, if to there are the information such as calling exception to print in daily record, whole user's request call terminates, and owns Daily record has all been printed in journal file.
In summary, in the above-described embodiments, the request that user is sent by application terminal is received first, is then based on collecting Request is intercepted and captured into spring blockers in the application, will based on request generation log chain unique request mark request ID Request ID are put into threadlocal threads, and spring blockers obtain the recalls information of user's request, user's request At the end of calling, srping blockers obtain request call ending message, and the log information for being identified with request ID is printed Into daily record.The present invention for each application by unifying configuring request blocker, for generating unique request ID and receipts Collect solicited message, the call chain daily record details entirely asked can be inquired by request ID, improve inquiry and statistics Efficiency is very convenient quick for investigation exception, fast positioning.
As shown in Fig. 2 implement for a kind of request ID transmission methods based on spring blockers disclosed by the invention The flow chart of example 2, methods described include:
S201, receive the request that user is sent by application terminal;
When being managed to daily record, it is necessary to generate request ID, when generating request ID, user passes through first Application terminal sends request, then receives the request that user is sent by application terminal.
S202, intercepted and captured and asked based on integrated spring blockers in the application;
The Spring blockers due to application integration, initially enter spring blockers, Spring when there is request to come Blocker is intercepted and captured to the request that user sends.
S203, log chain unique request mark request ID are generated based on request;
After request is intercepted, the unique request ID of log chain are generated according to the request of intercepting and capturing.
S204, request ID are put into threadlocal threads;
Then the request ID of generation are put into threadlocal threads.
S205, when application integration during dubbo, request ID are passed to dubbo filters, while obtain dubbo calling Information, when application integration during Sql DruID connection pools, request ID are passed to druID filters, while obtain sql tune Use information;
Then spring blockers obtain the recalls information of user's request.If application integration dubbo, requestID Incoming dubbo filters, while dubbo filters can obtain dubbo recalls informations, wherein, dubbo recalls informations can include Dubbo Service names, method name, allocating time, call parameters etc..
If application integration Sql DruID connection pools, requestID are passed to druID filters, while druID mistakes Filter can obtain sql recalls information, wherein, sql recalls information can include sql sentences, parameter, perform time etc..
At the end of S206, user's request call, srping blockers obtain request call ending message, will be identified with Request ID log information is printed in daily record.
After user's request terminates, srping blockers are re-introduced into, while request ID can be also passed into, so It is time-consuming by what is entirely asked afterwards, if to there are the information such as calling exception to print in daily record, whole user's request call terminates, and owns Daily record has all been printed in journal file.
In summary, in the above-described embodiments, the request that user is sent by application terminal is received first, is then based on collecting Request is intercepted and captured into spring blockers in the application, will based on request generation log chain unique request mark request ID Request ID are put into threadlocal threads, and when application integration during dubbo, request ID are passed to dubbo mistakes Filter, while obtain dubbo recalls informations, when application integration during Sql DruID connection pools, request ID are passed to druID Filter, while sql recalls information is obtained, at the end of user's request call, srping blockers, which obtain request call, to be terminated Information, the log information for being identified with request ID is printed in daily record.The log system disposed compared to conventional elk, It is that each application is uniformly configured with Request Interceptor in design, for generating unique RequestID and collecting solicited message etc., The call chain daily record details entirely asked can be inquired by RequestID, it is very convenient fast for investigation exception, fast positioning It is prompt.
It should be noted that in the above-described embodiments, after based on spring blockers generation request ID, one can be entered The request ID that step generates the blocker configured in the respective applications, and the recalls information for the application collected and user's letter Breath output is into daily record;Under distributed scene, the log information of each application on each application server is gathered;Answered each Log information unique caching is in the name that Key is logstash;Pull log information, carry out from initial data to The conversion of data format required by ElasticSearch search servers;Keyword is captured from log information, based on key Corresponding log information is stored in ElasticSearch search servers by word.
Specifically, when needing to be managed daily record, unify configuring request blocker for each application first, work as interception During to http request, blocker firstly generates request ID, while collects the recalls information and some user profile of application, The request ID and the encryption of the recalls information and user profile of the application of collection are output in daily record.Wherein, Request ID generation is to form call chain between each application daily record, and request every time can all generate unique Request ID, in the case where daily record amount is very huge, aim at the day with Request ID investigating failure, inquiry user asks institute every time Caused daily record is very convenient, quick.
Then, under distributed scene, a log acquisition module is both increased on each application server, passes through daily record Acquisition module collects the log information of each application on server.
After the log information of each application is collected, the log information unique caching of each application collected is existed Key is in logstash name.
Then, log information is pulled, is carried out from the data required by initial data to ElasticSearch search servers The conversion of form, for example, date format is converted to predefined form, the removal of some fields, the merging conversion of field, Message information json parsings etc., ip locations are obtained also by GeoIP, according to system customization filter condition, canonical parsing Deng.
Keyword is captured from log information, judges be written in ElasticSearch which index, and By information be stored in corresponding to index, complete by log information be stored in ElasticSearch search servers.Daily record is stored in In ElasticSearch, same ElasticSearch is also to be disposed using trunking mode, passes through cluster.name To define cluster name.ElasticSearch clustered nodes are divided into two types:master node、data node.Master node:The management node of cluster, major function are to safeguard metadata, manage the state of each node of cluster.Data node:It is negative Blame storage, inquiry and the importing of data.
As shown in figure 3, implement for a kind of request ID transmission systems based on spring blockers disclosed by the invention The structural representation of example 1, the system include:
Receiving module 301, the request sent for receiving user by application terminal;
When being managed to daily record, it is necessary to generate request ID, when generating request ID, user passes through first Application terminal sends request, then receives the request that user is sent by application terminal.
Interception module 302, for intercepting and capturing request based on integrated spring blockers in the application;
The Spring blockers due to application integration, initially enter spring blockers, Spring when there is request to come Blocker is intercepted and captured to the request that user sends.
Generation module 303, for based on request generation log chain unique request mark request ID;
After request is intercepted, the unique request ID of log chain are generated according to the request of intercepting and capturing.
Storage module 304, for request ID to be put into threadlocal threads;
Then the request ID of generation are put into threadlocal threads.
Acquisition module 305, the recalls information of user's request is obtained for spring blockers;
Then spring blockers obtain the recalls information of user's request, wherein, recalls information includes application name, method name Deng.
Print module 306, at the end of user's request call, srping blockers obtain request call ending message, The log information for being identified with request ID is printed in daily record.
After user's request terminates, srping blockers are re-introduced into, while request ID can be also passed into, so It is time-consuming by what is entirely asked afterwards, if to there are the information such as calling exception to print in daily record, whole user's request call terminates, and owns Daily record has all been printed in journal file.
In summary, in the above-described embodiments, the request that user is sent by application terminal is received first, is then based on collecting Request is intercepted and captured into spring blockers in the application, will based on request generation log chain unique request mark request ID Request ID are put into threadlocal threads, and spring blockers obtain the recalls information of user's request, user's request At the end of calling, srping blockers obtain request call ending message, and the log information for being identified with request ID is printed Into daily record.The present invention for each application by unifying configuring request blocker, for generating unique request ID and receipts Collect solicited message, the call chain daily record details entirely asked can be inquired by request ID, improve inquiry and statistics Efficiency is very convenient quick for investigation exception, fast positioning.
As shown in figure 4, implement for a kind of request ID transmission systems based on spring blockers disclosed by the invention The structural representation of example 2, the system include:
Receiving module 401, the request sent for receiving user by application terminal;
When being managed to daily record, it is necessary to generate request ID, when generating request ID, user passes through first Application terminal sends request, then receives the request that user is sent by application terminal.
Interception module 402, for intercepting and capturing request based on integrated spring blockers in the application;
The Spring blockers due to application integration, initially enter spring blockers, Spring when there is request to come Blocker is intercepted and captured to the request that user sends.
Generation module 403, for based on request generation log chain unique request mark request ID;
After request is intercepted, the unique request ID of log chain are generated according to the request of intercepting and capturing.
Storage module 404, for request ID to be put into threadlocal threads;
Then the request ID of generation are put into threadlocal threads.
Acquisition module 405, during for the dubbo when application integration, request ID are passed to dubbo filters, obtain simultaneously Dubbo recalls informations are taken, when application integration during Sql DruID connection pools, request ID are passed to druID filters, simultaneously Obtain sql recalls information;
Then spring blockers obtain the recalls information of user's request.If application integration dubbo, requestID Incoming dubbo filters, while dubbo filters can obtain dubbo recalls informations, wherein, dubbo recalls informations can include Dubbo Service names, method name, allocating time, call parameters etc..
If application integration Sql DruID connection pools, requestID are passed to druID filters, while druID mistakes Filter can obtain sql recalls information, wherein, sql recalls information can include sql sentences, parameter, perform time etc..
Print module 406, at the end of user's request call, srping blockers obtain request call ending message, The log information for being identified with request ID is printed in daily record.
After user's request terminates, srping blockers are re-introduced into, while request ID can be also passed into, so It is time-consuming by what is entirely asked afterwards, if to there are the information such as calling exception to print in daily record, whole user's request call terminates, and owns Daily record has all been printed in journal file.
In summary, in the above-described embodiments, the request that user is sent by application terminal is received first, is then based on collecting Request is intercepted and captured into spring blockers in the application, will based on request generation log chain unique request mark request ID Request ID are put into threadlocal threads, and when application integration during dubbo, request ID are passed to dubbo mistakes Filter, while obtain dubbo recalls informations, when application integration during Sql DruID connection pools, request ID are passed to druID Filter, while sql recalls information is obtained, at the end of user's request call, srping blockers, which obtain request call, to be terminated Information, the log information for being identified with request ID is printed in daily record.The log system disposed compared to conventional elk, It is that each application is uniformly configured with Request Interceptor in design, for generating unique RequestID and collecting solicited message etc., The call chain daily record details entirely asked can be inquired by RequestID, it is very convenient fast for investigation exception, fast positioning It is prompt.
In order to more specifically emphasize the independence implemented, this specification is related to number of modules or unit.For example, mould Block or unit can be realized that the hardware circuit includes special VLSI circuits OR gate array, such as logic chip, crystal by hardware circuit Pipe, or other components.Module or unit can also be realized in programmable computer hardware, for example field is imitated programmable gate array, can compiled Journey array logic, programmable logic device etc..
Module or unit can also be realized in by the software performed by various forms of processors.Such as one can hold Row code module may include one or more entities or logic computer instruction block, and the block is formed into, such as, Object, program or function.However, the executable part of identification module or unit need not physically be put together, but can be by The different instruction for being stored in diverse location is formed, and when combining in logic, is formed module or unit and is reached the module Or the purpose required by unit.
In fact, executable code module or unit can be a single instruction or multiple instruction, it might even be possible to which distribution is in place In several different code sections of different programs, and across several storage devices.Similarly, operation data can be identified and It is shown in this module or unit, and can implements in any suitable form and any suitably in data structure form Tissue.Operation data can assemble single data set, or can be distributed in the different positions with different storage devices, and Only it is present in a system or network in a manner of electronic signal at least in part.
" embodiment " or similar term mentioned by this specification represent characteristic, structure or the feature relevant with embodiment, It is included at least embodiment of the present invention.Therefore, this specification occurs term " in one embodiment ", " implementing In example " and similar to term possibility but it is not necessarily all the identical embodiment of sensing.
Furthermore characteristic of the present invention, structure or feature can combine in one or more embodiments in any way. Explanation will provide many specific details below, for example programming, software module, user's selection, network trading, database are looked into The examples such as inquiry, database structure, hardware module, hardware circuit, hardware chip, to provide the understanding to the embodiment of the present invention.So And those of ordinary skill in the related art will be seen that the present invention, though wherein one or more specific details are not utilized, or profit It can also be implemented with other methods, component, material etc..On the other hand, it is the present invention that avoids confusion, known structure, material or behaviour Do not have a detailed description.
Each embodiment is described by the way of progressive in this specification, what each embodiment stressed be and other The difference of embodiment, between each embodiment identical similar portion mutually referring to.For device disclosed in embodiment For, because it is corresponded to the method disclosed in Example, so description is fairly simple, related part is said referring to method part It is bright.
Professional further appreciates that, with reference to the unit of each example of the embodiments described herein description And algorithm steps, can be realized with electronic hardware, computer software or the combination of the two, in order to clearly demonstrate hardware and The interchangeability of software, the composition and step of each example are generally described according to function in the above description.These Function is performed with hardware or software mode actually, application-specific and design constraint depending on technical scheme.Specialty Technical staff can realize described function using distinct methods to each specific application, but this realization should not Think beyond the scope of this invention.
Directly it can be held with reference to the step of method or algorithm that the embodiments described herein describes with hardware, processor Capable software module, or the two combination are implemented.Software module can be placed in random access memory (RAM), internal memory, read-only deposit Reservoir (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technology In any other form of storage medium well known in field.
The foregoing description of the disclosed embodiments, professional and technical personnel in the field are enable to realize or using the present invention. A variety of modifications to these embodiments will be apparent for those skilled in the art, as defined herein General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, it is of the invention The embodiments shown herein is not intended to be limited to, and is to fit to and principles disclosed herein and features of novelty phase one The most wide scope caused.

Claims (10)

  1. A kind of 1. request ID transmission methods based on spring blockers, it is characterised in that including:
    Receive the request that user is sent by application terminal;
    The request is intercepted and captured based on integrated spring blockers in the application;
    Based on the request generation log chain unique request mark request ID;
    The request ID are put into threadlocal threads;
    The spring blockers obtain the recalls information of user's request;
    At the end of user's request call, the srping blockers obtain request call ending message, will be identified with request ID log information is printed in daily record.
  2. 2. according to the method for claim 1, it is characterised in that the spring blockers obtain the calling letter of user's request Breath includes:
    When application integration during dubbo, request ID are passed to dubbo filters, while obtain dubbo recalls informations.
  3. 3. according to the method for claim 2, it is characterised in that the spring blockers obtain the calling letter of user's request Breath also includes:
    When application integration during Sql DruID connection pools, request ID are passed to druID filters, while obtain sql calling Information.
  4. 4. according to the method for claim 3, it is characterised in that the dubbo recalls informations include:Dubbo Service names, side Religious name, allocating time and call parameters.
  5. 5. according to the method for claim 4, it is characterised in that the recalls information of the sql includes:
    Sql sentences, parameter and execution time.
  6. A kind of 6. request ID transmission systems based on spring blockers, it is characterised in that including:
    Receiving module, the request sent for receiving user by application terminal;
    Interception module, for intercepting and capturing the request based on integrated spring blockers in the application;
    Generation module, for based on the request generation log chain unique request mark request ID;
    Storage module, for the request ID to be put into threadlocal threads;
    Acquisition module, the recalls information of user's request is obtained for the spring blockers;
    Print module, for user's request call at the end of, the srping blockers obtain request call ending message, will mark The log information that knowing has request ID is printed in daily record.
  7. 7. system according to claim 6, it is characterised in that the acquisition module is used for:
    When application integration during dubbo, request ID are passed to dubbo filters, while obtain dubbo recalls informations.
  8. 8. system according to claim 7, it is characterised in that the acquisition module is additionally operable to:
    When application integration during Sql DruID connection pools, request ID are passed to druID filters, while obtain sql calling Information.
  9. 9. system according to claim 8, it is characterised in that the dubbo recalls informations include:Dubbo Service names, side Religious name, allocating time and call parameters.
  10. 10. system according to claim 9, it is characterised in that the recalls information of the sql includes:
    Sql sentences, parameter and execution time.
CN201711171790.XA 2017-11-22 2017-11-22 A kind of request ID transmission methods and system based on spring blockers Pending CN107818024A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711171790.XA CN107818024A (en) 2017-11-22 2017-11-22 A kind of request ID transmission methods and system based on spring blockers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711171790.XA CN107818024A (en) 2017-11-22 2017-11-22 A kind of request ID transmission methods and system based on spring blockers

Publications (1)

Publication Number Publication Date
CN107818024A true CN107818024A (en) 2018-03-20

Family

ID=61610379

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711171790.XA Pending CN107818024A (en) 2017-11-22 2017-11-22 A kind of request ID transmission methods and system based on spring blockers

Country Status (1)

Country Link
CN (1) CN107818024A (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109271359A (en) * 2018-11-20 2019-01-25 北京千丁互联科技有限公司 Log information processing method, device, electronic equipment and readable storage medium storing program for executing
CN109739735A (en) * 2018-12-04 2019-05-10 东软集团股份有限公司 Log generation method and device
CN110263129A (en) * 2019-06-25 2019-09-20 四川长虹电器股份有限公司 The method for carrying out slow inquiry operation statistics based on Mybatis frame
CN110609680A (en) * 2019-09-19 2019-12-24 北京锐安科技有限公司 Parameter transmission method and device based on Spring interceptor, storage medium and equipment
WO2020000722A1 (en) * 2018-06-30 2020-01-02 平安科技(深圳)有限公司 Method and apparatus for saving server log
WO2020010702A1 (en) * 2018-07-11 2020-01-16 平安科技(深圳)有限公司 Log search method and system, computer device, and storage medium
CN110825425A (en) * 2018-08-09 2020-02-21 北京京东尚科信息技术有限公司 Configuration data management method and device, electronic equipment and storage medium
CN111177599A (en) * 2019-12-26 2020-05-19 紫光云(南京)数字技术有限公司 Cross-system link tracking method based on tangent plane
CN111258512A (en) * 2020-01-13 2020-06-09 无线生活(北京)信息技术有限公司 Method and device for printing interface log based on interception
CN111339507A (en) * 2020-02-24 2020-06-26 杭州数梦工场科技有限公司 Method, system, equipment and readable storage medium for processing access request
CN112286778A (en) * 2020-12-25 2021-01-29 国网汇通金财(北京)信息科技有限公司 Service chain call analysis method and device
CN112783451A (en) * 2021-01-22 2021-05-11 中信银行股份有限公司 Time-consuming abnormity analysis method and system based on interceptor and storage medium
CN113238722A (en) * 2021-05-17 2021-08-10 上海中通吉网络技术有限公司 Log printing method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105224445A (en) * 2015-10-28 2016-01-06 北京汇商融通信息技术有限公司 Distributed tracking system
CN106487596A (en) * 2016-10-26 2017-03-08 宜人恒业科技发展(北京)有限公司 Distributed Services follow the tracks of implementation method
CN106502874A (en) * 2016-10-26 2017-03-15 南京途牛科技有限公司 A kind of call chain tracking
CN107295077A (en) * 2017-06-16 2017-10-24 深圳易嘉恩科技有限公司 Distributed cloud platform system based on micro services framework

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105224445A (en) * 2015-10-28 2016-01-06 北京汇商融通信息技术有限公司 Distributed tracking system
CN106487596A (en) * 2016-10-26 2017-03-08 宜人恒业科技发展(北京)有限公司 Distributed Services follow the tracks of implementation method
CN106502874A (en) * 2016-10-26 2017-03-15 南京途牛科技有限公司 A kind of call chain tracking
CN107295077A (en) * 2017-06-16 2017-10-24 深圳易嘉恩科技有限公司 Distributed cloud platform system based on micro services framework

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020000722A1 (en) * 2018-06-30 2020-01-02 平安科技(深圳)有限公司 Method and apparatus for saving server log
WO2020010702A1 (en) * 2018-07-11 2020-01-16 平安科技(深圳)有限公司 Log search method and system, computer device, and storage medium
CN110825425A (en) * 2018-08-09 2020-02-21 北京京东尚科信息技术有限公司 Configuration data management method and device, electronic equipment and storage medium
CN109271359A (en) * 2018-11-20 2019-01-25 北京千丁互联科技有限公司 Log information processing method, device, electronic equipment and readable storage medium storing program for executing
CN109739735B (en) * 2018-12-04 2022-05-31 东软集团股份有限公司 Log generation method and device
CN109739735A (en) * 2018-12-04 2019-05-10 东软集团股份有限公司 Log generation method and device
CN110263129A (en) * 2019-06-25 2019-09-20 四川长虹电器股份有限公司 The method for carrying out slow inquiry operation statistics based on Mybatis frame
CN110609680A (en) * 2019-09-19 2019-12-24 北京锐安科技有限公司 Parameter transmission method and device based on Spring interceptor, storage medium and equipment
CN111177599A (en) * 2019-12-26 2020-05-19 紫光云(南京)数字技术有限公司 Cross-system link tracking method based on tangent plane
CN111258512A (en) * 2020-01-13 2020-06-09 无线生活(北京)信息技术有限公司 Method and device for printing interface log based on interception
CN111339507A (en) * 2020-02-24 2020-06-26 杭州数梦工场科技有限公司 Method, system, equipment and readable storage medium for processing access request
CN112286778A (en) * 2020-12-25 2021-01-29 国网汇通金财(北京)信息科技有限公司 Service chain call analysis method and device
CN112286778B (en) * 2020-12-25 2021-03-30 国网汇通金财(北京)信息科技有限公司 Service chain call analysis method and device
CN112783451A (en) * 2021-01-22 2021-05-11 中信银行股份有限公司 Time-consuming abnormity analysis method and system based on interceptor and storage medium
CN113238722A (en) * 2021-05-17 2021-08-10 上海中通吉网络技术有限公司 Log printing method and device

Similar Documents

Publication Publication Date Title
CN107818024A (en) A kind of request ID transmission methods and system based on spring blockers
CN107861859A (en) A kind of blog management method and system based on micro services framework
CN107766205B (en) A kind of monitoring system and method towards the tracking of micro services calling process
CN105608203B (en) A kind of Internet of Things log processing method and device based on Hadoop platform
Mayer et al. An approach to extract the architecture of microservice-based software systems
CN109409633B (en) Business monitoring and risk early warning system
US9189356B2 (en) Data audit module for application software
CN111917887A (en) System for realizing data governance under big data environment
CN108509392B (en) Multi-mechanism account checking method, system, computer equipment and storage medium
CN109947746A (en) A kind of quality of data management-control method and system based on ETL process
US20080104133A1 (en) Data cache techniques in support of synchronization of databases in a distributed environment
JP2007531939A (en) Provision of corporate information
US20100088197A1 (en) Systems and methods for generating remote system inventory capable of differential update reports
CN104217276A (en) Rule-based automatic auditing method and system
CN111046000B (en) Government data exchange sharing oriented security supervision metadata organization method
CN110990391A (en) Integration method and system of multi-source heterogeneous data, computer equipment and storage medium
CN106055325B (en) A kind of service construction method that support multisystem is run simultaneously
CN110336863B (en) Data reporting method and system
CN114745295A (en) Data acquisition method, device, equipment and readable storage medium
CN107506422A (en) The distributed information log processing system and method for a kind of multi-data source
CN114595129A (en) Configurable multi-dimensional data monitoring method and device and storage medium
CN112448911B (en) K-Means-based normal Server IP white list mining method
CN105681100B (en) A kind of comprehensive network management multi-protocols collection scheduling method
CN113010385B (en) Task state updating method, device, equipment and medium
US10706073B1 (en) Partitioned batch processing for a usage analysis system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20180320

RJ01 Rejection of invention patent application after publication