CN105391772B - Service request processing method, log processing method and device - Google Patents
Service request processing method, log processing method and device Download PDFInfo
- Publication number
- CN105391772B CN105391772B CN201510672608.3A CN201510672608A CN105391772B CN 105391772 B CN105391772 B CN 105391772B CN 201510672608 A CN201510672608 A CN 201510672608A CN 105391772 B CN105391772 B CN 105391772B
- Authority
- CN
- China
- Prior art keywords
- service request
- log
- mark
- log recording
- request processing
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Abstract
The embodiment of the present invention provides a kind of service request processing method, log processing method and device, wherein service request processing method includes: acquisition service requesting information；Service request operation is executed according to the service requesting information, wherein, being generated according to the service requesting information includes service request mark, the first logged sequence identifies and the service request of the second log sequence identifier handles log recording, the first logged sequence mark is the mark of current log, and the second log sequence identifier is the mark of current log father node.Using the technical solution of the embodiment of the present invention, rapidly and accurately can analyze and position leads to the key message of service request exception and/or the key message of failure on other lines is caused to reduce cost to quickly stop loss.
Description
Technical field
The present invention relates to technical field of data processing more particularly to a kind of service request processing methods, log processing method
And device.
Background technique
The user of requirement with to(for) network service is higher and higher, provides the platform scale of service also increasingly for user
Greatly, the system being related to when processing business is requested is more and more, when there is failure on line, needs for relevant log to be together in series
Being analyzed just can be with positioning failure.At present series connection log only have Developmental Engineer to log in each system after using manual mode into
Row, to position the key message for leading to failure, this mode is at high cost, time-consuming, low efficiency and accuracy are poor.
Summary of the invention
The purpose of the present invention is to provide a kind of service request processing method, log processing method and devices, can be quick
It is accurately realized fault location on line.
According to an aspect of the present invention, the present invention provides a kind of service request processing method, which comprises obtains industry
Business solicited message；Service request operation is executed according to the service requesting information, wherein is generated according to the service requesting information
Service request including service request mark, the first logged sequence mark and the second log sequence identifier handles log recording, institute
The mark that the first logged sequence mark is current log is stated, the second log sequence identifier is the mark of current log father node
Know.
Optionally, the service request is HTTP/HTTPS request, and the header of the HTTP/HTTPS request includes described
The information of service request mark, the first logged sequence mark and the second log sequence identifier.
Optionally, the method also includes: read service request mark, first day from preset common memory position
The information of will sequence identifier and the second log sequence identifier.
Optionally, the method also includes: the service request of generation processing log recording is stored in scheduled hard disk position
It sets or the service request processing log recording of generation is sent to specified server.
According to another aspect of the present invention, the present invention also provides a kind of log processing methods, which comprises obtains more
Service request handles log recording, and the service request processing log recording includes service request mark, the first logged sequence
Mark and the second log sequence identifier；The a plurality of service request processing log recording is gathered according to service request mark
It closes；Log recording is handled to the service request based on the mark polymerization of any service request, is closed according to the calling between business module
System determines the hierarchical relationship of the service request processing log recording of the polymerization, and is identified according to logged sequence to the polymerization
Service request processing log recording establish tree structure.
According to another aspect of the invention, the present invention also provides a kind of service request processing unit, described device includes: industry
Business acquiring unit, for obtaining service requesting information；Business operation unit, for executing business according to the service requesting information
Request operation, wherein being generated according to the service requesting information includes service request mark, the first logged sequence mark and second
The service request of logged sequence mark handles log recording, and the first logged sequence mark is the mark of current log, described
Second log sequence identifier is the mark of current log father node.
Optionally, the service request is HTTP/HTTPS request, and the header of the HTTP/HTTPS request includes described
The information of service request mark, the first logged sequence mark and the second log sequence identifier.
Optionally, described device further include: common memory unit, for storing the service request mark, the first log
The information of sequence identifier and the second log sequence identifier；
The business operation unit is used to read the service request mark, the first log sequence from the common memory unit
The information of column mark and the second log sequence identifier.
Optionally, described device further include: record/transmission unit, the service request for that will generate handle log recording
It is stored in scheduled hard disk position or the service request processing log recording of generation is sent to specified server.
According to another aspect of the invention, the present invention also provides a kind of log processing device, described device includes: that log obtains
Unit is taken, for obtaining a plurality of service request processing log recording, the service request processing log recording includes service request
Mark, the first logged sequence mark and the second log sequence identifier；Log aggregation unit, for being identified according to service request to institute
A plurality of service request processing log recording is stated to be polymerize；Journal processing unit, for poly- based on any service request mark
The service request of conjunction handles log recording, determines that the service request of the polymerization is handled according to the call relation between business module
The hierarchical relationship of log recording, and tree is established according to service request processing log recording of the logged sequence mark to the polymerization
Shape structure.
Service request processing method, log processing method provided by the embodiment of the present invention and device, at service request
The service request processing log generated after reason passes through service request mark, the first logged sequence mark and the second log sequence identifier
Carry out Xian Shang globally unique identifier.When occurring including the case where at least one: the processing result hair of a certain service request
Failure on raw abnormal and other lines identifies convergence service request processing log recording according to service request, according to business module it
Between call relation determine the polymerization service request processing log recording hierarchical relationship and identified according to logged sequence
Tree structure is established to the service request of polymerization processing log recording, so as to rapidly and accurately analyze and positioning causes
The key message of service request exception and/or the key message of failure on other lines is caused to reduce cost to quickly stop loss.
Detailed description of the invention
Fig. 1 is the flow diagram for showing exemplary embodiment of the present service request processing method；
Fig. 2 is the flow diagram for showing exemplary embodiment of the present log processing method；
Fig. 3 is to show exemplary embodiment of the present business module call relation schematic diagram；
Fig. 4 is to show exemplary embodiment of the present service request processing log recording tree structure schematic diagram；
Fig. 5 is a kind of structural schematic diagram for showing exemplary embodiment of the present service request processing unit；
Fig. 6 is another structural schematic diagram for showing exemplary embodiment of the present service request processing unit；
Fig. 7 is the structural schematic diagram for showing exemplary embodiment of the present log processing device；
Fig. 8 is that the service request processing log recording shown in exemplary embodiment of the present service request treatment process gathers
Close schematic diagram.
Specific embodiment
Basic conception of the invention is to provide service request processing method, log processing method and realizes the above method
Device.For same service request when service request is executed and operated, generating includes service request mark, the first logged sequence mark
Know and the service request of the second log sequence identifier handles log recording, wherein the first logged sequence mark is to work as the day before yesterday
The mark of will, the second log sequence identifier are the marks of current log father node.When appearance includes at least one
When situation: the processing result of a certain service request be abnormal with failure on other lines, according to service request identify convergence service
Request processing log recording determines that the service request of the polymerization handles log recording according to the call relation between business module
Hierarchical relationship and tree structure is established to the service request of polymerization processing log recording according to logged sequence mark,
Lead to the key message of service request exception so as to rapidly and accurately analyze and position and/or lead to failure on other lines
Key message reduces cost to quickly stop loss.
The monitoring method to the Distributed Services of exemplary embodiment of the present and device carry out detailed with reference to the accompanying drawing
Description.
Embodiment one
Fig. 1 is the flow diagram for showing exemplary embodiment of the present service request processing method.
Referring to Fig.1, in step S110, service requesting information is obtained.
As generation remote procedure call protocol (Remote Procedure Call between different business systems
Protocol, RPC) call or hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) call when,
Service request is HTTP/HTTPS request.
When identical services system is called, common memory position is preset for storing information in the operation system.
In the present embodiment, operation system can be obtained using technologies such as hypertext transfer protocol filter or blockers
The interior recalls information between different business systems.
In step S120, service request operation is executed according to the service requesting information, wherein according to the service request
It includes service request mark that information, which generates, the first logged sequence identifies and the service request of the second log sequence identifier handles log
Record, the first logged sequence mark are the marks of current log, and the second log sequence identifier is current log father section
The mark of point.In the present embodiment, service request mark is indicated with RequestID, for identifying same service request, same industry
The RequestID of the service request processing log recording of business request is identical, the service request processing log note of different business request
The RequestID of record is different；First logged sequence mark is indicated with SequenceID, for as service request processing log note
The mark of current log in record, and sequentially according to calling；Second log sequence identifier is indicated with ParentID, is used for conduct
Service request handles the mark of current log father node in log recording.
It is hidden in the header of HTTP/HTTPS request when RPC calling occurring between different business systems or HTTP is called
The information comprising service request mark, the first logged sequence mark and the second log sequence identifier is written likes, and is written
Into current thread context, used for generating log.
When same operation system is called, in preset common memory position storage service request mark, first day
The information of will sequence identifier and the second log sequence identifier is used for generating log.
Optionally, in step S130, by the service request processing log recording of generation be stored in scheduled hard disk position or
The service request processing log recording of generation is sent to specified server.
Using the technical solution of the present embodiment, business is passed through to the service request processing log generated after service request processing
Request mark, the first logged sequence mark and the second log sequence identifier carry out Xian Shang globally unique identifier.
Embodiment two
Fig. 2 is the flow diagram for showing exemplary embodiment of the present log processing method.
Referring to Fig. 2, exemplary embodiment of the present log processing method after the method for processing business for executing embodiment one,
The log processing method of the present embodiment can include:
In step S210, a plurality of service request processing log recording is obtained, the service request processing log recording includes
Service request mark, the first logged sequence mark and the second log sequence identifier.
Service request processing log request instruction is generated, includes service request mark, the first logged sequence mark in the instruction
Knowledge and the second log sequence identifier handle log recording according to a plurality of service request is obtained.
In step S220, a plurality of service request processing log recording is polymerize according to service request mark.
The RequestID of the service request processing log recording of same service request is identical, the business of different business request
The RequestID of request processing log recording is different, remembers according to by identical RequestID to the processing log of same service request
Record is polymerize.Log is handled to same service request with querying conditions such as timestamp or keywords in compared with the existing technology
Record carries out the mode of synthetic polymeric, and timestamp and keyword need true according to specific service request by maintenance personnel in polymerization
Fixed, subjectivity is strong, and randomness is also strong, low efficiency, poor accuracy.The present embodiment passes through RequestID globally unique identifier pair
Same service request processing log recording is polymerize, and high-efficient, accuracy is high.
In step S230, log recording is handled to the service request based on the mark polymerization of any service request, according to business
Call relation between module determines the hierarchical relationship of the service request processing log recording of the polymerization, and according to log sequence
Column mark establishes tree structure to the service request processing log recording of the polymerization.
Fig. 3 is to show exemplary embodiment of the present business module call relation schematic diagram.Single business module may
It generates single service request processing log recording to be also possible to that multiple service request processing log recordings can be generated, therefore, right
After service request handles log recording polymerization, the service request of polymerization can be first determined according to the call relation between business module
The hierarchical relationship for handling log recording, referring to Fig. 3, wherein the first business module M1, the second business module M2 and third business mould
Block M3 is successively call relation, and optionally, it is specific by three business submodules that the first business module M1 carries out service request processing
It realizing, i.e. the first business submodule H1, the second business submodule H2 and third business submodule H3, business processing is finished, and first
Business module M1, the second business module M2 and the corresponding service request processing log recording of third business module M3 are first
Business submodule H1, the second business submodule H2 and the corresponding service request of third business submodule H3 handle log recording
Upper one layer；The corresponding service request processing log recording of first business module M1 is the first business submodule H1, second respectively
The business of the father node of the corresponding service request processing log recording of business submodule H2 and third business submodule H3 is asked
Seek processing log recording.
First logged sequence mark is indicated with SequenceID, works as the day before yesterday for handling in log recording as service request
The mark of will, and sequentially according to calling；Second log sequence identifier is indicated with ParentID, for as at service request
Manage the mark of current log father node in log recording.Log recording is handled for the service request of divided hierarchical relationship,
Log recording can be handled to the service request of the polymerization according to the first logged sequence mark and the second log sequence identifier to build
Vertical tree structure.
For convenience of the log processing method in above-described embodiment is understood, below with a specific example to service request at
Specific description is done in the processing of reason log recording.
Log recording is handled for the service request that service request mark RequestID is 6518732360433892617
It is handled, generates for example following service request processing log request instruction:
It instructs 1.:
{ " result ": " [status=1, snapshot=
Com.baidu.rigel.log.platform.bo.LogSource@153, changeLogInfo={ }, class=class
The new Pan Gu data center standard of com.baidu.rigel.log.platform.bo.LogSource, logDesc=
Log, appName=ipangu-datacenter, id=339,21 09:57:52GMT+08:00 of updTime=FriAug
2015, searchurl=10.67.33.45:7600, name=ipanguDatacenterBase, primaryKey=339,
05 15:56:11GMT+08:002014 of base=0, addTime=Wed Nov ,] ", " returnCode ": " NORMAL ",
"threadId":"4906","logId":"4_7da9fc9f-ede1-4c40-8479-ee90dc11f3ff","
requestId":"6518732360433892617","cost":"44","proccessId":"161","
methodParams":"[339,]","depth":"3","startTime":"1442388612231","parentId":"
3","logSrcId":"4","interfaceName":"com.baidu.bjf.dao.SqlMapDao.findById","
nodeAddress":"10.57.202.16","threadName":"http-8080-22","isTreeNode":"true","
className":"com.baidu.bjf.dao.SqlMapDao","sequenceId":"4","methodName":"
findById","logType":"service"}
Wherein, RequestID is " 6518732360433892617 ", and ParentID is " 3 ", " SequenceID is " 4 ".
It instructs 2.:
{ " result ": " [status=1, snapshot=
Com.baidu.rigel.log.platform.bo.LogSource@153, changeLogInfo={ }, class=class
The new Pan Gu data center standard of com.baidu.rigel.log.platform.bo.LogSource, logDesc=
Log, appName=ipangu-datacenter, id=339,21 09:57:52GMT+08:00 of updTime=FriAug
2015, searchurl=10.67.33.45:7600, name=ipanguDatacenterBase, primaryKey=339,
05 15:56:11GMT+08:00 2014 of base=0, addTime=Wed Nov ,] ", " returnCode ": " NORMAL ", "
threadId":"4906","logId":
"4_5c12ab9e-27b0-45b3-a864-2bfe35cc802c","requestId":"
6518732360433892617","cost":"44","proccessId":"161","methodParams":"[339,]","
depth":"2","startTime":"1442388612231","parentId":"2","logSrcId":"4","
interfaceName":"com.baidu.bjf.service.GenericService.findById","
nodeAddress":"10.57.202.16","threadName":"http-8080-22","isTreeNode":"true","
className":"com.baidu.bjf.service.GenericService","sequenceId":"3","
methodName":"findById","logType":"service"}
Wherein, RequestID is " 6518732360433892617 ", and ParentID is " 2 ", " SequenceID is " 3 ".
It instructs 3.:
{"result":"[com.baidu.rigel.log.platform.bo.UnitySearch@1,
com.baidu.rigel.log.platform.bo.UnitySearch@2,
com.baidu.rigel.log.platform.bo.UnitySearch@3,
com.baidu.rigel.log.platform.bo.UnitySearch@4,
com.baidu.rigel.log.platform.bo.UnitySearch@5,
com.baidu.rigel.log.platform.bo.UnitySearch@6,
com.baidu.rigel.log.platform.bo.UnitySearch@7,
com.baidu.rigel.log.platform.bo.UnitySearch@8,
com.baidu.rigel.log.platform.bo.UnitySearch@9,
com.baidu.rigel.log.platform.bo.UnitySearch@a,
com.baidu.rigel.log.platform.bo.UnitySearch@b,
com.baidu.rigel.log.platform.bo.UnitySearch@c,
com.baidu.rigel.log.platform.bo.UnitySearch@d,]","returnCode":"NORMAL","
threadId":"4906","logId":"4_1def8c8d-7b32-4ee0-8e28-6217996d5ee5","
requestId":"6518732360433892617","cost":"37","proccessId":"161","
methodParams":"[]","depth":"2","startTime":"1442388612275","parentId":"2","
logSrcId":"4","interfaceName":"
com.baidu.bjf.service.GenericService.findAll","nodeAddress":"10.57.202.16","
threadName":"http-8080-22","isTreeNode":"true","className":"
com.baidu.bjf.service.GenericService","sequenceId":"5","methodName":"
findAll","logType":"service"}
Wherein, RequestID is " 6518732360433892617 ", and ParentID is " 2 ", " SequenceID is " 5 ".
It instructs 4.:
{ " result ": " [curPageNum=1, page_size=20, nextPage=null, orderBy=null,
TotalRecNum=2265885, pageSize=20, class=class com.baidu.bjf.dao.
PagineBean,
Total_page_num=2265885, dataList=
Com.baidu.rigel.log.platform.vo.LogRTVO@7da21755, prePage=null, isLastPage=
Null, sortBy=null, cur_page_num=1, startSerial=null ..., size=16] ", "
returnCode":"NORMAL","threadId":"4906","logId":"4_4656a2f0-e037-41bc-92d5-
95ca1e2f6c0e","requestId":"6518732360433892617","cost":"24755","proccessId":"
161","methodParams":"[com.baidu.rigel.log.platform.vo.LogRTSeachQuery@
7307afba,339,1,20,]","depth":"1","startTime":"1442388612231","parentId":"1","
logSrcId":"4","interfaceName":"
com.baidu.rigel.log.platform.service.LogRTService.searchLogRTVOList","
nodeAddress":"10.57.202.16","threadName":"http-8080-22","isTreeNode":"true","
className":"com.baidu.rigel.log.platform.service.LogRTService","sequenceId":"
2","methodName":"searchLogRTVOList","logType":"service"}
Wherein, RequestID is " 6518732360433892617 ", and ParentID is " 1 ", " SequenceID is " 2 ".
It instructs 5.:
{ " result ": " [] ", " returnCode ": " NORMAL ", " requestParam ": " [query.costEnd=
[Ljava.lang.String；@31d3f5f1, query.costBegin=[Ljava.lang.String；@17430845,
Query.isTreeNode=[Ljava.lang.String；@7ad6de10, query.interfaceName=
[Ljava.lang.String；@1c4705f0, query.logId=[Ljava.lang.String；@308d2b71,
Query.logType=[Ljava.lang.String；@41f209e, pageSize=[Ljava.lang.String；@
490b9482, query.sequenceId=[Ljava.lang.String；@108fa563, query.nodeAddress=
[Ljava.lang.String；@1796672f, query.startTimeEnd=[Ljava.lang.String；@
15a2cca8, query.extra=[Ljava.lang.String；@52b7bac5, query.returnCode=
[Ljava.lang.String；@3cb11c, query.parentId=[Ljava.lang.String；@13504ac2,
Query.startTimeBegin=[Ljava.lang.String；@46b30f13 ..., size=17] ", "
threadId":"4906","logId":"4_339d89a4-01ae-4bff-ba92-c5f02379ba9b","
requestId":"6518732360433892617","cost":"24764","proccessId":"161","depth":"
0","startTime":"1442388612227","parentId":"0","logSrcId":"4","
interfaceName":"/log-platform/log/logRealTime_query.action","nodeAddress":"
10.57.202.16","threadName":"http-8080-22","isAjax":"false","isTreeNode":"
true","srcAddress":"10.50.6.212","sequenceId":"1","logType":"http"}
Wherein, RequestID is " 6518732360433892617 ", and ParentID is " 0 ", " SequenceID is " 1 ".
Fig. 4 is to show exemplary embodiment of the present service request processing log recording tree structure schematic diagram.Referring to figure
4, service request mark RequestID are 6518732360433892617 service request processing log recording tree structures
5. service request that the first row corresponding instruction obtains handles log recording, 4. service request processing that the second row corresponding instruction obtains
Log recording, 2. service request that the third line corresponding instruction obtains handle log recording, 1. industry that fourth line corresponding instruction obtains
Business request processing log recording, 3. service request that fifth line corresponding instruction obtains handle log recording.
Embodiment three
Fig. 5 is a kind of structural schematic diagram for showing exemplary embodiment of the present service request processing unit.
Referring to Fig. 5, the service request processing side of embodiment one is can be performed in the service request processing unit of the embodiment of the present invention
Method.
The service request processing unit of the embodiment of the present invention may include business acquiring unit 510 and business operation unit 520.
Business acquiring unit 510 is for obtaining service requesting information.
Business operation unit 520 is used to execute service request operation according to the service requesting information, wherein according to described
It includes service request mark that service requesting information, which generates, the first logged sequence identifies and the service request of the second log sequence identifier
Log recording is handled, the first logged sequence mark is the mark of current log, and the second log sequence identifier is current
The mark of log father node.
The service request processing unit of the embodiment of the present invention handles day to the service request generated after service request processing
Will is identified by service request, the first logged sequence mark and the second log sequence identifier carry out Xian Shang globally unique identifier.
Optionally, the service request is HTTP/HTTPS request, and the header of the HTTP/HTTPS request includes described
The information of service request mark, the first logged sequence mark and the second log sequence identifier.
Example IV
Fig. 6 is another structural schematic diagram for showing exemplary embodiment of the present service request processing unit.
Referring to Fig. 6, on the basis of embodiment three, the service request processing unit described device of the present embodiment can also be wrapped
It includes: common memory unit 530, for storing the service request mark, the first logged sequence mark and the second logged sequence mark
The information of knowledge；Business operation unit is used to read the service request mark, the first logged sequence from the common memory unit
The information of mark and the second log sequence identifier.
Optionally, described device can also include: record/transmission unit 540, and the service request for that will generate handles day
Will record storage is sent to specified server in scheduled hard disk position or by the service request processing log recording of generation.
Embodiment five
Fig. 7 is the structural schematic diagram for showing exemplary embodiment of the present log processing device.
Referring to Fig. 7, the log processing method of embodiment two is can be performed in the log processing device of the embodiment of the present invention.The present invention
The log processing device of embodiment may include log acquisition unit 710, log aggregation unit 720 and journal processing unit 730.
Log acquisition unit 710 handles log for obtaining a plurality of service request processing log recording, the service request
Record includes service request mark, the first logged sequence mark and the second log sequence identifier.
Log aggregation unit 720 is used to carry out a plurality of service request processing log recording according to service request mark
Polymerization.
Journal processing unit 730 is used to handle log recording to the service request based on the mark polymerization of any service request,
The hierarchical relationship of the service request processing log recording of the polymerization, and root are determined according to the call relation between business module
Tree structure is established according to service request processing log recording of the logged sequence mark to the polymerization.
Fig. 8 is that the service request processing log recording shown in exemplary embodiment of the present service request treatment process gathers
Close schematic diagram.
Referring to Fig. 8, the context transfer of the first business system server 810 and the second business system server 820
Service request mark, the first logged sequence mark and the second log sequence identifier, the first business are carried in HTTP/HTTPS request
System server 810 and the second business system server 820 execute service request according to the service requesting information and operate, respectively
It generates service request and handles log recording, and the service request processing log recording with identical services request mark is gathered
It closes.
Log processing device provided by the embodiment of the present invention, when occurring including the case where at least one: a certain
The processing result of service request be abnormal with failure on other lines, according to service request identify convergence service request processing log
Record determines the hierarchical relationship of the service request processing log recording of the polymerization according to the call relation between business module
And tree structure is established according to service request processing log recording of the logged sequence mark to the polymerization, so as to quick
Accurately analyzing and position leads to the key message of service request exception and/or leads to the key message of failure on other lines, from
And quickly stop loss, reduce cost.
It may be noted that each step described in this application can be split as more multi-step according to the needs of implementation, it can also
The part operation of two or more steps or step is combined into new step, to achieve the object of the present invention.
It is above-mentioned to be realized in hardware, firmware according to the method for the present invention, or be implemented as being storable in recording medium
Software or computer code in (such as CD ROM, RAM, floppy disk, hard disk or magneto-optic disk), or it is implemented through network downloading
Original storage in long-range recording medium or nonvolatile machine readable media and the meter that will be stored in local recording medium
Calculation machine code, so that method described herein can be stored in using general purpose computer, application specific processor or programmable or specially
It is handled with such software in the recording medium of hardware (such as ASIC or FPGA).It is appreciated that computer, processor, micro-
Processor controller or programmable hardware include can store or receive software or computer code storage assembly (for example, RAM,
ROM, flash memory etc.), when the software or computer code are by computer, processor or hardware access and execute, realize herein
The processing method of description.In addition, when general purpose computer accesses the code for realizing the processing being shown here, the execution of code
General purpose computer is converted to the special purpose computer for being used for executing the processing being shown here.
The above description is merely a specific embodiment, but scope of protection of the present invention is not limited thereto, any
Those familiar with the art in the technical scope disclosed by the present invention, can easily think of the change or the replacement, and should all contain
Lid is within protection scope of the present invention.Therefore, protection scope of the present invention should be based on the protection scope of the described claims.
Claims (10)
1. a kind of service request processing method, which is characterized in that the described method includes:
Obtain service requesting information；
Service request operation is executed according to the service requesting information, wherein generating according to the service requesting information includes industry
The service request processing log recording of business request mark, the first logged sequence mark and the second log sequence identifier, described first
Logged sequence mark is the mark of current log, and the second log sequence identifier is the mark of current log father node.
2. the method according to claim 1, wherein the service request be HTTP/HTTPS request, it is described
The header of HTTP/HTTPS request includes service request mark, the first logged sequence mark and the second logged sequence mark
The information of knowledge.
3. the method according to claim 1, wherein the method also includes:
The service request mark, the first logged sequence mark and the second logged sequence mark are read from preset common memory position
The information of knowledge.
4. method described in any one of claim 1 to 3, which is characterized in that the method also includes: by the industry of generation
Business request processing log recording is stored in scheduled hard disk position or the service request processing log recording of generation is sent to finger
Fixed server.
5. a kind of log processing method, which is characterized in that the described method includes:
Obtain a plurality of service request processing log recording, the service request processing log recording includes service request mark, the
One logged sequence mark and the second log sequence identifier；
The a plurality of service request processing log recording is polymerize according to service request mark；
Log recording is handled to the service request based on the mark polymerization of any service request, is closed according to the calling between business module
System determines the hierarchical relationship of the service request processing log recording of the polymerization, and is identified according to logged sequence to the polymerization
Service request processing log recording establish tree structure.
6. a kind of service request processing unit, which is characterized in that described device includes:
Business acquiring unit, for obtaining service requesting information；
Business operation unit, for executing service request operation according to the service requesting information, wherein asked according to the business
Asking information to generate includes the service request processing day of service request mark, the first logged sequence mark and the second log sequence identifier
Will record, the first logged sequence mark are the marks of current log, and the second log sequence identifier is current log father
The mark of node.
7. device according to claim 6, which is characterized in that the service request is HTTP/HTTPS request, described
The header of HTTP/HTTPS request includes service request mark, the first logged sequence mark and the second logged sequence mark
The information of knowledge.
8. device according to claim 6, which is characterized in that described device further include:
Common memory unit, for storing the service request mark, the first logged sequence mark and the second log sequence identifier
Information；
The business operation unit is used to read the service request mark, the first logged sequence mark from the common memory unit
Know the information with the second log sequence identifier.
9. the device according to any one of claim 6~8, which is characterized in that described device further include:
Record/transmission unit, for the service request processing log recording of generation to be stored in scheduled hard disk position or will be given birth to
At service request processing log recording be sent to specified server.
10. a kind of log processing device, which is characterized in that described device includes:
Log acquisition unit, for obtaining a plurality of service request processing log recording, the service request handles log recording packet
Include service request mark, the first logged sequence mark and the second log sequence identifier；
Log aggregation unit, for being polymerize according to service request mark to a plurality of service request processing log recording；
Journal processing unit, for handling log recording to the service request based on the mark polymerization of any service request, according to industry
Call relation between business module determines the hierarchical relationship of the service request processing log recording of the polymerization, and according to log
Sequence identifier establishes tree structure to the service request processing log recording of the polymerization.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510672608.3A CN105391772B (en) | 2015-10-16 | 2015-10-16 | Service request processing method, log processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510672608.3A CN105391772B (en) | 2015-10-16 | 2015-10-16 | Service request processing method, log processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105391772A CN105391772A (en) | 2016-03-09 |
| CN105391772B true CN105391772B (en) | 2019-02-22 |
Family
ID=55423602
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510672608.3A Active CN105391772B (en) | 2015-10-16 | 2015-10-16 | Service request processing method, log processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105391772B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107181721A (en) * | 2016-03-11 | 2017-09-19 | 阿里巴巴集团控股有限公司 | A kind of information processing method and device based on daily record |
| CN106254144B (en) * | 2016-09-06 | 2020-02-14 | 华为技术有限公司 | Fault positioning platform, fault positioning method and device |
| CN108462598B (en) * | 2017-02-21 | 2022-03-11 | 阿里巴巴集团控股有限公司 | Log generation method, log analysis method and device |
| CN109213773B (en) * | 2017-07-06 | 2023-02-10 | 阿里巴巴集团控股有限公司 | Online fault diagnosis method and device and electronic equipment |
| CN107678933A (en) * | 2017-09-28 | 2018-02-09 | 中国平安人寿保险股份有限公司 | Daily record generation management method, device, equipment and computer-readable recording medium |
| CN108599973B (en) * | 2018-01-05 | 2021-08-24 | 创新先进技术有限公司 | Log association method, device and equipment |
| CN110297748A (en) * | 2018-03-22 | 2019-10-01 | 财付通支付科技有限公司 | The method, apparatus and computer readable storage medium of error are called in a kind of positioning |
| CN108667649B (en) * | 2018-03-30 | 2019-09-27 | 重庆小雨点小额贷款有限公司 | A kind of malfunction elimination method, apparatus and server |
| CN108768752B (en) * | 2018-06-25 | 2021-12-03 | 华为技术有限公司 | Fault positioning method, device and system |
| CN110007957A (en) * | 2018-12-17 | 2019-07-12 | 阿里巴巴集团控股有限公司 | Call link construction method, device and equipment |
| CN111625431B (en) * | 2019-02-28 | 2022-04-22 | 华为技术有限公司 | Log information generation method and device and electronic equipment |
| CN110046073B (en) * | 2019-03-29 | 2022-10-18 | 厦门网宿有限公司 | Log collection method and device, equipment and storage medium |
| CN112434244A (en) * | 2020-11-23 | 2021-03-02 | 北京八分量信息科技有限公司 | Method and device for log processing based on UEBA (unified extensible firmware architecture) and related product |
| CN112433915B (en) * | 2020-11-30 | 2023-06-16 | 泰康保险集团股份有限公司 | Data monitoring method and related device based on distributed performance monitoring tool |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557291A (en) * | 2009-05-25 | 2009-10-14 | 杭州华三通信技术有限公司 | Method for log aggregation and device thereof |
| CN101753344A (en) * | 2008-12-12 | 2010-06-23 | 华为技术有限公司 | Method, device and system for logging |
| CN102136922A (en) * | 2010-01-22 | 2011-07-27 | 华为技术有限公司 | Correlation analysis method, equipment and system |
| CN102447633A (en) * | 2011-12-29 | 2012-05-09 | 北京亿赞普网络技术有限公司 | Log transmission method and system |
| CN104052616A (en) * | 2013-03-15 | 2014-09-17 | 深圳市腾讯计算机系统有限公司 | Method and system for managing services in Internet data center |
| CN104301360A (en) * | 2013-07-19 | 2015-01-21 | 阿里巴巴集团控股有限公司 | Method, log server and system for recording log data |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI305619B (en) * | 2006-05-12 | 2009-01-21 | Qisda Corp | State synchronization systems and methods |
| US7752229B2 (en) * | 2007-01-26 | 2010-07-06 | International Business Machines Corporation | Real-time identification of sub-assemblies containing nested parts |
-
2015
- 2015-10-16 CN CN201510672608.3A patent/CN105391772B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101753344A (en) * | 2008-12-12 | 2010-06-23 | 华为技术有限公司 | Method, device and system for logging |
| CN101557291A (en) * | 2009-05-25 | 2009-10-14 | 杭州华三通信技术有限公司 | Method for log aggregation and device thereof |
| CN102136922A (en) * | 2010-01-22 | 2011-07-27 | 华为技术有限公司 | Correlation analysis method, equipment and system |
| CN102447633A (en) * | 2011-12-29 | 2012-05-09 | 北京亿赞普网络技术有限公司 | Log transmission method and system |
| CN104052616A (en) * | 2013-03-15 | 2014-09-17 | 深圳市腾讯计算机系统有限公司 | Method and system for managing services in Internet data center |
| CN104301360A (en) * | 2013-07-19 | 2015-01-21 | 阿里巴巴集团控股有限公司 | Method, log server and system for recording log data |
Non-Patent Citations (1)
| Title |
|---|
| 《一种适用于多样性环境的业务流程挖掘方法》;杨丽琴;《软件学报》;20150315(第3期);第550-560页 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105391772A (en) | 2016-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105391772B (en) | Service request processing method, log processing method and device | |
| JP6998976B2 (en) | Query processing methods, query processing systems, servers and computer-readable media | |
| US10133622B2 (en) | Enhanced error detection in data synchronization operations | |
| CN105207806A (en) | Monitoring method and apparatus of distributed service | |
| US10177984B2 (en) | Isolation of problems in a virtual environment | |
| US20180004833A1 (en) | Data linking | |
| US9122784B2 (en) | Isolation of problems in a virtual environment | |
| CN110022221B (en) | System interface data monitoring method, device and system | |
| US20120089734A1 (en) | Allocation of resources between web services in a composite service | |
| CN111124830B (en) | Micro-service monitoring method and device | |
| CN106210124B (en) | A kind of unified cloud data center monitoring system | |
| CN107133231B (en) | Data acquisition method and device | |
| CN111400288A (en) | Data quality inspection method and system | |
| CN111459944A (en) | MR data storage method, device, server and storage medium | |
| WO2015139565A1 (en) | Heterogeneous logging system management configuration | |
| US10671470B2 (en) | Application performance management system with dynamic discovery and extension | |
| CN111177244A (en) | Data association analysis method for multiple heterogeneous databases | |
| JP2018525728A (en) | A distributed machine learning analysis framework for analyzing streaming datasets from computer environments | |
| EP2052325A1 (en) | Reduction of message flow between bus-connected consumers and producers | |
| KR20130097366A (en) | Method and apparatus for managing data center based on ontology | |
| CN111177239B (en) | Unified log processing method and system based on HDP big data cluster | |
| WO2016206241A1 (en) | Data analysis method and apparatus | |
| CN115033639A (en) | Method and related device for generating relation graph for data sharing among clusters | |
| CN109710487A (en) | A kind of monitoring method and device | |
| CN112749197B (en) | Data fragment refreshing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |