CN109921927A - Real-time calling D-chain trace method based on micro services - Google Patents
Real-time calling D-chain trace method based on micro services Download PDFInfo
- Publication number
- CN109921927A CN109921927A CN201910126968.1A CN201910126968A CN109921927A CN 109921927 A CN109921927 A CN 109921927A CN 201910126968 A CN201910126968 A CN 201910126968A CN 109921927 A CN109921927 A CN 109921927A
- Authority
- CN
- China
- Prior art keywords
- chain
- call
- calling
- traceid
- link
- 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
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
A kind of real-time calling D-chain trace method based on micro services, the present invention uses call relation data structure, it brings distributed caching and database client monitoring into micro services and calls Chain System, by being implanted into traceID in business diary, the business information of call chain is connected, for calling nest relation one by one being combed clear in complicated calling.The efficiency of positioning production problem can be greatly promoted by this system, and exploitation operation maintenance personnel can be promoted for the understandability of system, so as to better Optimal improvements system by the performance information of each link in analysis micro services call chain.
Description
Technical field
The invention belongs to fields of communication technology, are related to a kind of real-time calling D-chain trace method based on micro services.
Background technique
Micro services have become the noun of non-normalizing in IT Internet technology at present, and the thought of micro services framework is exactly will be whole
Body business splits into independent module one by one according to business scope.Each micro services module is independently disposed, between micro services
Relationship is loose coupling.It is a distributed structure/architecture, micro services mould that these characteristics of micro services, which have been doomed micro services framework innately,
It is interacted between block by the interface after splitting, and is stateless service.Under this framework, a complete business
Process is likely to processing and forwarding by multiple micro services.So below by that can encounter in our daily business
Some scenes:
1, user places an order on certain APP buys the failure of some product, is that the interface APP tune crm system malfunctions on earth, still
APP tune counter system malfunctions, and also or APP tune crm system, CRM adjust sales counter to malfunction again；
2, user always has a certain proportion of failure when handling a certain business, and whether that is in some micro services cluster
Some node there is a problem；
3, very poor for the access performance of data Layer in the calling of certain micro services, wonder it is access cache service
SQL executes time mistake when device (such as Redis) performance is out of joint or access relational database (such as MYSQL)
It is long?
In the prior art, the completion of service request will call the service of multiple subsystems on different server, be called
Service will also call other services mostly, and along with the access to the multiple Database Systems of bottom or file system.It faces
The call relation of various complexity, when a problem occurs, the problem diagnostic method under traditional centralized application architecture will be unable to fastly
Fast, accurate orientation problem point.
As technology continues to develop, nowadays the most of background services of internet area all have been completed that SOA is (service-oriented
Architecture) change, so the tracking to business can directly be reduced to the tracking to service call frame, so more and more
Tracking system also emerge.Distributed tracking Systems Theory model basic source is in the Dapper of GOOGLE at present, it is in detail
Thin elaborates how to track to request call chain, and Dapper is initially the request processing in order to track online service system
Process.Such as in search system, the request of user can pass through the processing of multiple subsystems in systems, and at these
Reason occurs, when request processing is abnormal, to need quickly to find the problem on the even different clusters of different machines, and
Being accurately positioned is which link is out of joint, this is very important, and Dapper is exactly in order to solve the problems.But
Dapper is only to solve the problems, such as request call this proposes theoretical model and simple realization, and function is relatively simple, can not
Comprehensive solution is provided.
Therefore, how to solve the above problems, be those skilled in the art the content of important research.
Summary of the invention
To overcome the deficiencies in the prior art described above, it is an object of that present invention to provide a kind of real-time callings based on micro services
D-chain trace method.
In order to achieve the above objects and other related objects, the present invention provides a kind of real-time calling D-chain trace based on micro services
Method, comprising the following steps:
(1), a globally unique traceID can be generated when each service is initiated, and in link calling process,
TraceID can be transmitted to each link link, and each isolated calling is together in series by this traceID, call chain with
Track streaming counting device calculates the time-consuming and calling time of entire link using the log information of identical traceID to be collected into together
The time-consuming and call number of several and each link link, and Hbase is written, call chain trace log is generated, link tracing is used for
Optimize with performance；
(2), by the depth of call chain and range information, the sequential hierarchy information that micro services are called is obtained, and identifies and follows
Ring nesting allocation；Call each link nodes in link that can generate a chainID, for distinguishing calling sequence in call chain
With the level of nesting；
(3) micro services RPC frame, is transformed, transmits traceID and chainID when calling, is received in server-side
After to request by traceID be arranged into ThreadLocal, while according to be transmitted through come father chain road chainID, generate indicate this
The chainID of link sequence and nest relation；
(4) the interface for providing in micro services RPC frame and obtaining traceID, is transformed, allows developer to obtain at any time and works as front
TraceID in journey access, is used for orientation problem.
Further, the generation of the call chain trace log is to collect prison using addition filter class in RPC frame
Control message format data, and it is asynchronous be sent to kafka message queue, identical traceID is sent to by hashing algorithm same
Kafkapatition, so that the monitoring log of each interface is all sent to the same place in call chain, it is subsequent calculating call chain
It prepares.
Further, chainID create-rule: nested layer level indicates that calling sequence is started counting from 0 with " ", sends out for the first time
Rise call, link link default chainID be 0, behind link link chainID are as follows: [father chain road chainID]+" "+[subchain
Road calling sequence].
Further, the call chain tracking streaming counter is passed through by the trace log of consumption kafka call chain
TraceID filters out the data belonged to call chain in a service request, is arranged out by chainID with a call chain
Upper interface calling sequence, generates the object of fork tree construction, and generate chainKey, for identifying call chain, is identified with traceID
Certain call chain example.
Further, it is described referred to by chainID arrangement using according to chain type interface service title method name and
Call the character string arrangement being sequentially generated.
Further, call each call chain of sequential grammar generation chainKey statistics per second according to the call chain interface
Call number and average response time, and in addition write timing database Opentsdb in real time will for monitoring and alerting
TraceID and call chain example are stored in Hbase.
Further, call chain structured data chainKey and the company's of calling instance data are stored separately by the Hbase table,
Hbase chainKey table is created first, and for depositing call chain structured data, table data volume is smaller, and the MD5 value of chainKey is done
For the rowKey of table, chainKey character string is as train value；Chain instance table is created again, according to the MD5 of chainKey
Value splicing second grade timestamp stores calling per second and connects instance data, and column key value deposits traceID, and column value value deposits call chain reality
Number of cases evidence.
Since above-mentioned technical proposal is used, the present invention has the advantage that as follows compared with prior art:
The present invention uses call relation data structure, and distributed caching and database client monitoring are brought into incognito
Chain System is called in business, and by being implanted into traceID in business diary, the business information of call chain is connected；For in complexity
It is clear calling nest relation to comb one by one in calling.The effect of positioning production problem can be greatly promoted by this system
Rate, and exploitation operation maintenance personnel can be promoted for system by the performance information of each link in analysis micro services call chain
Understandability, so as to better Optimal improvements system.
Every business backstage micro services chain relationship of real-time calling D-chain trace system monitoring enterprise of the present invention, passes through
TraceID positions a specific call chain tracking data, and records each interface details for calling link, and recalls information (is called
State, response time), help enterprise's operation maintenance personnel, developer's orientation problem, problem analysis, optimization performance etc..With this skill
Effect after art innovation achievement shows the following aspects:
1, code is entirely without invasive.
2, standard supervision agreement is formulated, a variety of RPC frames is supported to access.
3, multitype database and distributed cache system, such as Oracle, MySQL, Redis are supported.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention, for those of ordinary skill in the art, without any creative labor, according to
These attached drawings obtain other attached drawings and still fall within scope of the invention.
Fig. 1 is that the embodiment of the present invention calls chain type relation schematic diagram.
Specific embodiment
Below in conjunction with attached drawing, embodiments of the present invention, those skilled in the art are illustrated by particular specific embodiment
It can be understood other advantages and efficacy of the present invention easily by content disclosed by this specification.
Embodiment:
A kind of real-time calling D-chain trace method based on micro services, comprising the following steps:
(1), a globally unique traceID can be generated when each service is initiated, and in link calling process,
TraceID can be transmitted to each link link, and each isolated calling is together in series by this traceID, call chain with
The log information of identical traceID using the time-consuming for calculating entire link together is collected by track streaming counting device, with calling time
Number, and Hbase is written, call chain trace log is generated, is optimized for link tracing and performance；
(2), by the depth of call chain and range information, the sequential hierarchy information that micro services are called is obtained, and identifies and follows
Ring nesting allocation；Call each link nodes in link that can generate a chainID, for distinguishing calling sequence in call chain
With the level of nesting；
(3) micro services RPC (such as Dubbo) frame, is transformed, transmits traceID and chainID when calling,
Server-side receive request after by traceID be arranged into ThreadLocal, while according to be transmitted through come father chain road chainID,
Generate the chainID for indicating link sequence and nest relation；
(4), be transformed micro services RPC (such as Dubbo) frame in provide obtain traceID interface, allow developer at any time
The traceID in current thread access is obtained, orientation problem is used for.
Further, the generation of the call chain trace log is to collect prison using addition filter class in RPC frame
Control message format data, and it is asynchronous be sent to kafka message queue, identical traceID is sent to by hashing algorithm same
Kafkapatition, so that the monitoring log of each interface is all sent to the same place in call chain, it is subsequent calculating call chain
It prepares.
Call chain trace log list of fields is as follows
Json message format log is as follows:
Message is provided in the form of array, and sequence turns to json object.Json object example is as follows:
[{
"protocol":"dubbo",
"providerPort":7010,
"consumerSide":true,
"serviceVersion":"1.0.0",
"endTime":1484887076041,
"serviceName":"cn.com.git.sc.customer2dubbo.service.CusService",
"startTime":1484887076031,
"appName":"app_product",
"chainId":"0",
"consumerPort":0,
"initial":true,
"serviceGroup":"",
"traceId":"35d01fc4-7cd7-48a7-be6f-36603e5c8d62",
"methodName":"$invoke",
"success":true,
"consumerHost":"192.168.99.41",
"providerHost":"192.168.99.42"
}]
Further, chainID create-rule: nested layer level indicates that calling sequence is started counting from 0 with " ", sends out for the first time
Rise call, link link default chainID be 0, behind link link chainID are as follows: [father chain road chainID]+" "+[subchain
Road calling sequence].As shown in Figure 1, example is as follows:
Front end applications are initiated to call for the first time, and service A, the chainID of link link is called to be denoted as 0,
A calls service B, the chainID of link link to be denoted as 0.0 (father chain road chainID:0) for the first time,
B initiate for the first time call Redis component, the chainID of link link be denoted as 0.0.0 (father chain road chainID:
0.0),
B initiates second and service D, the chainID of link link is called to be denoted as 0.0.1 (father chain road chainID:0.0),
Second of calling of A hair, calls service C, link link chainID to be denoted as 0.1 (father chain road chainID:0),
……
Further, the call chain tracking streaming counter is passed through by the trace log of consumption kafka call chain
TraceID filters out the data belonged to call chain in a service request, is arranged out by chainID with a call chain
Upper interface calling sequence, generates the object of fork tree construction, and generate chainKey, for identifying call chain, is identified with traceID
Certain call chain example.
Further, it is described referred to by chainID arrangement using according to chain type interface service title method name and
Call the character string arrangement being sequentially generated.
Further, call each call chain of sequential grammar generation chainKey statistics per second according to the call chain interface
Call number and average response time, and in addition write timing database Opentsdb in real time will for monitoring and alerting
TraceID and call chain example are stored in Hbase.
Further, call chain structured data chainKey and the company's of calling instance data are stored separately by the Hbase table,
Creation hbase chainKey table is for depositing call chain structured data first, and data volume is smaller, and the MD5 value of chainKey is as table
RowKey, chainKey character string is as train value；Chain instance table is created again, is spelled according to the MD5 value of chainKey
It connects second grade timestamp and stores calling per second and connect instance data, column key value deposits traceID, and column value value deposits call chain instance number
According to.
With when, Internet user use app login account, app call Account Registration center micro services interface, app account
Family registration center receives user's registration information, calls searching for user relevance information micro services interface (queryUserSerRela),
Searching for user relevance information micro services interface can cache the inside from redis and take out data, return to registration center's interface, right family note
Volume hub-interface, which recalls user and authorizes sort interface (authUserAndType), looks into new user authorization levels, user's authorization
Data can be obtained from redis caching with sort interface to return, finally return to data and give login account center.
The above-described embodiments merely illustrate the principles and effects of the present invention, and is not intended to limit the present invention.It is any ripe
The personage for knowing this technology all without departing from the spirit and scope of the present invention, carries out modifications and changes to above-described embodiment.Cause
This, institute is complete without departing from the spirit and technical ideas disclosed in the present invention by those of ordinary skill in the art such as
At all equivalent modifications or change, should be covered by the claims of the present invention.
Claims (6)
1. a kind of real-time calling D-chain trace method based on micro services, it is characterised in that: the following steps are included:
, when each service is initiated can generate a globally unique traceID, and in link calling process, traceID
It can be transmitted to each link link, each isolated calling is together in series by this traceID, call chain tracks streaming meter
Number devices calculate the time-consuming and call number and each of entire link using the log information of identical traceID to be collected into together
The time-consuming and call number of link link, and Hbase is written, call chain trace log is generated, it is excellent for link tracing and performance
Change；
, by the depth and range information of call chain, obtain the sequential hierarchy information that micro services are called, and identify that circulation is embedding
Set calls；Call each link nodes in link that can generate a chainID, for distinguish in call chain calling sequence with it is embedding
Cover level；
, transformation micro services RPC frame, traceID and chainID transmitted when calling, receives and asks in server-side
After asking by traceID be arranged into ThreadLocal, while according to be transmitted through come father chain road chainID, generate expression the link
The chainID of sequence and nest relation；
, transformation micro services RPC frame in provide obtain traceID interface, allow developer obtain at any time current thread visit
TraceID in asking is used for orientation problem.
2. the real-time calling D-chain trace method according to claim 1 based on micro services, it is characterised in that: the call chain
The generation of trace log and asynchronous is sent to using addition filter class collection monitoring message format data in RPC frame
Identical traceID is sent to the same kafka patition by the hash algorithm of kafka by kafka message queue, so that
The monitoring log of each interface is all sent to the same place in call chain, prepares for subsequent calculating call chain.
3. the real-time calling D-chain trace method according to claim 1 based on micro services, it is characterised in that: the call chain
Streaming counter is tracked by the trace log of consumption kafka call chain, is filtered out and is belonged to a business by traceID
The data of call chain in request are arranged out by chainID with interface calling sequence in a call chain, and fork tree construction is generated
Object, and chainKey is generated, for identifying call chain, certain call chain example is identified with traceID.
4. the real-time calling D-chain trace method according to claim 3 based on micro services, it is characterised in that: described to pass through
ChainID arrangement refers to be arranged using the character string being sequentially generated according to chain type interface service title method name and calling.
5. the real-time calling D-chain trace method according to claim 3 based on micro services, it is characterised in that: according to the tune
It calls sequential grammar to generate chainKey with chain interface and counts each call chain call number per second and average response time, and
In addition traceID and call chain example are stored in by real-time write timing database Opentsdb for monitoring and alerting
Hbase。
6. the real-time calling D-chain trace method according to claim 5 based on micro services, it is characterised in that: the Hbase
Call chain structured data chainKey and the company's of calling instance data are stored separately by table, and creation hbase chainKey table first is used
In depositing call chain structured data, data volume is smaller, and as the rowKey of table, chainKey character string done for the MD5 value of chainKey
For train value；Chain instance table is created again, and second grade timestamp is spliced according to the MD5 value of chainKey and stores calling per second
Even instance data, column key value deposit traceID, and column value value deposits call chain instance data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910126968.1A CN109921927A (en) | 2019-02-20 | 2019-02-20 | Real-time calling D-chain trace method based on micro services |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910126968.1A CN109921927A (en) | 2019-02-20 | 2019-02-20 | Real-time calling D-chain trace method based on micro services |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109921927A true CN109921927A (en) | 2019-06-21 |
Family
ID=66961847
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910126968.1A Pending CN109921927A (en) | 2019-02-20 | 2019-02-20 | Real-time calling D-chain trace method based on micro services |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109921927A (en) |
Cited By (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110377324A (en) * | 2019-07-04 | 2019-10-25 | 中铁四局集团有限公司 | A kind of informatization platform monitoring system and construction method |
| CN110428325A (en) * | 2019-07-31 | 2019-11-08 | 中国工商银行股份有限公司 | Transaction tracking and device |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
| CN110535722A (en) * | 2019-08-27 | 2019-12-03 | 江苏瑞中数据股份有限公司 | A kind of full link operation and monitoring method of the micro services in cross-safety zone domain |
| CN110601994A (en) * | 2019-10-14 | 2019-12-20 | 南京航空航天大学 | Load balancing method for micro-service chain perception in cloud environment |
| CN110677304A (en) * | 2019-10-11 | 2020-01-10 | 广州趣丸网络科技有限公司 | Distributed problem tracking system and equipment |
| CN110943858A (en) * | 2019-11-21 | 2020-03-31 | 中国联合网络通信集团有限公司 | Fault positioning method and device |
| CN111049878A (en) * | 2019-10-23 | 2020-04-21 | 平安科技（深圳）有限公司 | Method, device, electronic device and storage medium for visualizing micro-service call chain |
| CN111158995A (en) * | 2019-11-29 | 2020-05-15 | 武汉物易云通网络科技有限公司 | Method and system for realizing cross-system log tracking query based on skywalk and ELK platform |
| CN111277650A (en) * | 2020-01-20 | 2020-06-12 | 南京航空航天大学 | Automatic micro-service identification method combining functional indexes and non-functional indexes |
| CN111459766A (en) * | 2019-11-14 | 2020-07-28 | 国网浙江省电力有限公司信息通信分公司 | Calling chain tracking and analyzing method for micro-service system |
| CN111625452A (en) * | 2020-05-22 | 2020-09-04 | 上海哔哩哔哩科技有限公司 | Flow playback method and system |
| CN111638973A (en) * | 2020-05-11 | 2020-09-08 | 紫光云技术有限公司 | Method for tracing execution sequence of calculation by link |
| CN111913789A (en) * | 2020-06-29 | 2020-11-10 | 浪潮通用软件有限公司 | Program tracking method, device and medium supporting micro-service architecture |
| CN111984346A (en) * | 2020-08-12 | 2020-11-24 | 八维通科技有限公司 | Method, system, device and storage medium for call chain tracking in micro-service environment |
| CN112015622A (en) * | 2020-08-24 | 2020-12-01 | 杭州云徙科技有限公司 | Message link tracking and monitoring method and system applied to business middle station |
| CN112187527A (en) * | 2020-09-15 | 2021-01-05 | 中信银行股份有限公司 | Micro-service abnormity positioning method and device, electronic equipment and readable storage medium |
| CN112311811A (en) * | 2020-11-16 | 2021-02-02 | 深圳市欢太科技有限公司 | Full link tracking method, device, storage medium and server |
| CN112311894A (en) * | 2020-11-12 | 2021-02-02 | 北京沃东天骏信息技术有限公司 | Method, apparatus, electronic device, and computer-readable medium for generating information |
| CN112346856A (en) * | 2020-10-21 | 2021-02-09 | 北京基调网络股份有限公司 | Method, device and equipment for displaying multilink call topology under micro-service architecture |
| CN112416626A (en) * | 2020-12-02 | 2021-02-26 | 中国联合网络通信集团有限公司 | Data processing method and device |
| CN112433757A (en) * | 2020-11-27 | 2021-03-02 | 中国建设银行股份有限公司 | Method and device for determining interface calling relationship |
| CN112532478A (en) * | 2020-11-23 | 2021-03-19 | 华人运通(上海)云计算科技有限公司 | Link relation tracking method, system, viewing method, device, equipment and plug-in |
| CN112558947A (en) * | 2020-12-18 | 2021-03-26 | 京东数字科技控股股份有限公司 | Program call tracing method, device and storage medium |
| CN112559212A (en) * | 2020-12-18 | 2021-03-26 | 北京航天云路有限公司 | Service call chain implementation method based on self-research framework |
| CN112612675A (en) * | 2020-12-25 | 2021-04-06 | 山东经伟晟睿数据技术有限公司 | Distributed big data log link tracking method and system under micro-service architecture |
| CN112667457A (en) * | 2019-10-16 | 2021-04-16 | 烽火通信科技股份有限公司 | Method and system for monitoring service call under micro-service architecture |
| CN112699000A (en) * | 2019-10-23 | 2021-04-23 | 拉扎斯网络科技（上海）有限公司 | Data processing method and device, readable storage medium and electronic equipment |
| CN112783629A (en) * | 2021-02-01 | 2021-05-11 | 天津五八到家货运服务有限公司 | Service calling method and device, electronic equipment and storage medium |
| CN112988798A (en) * | 2021-03-29 | 2021-06-18 | 成都卫士通信息产业股份有限公司 | Log processing method, device, equipment and medium |
| CN113132143A (en) * | 2019-12-31 | 2021-07-16 | 深圳云天励飞技术有限公司 | Service call tracing method and related product |
| CN113360361A (en) * | 2021-08-11 | 2021-09-07 | 云智慧（北京）科技有限公司 | Method, device and equipment for constructing distributed operation and maintenance simulation system |
| CN113760778A (en) * | 2021-11-09 | 2021-12-07 | 浙江大学滨海产业技术研究院 | Word vector model-based micro-service interface division evaluation method |
| CN113868345A (en) * | 2021-10-11 | 2021-12-31 | 支付宝(杭州)信息技术有限公司 | Method and device for carrying out main body classification on business data |
| CN114003472A (en) * | 2022-01-04 | 2022-02-01 | 连连（杭州）信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114143369A (en) * | 2021-12-09 | 2022-03-04 | 华人运通(上海)云计算科技有限公司 | Service monitoring system of cloud platform |
| CN114172949A (en) * | 2021-12-10 | 2022-03-11 | 航天信息股份有限公司 | Micro-service link monitoring and tracking method and system |
| WO2022110675A1 (en) * | 2020-11-25 | 2022-06-02 | 平安普惠企业管理有限公司 | Artificial intelligence-based log generation method and apparatus, computer device and medium |
| CN114615521A (en) * | 2022-03-10 | 2022-06-10 | 网易（杭州）网络有限公司 | Video processing method and device, computer readable storage medium and electronic equipment |
| CN114745295A (en) * | 2022-04-19 | 2022-07-12 | 京东科技控股股份有限公司 | Data acquisition method, device, equipment and readable storage medium |
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN117573481A (en) * | 2024-01-15 | 2024-02-20 | 企家有道网络技术(北京)有限公司 | Interface monitoring method, system, electronic device and computer readable storage medium |
| US11947439B2 (en) | 2020-11-30 | 2024-04-02 | International Business Machines Corporation | Learning from distributed traces for anomaly detection and root cause analysis |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN107580018A (en) * | 2017-07-28 | 2018-01-12 | 北京北信源软件股份有限公司 | The tracking and device of a kind of distributed system |
| US20180131590A1 (en) * | 2015-07-20 | 2018-05-10 | Cisco Technology, Inc. | Method and apparatus for tracing paths in service function chains |
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
-
2019
- 2019-02-20 CN CN201910126968.1A patent/CN109921927A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180131590A1 (en) * | 2015-07-20 | 2018-05-10 | Cisco Technology, Inc. | Method and apparatus for tracing paths in service function chains |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106790718A (en) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | Service call link analysis method and system |
| CN107580018A (en) * | 2017-07-28 | 2018-01-12 | 北京北信源软件股份有限公司 | The tracking and device of a kind of distributed system |
| CN108038145A (en) * | 2017-11-23 | 2018-05-15 | 携程旅游网络技术（上海）有限公司 | Distributed Services tracking, system, storage medium and electronic equipment |
Cited By (65)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110377324A (en) * | 2019-07-04 | 2019-10-25 | 中铁四局集团有限公司 | A kind of informatization platform monitoring system and construction method |
| CN110377324B (en) * | 2019-07-04 | 2023-01-24 | 安徽数智建造研究院有限公司 | Information platform monitoring system and construction method |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
| CN110445643B (en) * | 2019-07-25 | 2021-11-16 | 泰康保险集团股份有限公司 | Asynchronous microservice call link tracking method, device, medium and electronic equipment |
| CN110428325A (en) * | 2019-07-31 | 2019-11-08 | 中国工商银行股份有限公司 | Transaction tracking and device |
| CN110535722A (en) * | 2019-08-27 | 2019-12-03 | 江苏瑞中数据股份有限公司 | A kind of full link operation and monitoring method of the micro services in cross-safety zone domain |
| CN110677304A (en) * | 2019-10-11 | 2020-01-10 | 广州趣丸网络科技有限公司 | Distributed problem tracking system and equipment |
| CN110601994B (en) * | 2019-10-14 | 2021-07-16 | 南京航空航天大学 | Load balancing method for micro-service chain perception in cloud environment |
| CN110601994A (en) * | 2019-10-14 | 2019-12-20 | 南京航空航天大学 | Load balancing method for micro-service chain perception in cloud environment |
| CN112667457A (en) * | 2019-10-16 | 2021-04-16 | 烽火通信科技股份有限公司 | Method and system for monitoring service call under micro-service architecture |
| CN112699000A (en) * | 2019-10-23 | 2021-04-23 | 拉扎斯网络科技（上海）有限公司 | Data processing method and device, readable storage medium and electronic equipment |
| CN111049878A (en) * | 2019-10-23 | 2020-04-21 | 平安科技（深圳）有限公司 | Method, device, electronic device and storage medium for visualizing micro-service call chain |
| CN111049878B (en) * | 2019-10-23 | 2023-03-21 | 平安科技（深圳）有限公司 | Method, device, electronic device and storage medium for visualizing micro-service call chain |
| CN111459766A (en) * | 2019-11-14 | 2020-07-28 | 国网浙江省电力有限公司信息通信分公司 | Calling chain tracking and analyzing method for micro-service system |
| CN111459766B (en) * | 2019-11-14 | 2024-01-12 | 国网浙江省电力有限公司信息通信分公司 | Micro-service system-oriented call chain tracking and analyzing method |
| CN110943858A (en) * | 2019-11-21 | 2020-03-31 | 中国联合网络通信集团有限公司 | Fault positioning method and device |
| CN111158995B (en) * | 2019-11-29 | 2020-12-29 | 武汉物易云通网络科技有限公司 | Method and system for realizing cross-system log tracking query based on skywalk and ELK platform |
| CN111158995A (en) * | 2019-11-29 | 2020-05-15 | 武汉物易云通网络科技有限公司 | Method and system for realizing cross-system log tracking query based on skywalk and ELK platform |
| CN113132143B (en) * | 2019-12-31 | 2023-04-07 | 深圳云天励飞技术有限公司 | Service call tracing method and related product |
| CN113132143A (en) * | 2019-12-31 | 2021-07-16 | 深圳云天励飞技术有限公司 | Service call tracing method and related product |
| CN111277650A (en) * | 2020-01-20 | 2020-06-12 | 南京航空航天大学 | Automatic micro-service identification method combining functional indexes and non-functional indexes |
| CN111638973A (en) * | 2020-05-11 | 2020-09-08 | 紫光云技术有限公司 | Method for tracing execution sequence of calculation by link |
| CN111625452B (en) * | 2020-05-22 | 2024-04-16 | 上海哔哩哔哩科技有限公司 | Flow playback method and system |
| CN111625452A (en) * | 2020-05-22 | 2020-09-04 | 上海哔哩哔哩科技有限公司 | Flow playback method and system |
| CN111913789A (en) * | 2020-06-29 | 2020-11-10 | 浪潮通用软件有限公司 | Program tracking method, device and medium supporting micro-service architecture |
| CN111984346A (en) * | 2020-08-12 | 2020-11-24 | 八维通科技有限公司 | Method, system, device and storage medium for call chain tracking in micro-service environment |
| CN111984346B (en) * | 2020-08-12 | 2023-10-27 | 八维通科技有限公司 | Method, system, device and storage medium for calling chain tracking in micro-service environment |
| CN112015622A (en) * | 2020-08-24 | 2020-12-01 | 杭州云徙科技有限公司 | Message link tracking and monitoring method and system applied to business middle station |
| CN112187527A (en) * | 2020-09-15 | 2021-01-05 | 中信银行股份有限公司 | Micro-service abnormity positioning method and device, electronic equipment and readable storage medium |
| CN112346856A (en) * | 2020-10-21 | 2021-02-09 | 北京基调网络股份有限公司 | Method, device and equipment for displaying multilink call topology under micro-service architecture |
| CN112311894A (en) * | 2020-11-12 | 2021-02-02 | 北京沃东天骏信息技术有限公司 | Method, apparatus, electronic device, and computer-readable medium for generating information |
| CN112311811A (en) * | 2020-11-16 | 2021-02-02 | 深圳市欢太科技有限公司 | Full link tracking method, device, storage medium and server |
| CN112311811B (en) * | 2020-11-16 | 2022-10-18 | 深圳市欢太科技有限公司 | Full link tracking method, device, storage medium and server |
| CN112532478B (en) * | 2020-11-23 | 2022-05-03 | 华人运通(上海)云计算科技有限公司 | Link relation tracking method, system, checking method, device and equipment |
| CN112532478A (en) * | 2020-11-23 | 2021-03-19 | 华人运通(上海)云计算科技有限公司 | Link relation tracking method, system, viewing method, device, equipment and plug-in |
| WO2022110675A1 (en) * | 2020-11-25 | 2022-06-02 | 平安普惠企业管理有限公司 | Artificial intelligence-based log generation method and apparatus, computer device and medium |
| CN112433757A (en) * | 2020-11-27 | 2021-03-02 | 中国建设银行股份有限公司 | Method and device for determining interface calling relationship |
| US11947439B2 (en) | 2020-11-30 | 2024-04-02 | International Business Machines Corporation | Learning from distributed traces for anomaly detection and root cause analysis |
| CN112416626B (en) * | 2020-12-02 | 2023-06-06 | 中国联合网络通信集团有限公司 | Data processing method and device |
| CN112416626A (en) * | 2020-12-02 | 2021-02-26 | 中国联合网络通信集团有限公司 | Data processing method and device |
| CN112558947B (en) * | 2020-12-18 | 2024-04-05 | 京东科技控股股份有限公司 | Program call tracking method, device and storage medium |
| CN112559212A (en) * | 2020-12-18 | 2021-03-26 | 北京航天云路有限公司 | Service call chain implementation method based on self-research framework |
| CN112558947A (en) * | 2020-12-18 | 2021-03-26 | 京东数字科技控股股份有限公司 | Program call tracing method, device and storage medium |
| CN112612675A (en) * | 2020-12-25 | 2021-04-06 | 山东经伟晟睿数据技术有限公司 | Distributed big data log link tracking method and system under micro-service architecture |
| CN112612675B (en) * | 2020-12-25 | 2023-02-28 | 山东经伟晟睿数据技术有限公司 | Distributed big data log link tracking method and system under micro-service architecture |
| CN112783629A (en) * | 2021-02-01 | 2021-05-11 | 天津五八到家货运服务有限公司 | Service calling method and device, electronic equipment and storage medium |
| CN112988798A (en) * | 2021-03-29 | 2021-06-18 | 成都卫士通信息产业股份有限公司 | Log processing method, device, equipment and medium |
| CN112988798B (en) * | 2021-03-29 | 2023-05-23 | 成都卫士通信息产业股份有限公司 | Log processing method, device, equipment and medium |
| CN113360361A (en) * | 2021-08-11 | 2021-09-07 | 云智慧（北京）科技有限公司 | Method, device and equipment for constructing distributed operation and maintenance simulation system |
| CN113360361B (en) * | 2021-08-11 | 2021-11-23 | 云智慧（北京）科技有限公司 | Method, device and equipment for constructing distributed operation and maintenance simulation system |
| CN113868345B (en) * | 2021-10-11 | 2024-05-28 | 支付宝(杭州)信息技术有限公司 | Method and device for classifying business data in main body |
| CN113868345A (en) * | 2021-10-11 | 2021-12-31 | 支付宝(杭州)信息技术有限公司 | Method and device for carrying out main body classification on business data |
| CN113760778A (en) * | 2021-11-09 | 2021-12-07 | 浙江大学滨海产业技术研究院 | Word vector model-based micro-service interface division evaluation method |
| CN113760778B (en) * | 2021-11-09 | 2022-02-08 | 浙江大学滨海产业技术研究院 | Word vector model-based micro-service interface division evaluation method |
| CN114143369A (en) * | 2021-12-09 | 2022-03-04 | 华人运通(上海)云计算科技有限公司 | Service monitoring system of cloud platform |
| CN114172949A (en) * | 2021-12-10 | 2022-03-11 | 航天信息股份有限公司 | Micro-service link monitoring and tracking method and system |
| CN114003472B (en) * | 2022-01-04 | 2022-04-12 | 连连（杭州）信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114003472A (en) * | 2022-01-04 | 2022-02-01 | 连连（杭州）信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114615521A (en) * | 2022-03-10 | 2022-06-10 | 网易（杭州）网络有限公司 | Video processing method and device, computer readable storage medium and electronic equipment |
| CN114615521B (en) * | 2022-03-10 | 2024-02-23 | 网易（杭州）网络有限公司 | Video processing method and device, computer readable storage medium and electronic equipment |
| CN114745295A (en) * | 2022-04-19 | 2022-07-12 | 京东科技控股股份有限公司 | Data acquisition method, device, equipment and readable storage medium |
| CN115037653B (en) * | 2022-06-28 | 2023-10-13 | 北京奇艺世纪科技有限公司 | Service flow monitoring method, device, electronic equipment and storage medium |
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN117573481A (en) * | 2024-01-15 | 2024-02-20 | 企家有道网络技术(北京)有限公司 | Interface monitoring method, system, electronic device and computer readable storage medium |
| CN117573481B (en) * | 2024-01-15 | 2024-04-30 | 企家有道网络技术(北京)有限公司 | Interface monitoring method, system, electronic device and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109921927A (en) | Real-time calling D-chain trace method based on micro services | |
| CN105224445B (en) | Distributed tracking system | |
| CN110572281B (en) | Credible log recording method and system based on block chain | |
| CN104885077B (en) | Utilize the relation management continuous-query of filing | |
| CN107018042A (en) | Method for tracing and tracing system for online service system | |
| CN112685385A (en) | Big data platform for smart city construction | |
| CN109690524A (en) | Data Serialization in distributed event processing system | |
| CN106709003A (en) | Hadoop-based mass log data processing method | |
| CN106790718A (en) | Service call link analysis method and system | |
| CN105404701A (en) | Peer-to-peer network-based heterogeneous database synchronization method | |
| CN110535722A (en) | A kind of full link operation and monitoring method of the micro services in cross-safety zone domain | |
| CN105993011A (en) | Pattern matching across multiple input data streams | |
| CN108809701A (en) | A kind of data center's wisdom data platform and its implementation | |
| CN108369550B (en) | Real-time alteration of data from different sources | |
| CN103516802A (en) | Method and device for achieving seamless transference of across heterogeneous virtual switch | |
| CN108108459A (en) | Multi-source fusion and the associated dynamic data cleaning method of loop and electronic equipment | |
| Feick et al. | Fundamentals of real-time data processing architectures lambda and kappa | |
| CN107066546A (en) | A kind of across data center method for quickly querying and system based on MPP engines | |
| US11620303B1 (en) | Security essentials and information technology essentials for a data intake and query system | |
| CN106339408A (en) | Data synchronization method, data synchronization device and server | |
| CN107733696A (en) | A kind of machine learning and artificial intelligence application all-in-one dispositions method | |
| CN109977125A (en) | A kind of big data safety analysis plateform system based on network security | |
| CN108573029A (en) | A kind of method, apparatus and storage medium obtaining network access relational data | |
| Wang et al. | Big data in telecommunication operators: data, platform and practices | |
| Preuveneers et al. | Samurai: A streaming multi-tenant context-management architecture for intelligent and scalable internet of things applications |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190621 |