CN114629949B - Service monitoring method, electronic equipment and computer storage medium - Google Patents
Service monitoring method, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN114629949B CN114629949B CN202111523317.XA CN202111523317A CN114629949B CN 114629949 B CN114629949 B CN 114629949B CN 202111523317 A CN202111523317 A CN 202111523317A CN 114629949 B CN114629949 B CN 114629949B
- Authority
- CN
- China
- Prior art keywords
- event
- business
- service
- target
- acquiring
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a service monitoring method, electronic equipment and a computer storage medium. The service monitoring method comprises the following steps: the service monitoring method comprises the following steps: acquiring a database backup log and a target business event of a business system; based on the database backup log, acquiring a business event with a business relation with a target business event and a corresponding business relation; and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship. By the technical scheme, the service circulation link can be accurately tracked and restored.
Description
Technical Field
The present invention relates to the field of service management technologies, and in particular, to a service monitoring method, an electronic device, and a computer storage medium.
Background
The existing service call link tracking tool is mainly used for positioning the processing time spent by each micro service node for processing the service in the synchronous call process under the micro service architecture, and cannot reliably acquire actual service bill information, such as single number, state and the like, and cannot accurately acquire the conditions of splitting, code conversion and the like of the bill in the circulation process, and cannot accurately describe the service flow (service circulation link).
Disclosure of Invention
The technical problem that this application mainly solves is to provide a business monitoring method, electronic equipment and computer storage medium to can accurate track and restore the business circulation link.
In order to solve the technical problems, one technical scheme adopted by the application is as follows: a service monitoring method is provided. The service monitoring method comprises the following steps: acquiring a database backup log and a target business event of a business system; based on the database backup log, acquiring a business event with a business relation with a target business event and a corresponding business relation; and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship.
In order to solve the technical problems, one technical scheme adopted by the application is as follows: an electronic device is provided. The electronic device comprises a memory and a processor coupled to each other, the processor being configured to execute program data stored in the memory to implement the traffic monitoring method of any of the above.
In order to solve the technical problems, one technical scheme adopted by the application is as follows: a computer storage medium is provided. The computer storage medium has stored thereon program data that can be executed to implement any of the traffic monitoring methods described above.
The beneficial effects of the embodiment of the application are that: the service monitoring method comprises the following steps: acquiring a database backup log and a target business event of a business system; based on the database backup log, acquiring a business event with a business relation with a target business event and a corresponding business relation; and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship. According to the technical scheme, the service event and the corresponding service relation related to the target service event are acquired based on the database backup log, the service circulation information can be acquired in a non-invasive manner, the completeness and the reliability of the information are guaranteed, the service circulation link of the target service event is determined by utilizing the target service event, the service event and the corresponding service relation, and the service circulation link of the target service event can be accurately restored. Therefore, the method and the device can accurately track and restore the service circulation link.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an embodiment of a method for traffic monitoring in the present application;
FIG. 2 is a schematic diagram showing a specific flow of step S12 in the embodiment of FIG. 1;
FIG. 3 is a schematic diagram showing a specific flow of step S22 in the embodiment of FIG. 2;
FIG. 4 is a flow chart of an embodiment of a method for traffic monitoring in the present application;
FIG. 5 is a flow chart of an embodiment of a method for traffic monitoring of the present application;
FIG. 6 is a flow chart of an embodiment of a method for traffic monitoring of the present application;
FIG. 7 is a schematic diagram illustrating the structure of an embodiment of a business flow template of the present application;
FIG. 8 is a flow chart of an embodiment of a method for traffic monitoring of the present application;
FIG. 9 is a schematic diagram of an embodiment of an electronic device of the present application;
FIG. 10 is a schematic diagram of an embodiment of a computer storage medium of the present application.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is specifically noted that the following examples are only for illustration of the present application, but do not limit the scope of the present application. Likewise, the following embodiments are only some, but not all, of the embodiments of the present application, and all other embodiments obtained by one of ordinary skill in the art without inventive effort are within the scope of the present application.
In the description of the embodiments of the present application, it should be noted that, unless explicitly specified and limited otherwise, the terms "connected," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium. The specific meaning of the terms in the embodiments of the present application will be understood by those of ordinary skill in the art in a specific context.
In the examples herein, a first feature "on" or "under" a second feature may be either the first and second features in direct contact, or the first and second features in indirect contact via an intermediary, unless expressly stated and defined otherwise. Moreover, a first feature being "above," "over" and "on" a second feature may be a first feature being directly above or obliquely above the second feature, or simply indicating that the first feature is level higher than the second feature. The first feature being "under", "below" and "beneath" the second feature may be the first feature being directly under or obliquely below the second feature, or simply indicating that the first feature is less level than the second feature.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
The present application first proposes a service monitoring method, as shown in fig. 1, and fig. 1 is a schematic flow chart of an embodiment of the service monitoring method of the present application. The service monitoring method specifically comprises the following steps:
step S11: and acquiring a database backup log and a target business event of the business system.
A service system may be used in a micro-service framework having a plurality of service units, i.e. a plurality of service nodes, and a service request is usually completed by executing corresponding service events (service logic) through the plurality of service nodes, respectively.
The database backup log in this embodiment is a local log of the service system, and log information of the operation of the whole service system is recorded. When executing business logic, the application program of the business system can cause the change of the data in the database, and at the moment, corresponding database backup logs can be generated. Modifications to the database submitted by the application will also result in the database generating a new binlog to synchronize the database modifications to the database backup nodes, generating corresponding database backup logs.
In the embodiment, tools such as alibaba signal and oracle dataguard can be used for respectively collecting database backup logs generated by databases such as mysql and oracle; further, after the database backup log is converted into json format, a kafka platform or the like is written. Among other things, kafka is a high-throughput distributed publish-subscribe messaging system that can handle all action flow data for consumers.
Of course, in other embodiments, the log file collection tool, database type, and distributed publish-subscribe messaging system described above may not be limiting.
The collection of the database backup logs is thoroughly non-invasive to the application program, so that the completeness and reliability of the service information source can be ensured.
Step S12: based on the database backup log, acquiring the business event with business relation with the target business event and the corresponding business relation.
The target business event can be configured according to the selection of the user, and in business logic containing the target business event, other business events have direct or indirect business relation with the target business event; the direct business relationship refers to direct circulation before the two, and the indirect business relationship refers to circulation between the two through other business events. A business relationship is a tie that connects two business events.
Alternatively, the present embodiment may implement step S12 by a method as shown in fig. 2. The method of the present embodiment includes step S21 and step S22.
Step S21: and acquiring a first message corresponding to the target business event from the database backup log.
When the application program executes the business logic, a database backup log in the form of a message is generated every time the data is changed.
Specifically, data cleaning is performed on the database backup log based on a preset cleaning rule so as to obtain a first message corresponding to the target business event.
In the embodiment, the method can adopt the Flink to clean the message flow of the backup log of the database in the message flow queue kafka in real time; the cleansing rules may be configured online by the operation and maintenance/operator and the Flink will update the cleansing rules at regular time.
The Apache Flink, abbreviated as Flink, is an open source stream processing framework developed by Apache software foundation, and the core is a distributed stream data stream engine written by Java and Scala. The Flink executes any stream data program in a data parallel and pipeline manner, and the pipeline runtime system of the Flink can execute batch processing and stream processing programs. Furthermore, the Flink runtime itself also supports the execution of iterative algorithms. The memory processing and the pipeline mode are applied to the scene of on-line real-time processing, and can provide the capability of real-time processing for the service.
For example, the operation and maintenance/operator may specify that the target business event "business event a" be purged from the relevant log of table_a; the "biz_id" field content of the table_a is used as an "event code" of the "service event a", the "status" field content is used as an "event state" of the "service event a", and the "update_by" field content is used as a "sponsor" of the "service event a", namely, associated service events; and a new message of "business event a" may be configured to be generated only when the data line "insert" (insert data) or "update" (update) of the table_a field is updated. The default message generation time is the event generation time. The specific time of each state change of a business logic or business event can be accurately collected by cleaning the database backup log.
The first message corresponding to the target service event obtained from the database backup log includes the event code, the event state, the associated service event (the upstream and downstream service events of the target service event), the service relationship with the associated service event, and each time node of the target service event.
Step S22: a first business event associated with a target business event and a first business relationship between the first business event and the target business event are acquired from a first message.
When two different and related business events (identifiable by event coding) occur in the same message, the business relationship between the two can be collected from the message. Therefore, the first business event associated with the target business event and the first business relationship between the first business event and the target business event can be obtained from the first message, wherein the first business event is a business event with a direct business relationship with the target business event.
The first business relation of the implementation comprises a business circulation relation, a circulation path between business logic executing nodes is embodied, the business logic executing nodes can be understood as an upstream-downstream relation between business events, and the first business relation also comprises information such as time of business event circulation, business event state change and the like.
Alternatively, the present embodiment may implement step S22 by a method as shown in fig. 3. The method of the present embodiment includes steps S31 to S33.
Step S31: an event code of a target business event and a first event code of a first business event are obtained.
From the above analysis, the first message includes the event code of the target service event and the first event code of the first service event. And different business events may have the same business code, such as the case of disassembly, assembly, document rework, etc., and different business events may be generated for the same business code.
Step S32: and responding to the event code being the same as the first event code, acquiring a service switching relation between the target service event and the first service event, and taking the service switching relation as a first service relation between the target service event and the first service event.
If the event code is different from the first event code, the service logic node corresponding to the target service event and the first service event is considered to be converted, the service switching relation between the target service event and the first service event is obtained, and the service switching relation is used as a first service relation between the target service event and the first service event.
Step S33: and responding to the event code being different from the first event code, acquiring a switching relation between the event state of the target business event and the event state of the first business event, and taking the switching relation as the first business relation between the event state of the target business event and the event state of the first business event.
If the event code is the same as the first event code, the target service event and the first service event are considered to be generated by the conditions of form disassembly, form combination, document rework and the like, belong to the same service logic node, the service relationship between the two service logic nodes, and the switching relationship is used as the switching relationship before the two service logic nodes, so that the complex service logic of the conditions of form disassembly, form combination, document rework and the like can be embodied.
The step S21 and the step S22 can obtain the service event and the corresponding service relationship of the target service event having the direct service relationship.
Optionally, the method of the embodiment of fig. 2 further includes step S23 and step S24.
Step S23: and obtaining a second message corresponding to the first business event from at least the database backup log.
Specifically, data cleaning is performed on the database backup log based on the first business event so as to obtain a second message corresponding to the first business event; the embodiment can use the Flink to clean the message flow of the database backup log in the message flow queue kafka in real time. A specific cleaning method may participate in step S21 described above.
Further, the database backup log is subjected to data cleaning based on the second business event so as to obtain a third message corresponding to the second business event, and the like, so that other business events which have direct or indirect relation with the target business event can be obtained.
Step S24: and acquiring a second business event associated with the first business event and a second business relationship between the second business event and the first business event from at least the second message.
When two different and related business events (identifiable by event codes) occur in the same second message, the business relationship between the two, i.e., the second business relationship, may be collected from the second message.
Further, a third business event associated with the second business event and a third business relationship between the second business event are acquired from the third message, and so on, so that other business events and corresponding business relationships (business relationships between every two business events) which have direct or indirect relationships with the target business event can be acquired.
Step S24 may be specifically implemented by using the method shown in fig. 3, which is not described herein.
The step S23 and the step S24 can obtain the business event and the corresponding business relationship with the target business event having an indirect business relationship in the whole business circulation link including the target business event.
The washed business event flows into a real-time alarm processing module and is stored into a distributed column storage database clickhouse; and (3) cleaning out the service relation, directly storing clickhouse for subsequent generation and restoration of the display service flow link.
Step S13: and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship.
And concatenating the washed business events corresponding to the target business events according to the corresponding business relationship to form a business circulation link containing the target business events.
Compared with the prior art, the method and the device are different from the prior art, the service event related to the target service event and the corresponding service relationship are acquired based on the database backup log, the service circulation information can be acquired in a non-invasive manner, the completeness and the reliability of the information are guaranteed, the service circulation link of the target service event is determined by utilizing the target service event, the service event and the corresponding service relationship, and the service circulation link of the target service event can be accurately restored. Therefore, the embodiment can accurately track and restore the service circulation link.
The application further proposes a service monitoring method of another embodiment, as shown in fig. 4, where the service monitoring method specifically includes the following steps:
step S41: and acquiring a database backup log and a target business event of the business system, and acquiring link monitoring information of the business system.
The method for obtaining the database backup log of the service system and the target service event may refer to step S11, which is not described herein.
The application program calls the service link tracking tool and outputs link monitoring information such as service input, output, response time, sql and the like in the execution process of service logic, so that the service link tracking tool not only can assist developers in positioning on-line problems, but also can be used as a supplementary data source of the database backup log so as to improve the completeness and reliability of data.
The link monitoring information generated by the service link tracking tool (customizing enhanced skywalking/zip support for collecting http request/response body) is directly sent or indirectly circulated into the kafka, so that the subsequent data cleaning is facilitated.
Step S42: and acquiring the business event with the business relation with the target business event and the corresponding business relation based on the database backup log and the link monitoring information.
The database backup log and the link monitoring information describe the data of the real-time processing result of the application program from different angles, and the data are collected into the message circulation queue kafka in real time; adopting a Flink to clean the message flow of the database backup log in the message flow queue kafka in real time and the message flow of the link monitoring information; the cleansing rules may be configured online by the operation and maintenance/operator and the Flink will update the cleansing rules at regular time.
For example, when the link monitoring information is purged, the configuration may be such that when the "url" and "httpStatus" fields are all equal to the specified values, and when the content is matched from the "responseBody" field by using the regular expression, the matched content is recorded under the event code of the business event.
The specific embodiment of step S42 may refer to step S22 described above, and is not described herein.
Step S43: and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship.
Step S43 is similar to step S13 described above, and is not repeated here.
On the basis of the above embodiment, the present embodiment invokes the service link tracking tool to acquire monitoring information for tracking the service link of the service system, and uses the monitoring information as a supplementary data source of the database backup log, so as to improve the completeness and reliability of data, and further improve the accuracy of the subsequently generated and restored service circulation link.
The application further proposes a service monitoring method of another embodiment, as shown in fig. 5, where the service monitoring method specifically includes the following steps:
step S51: and acquiring a database backup log and a target business event of the business system, and acquiring link monitoring information of the business system and an operation log of the business system.
The method for obtaining the database backup log of the service system and the target service event, and the method for obtaining the link monitoring information of the service system can refer to step S41, which is not described herein.
When the application program executes the business logic, the running log of the system is printed on a local disk, so that the system is used for assisting a developer in positioning the system problem, and is also used as a supplementary data source for backup log and monitoring information of a database so as to improve the completeness and reliability of data.
The log file collection tool filecoat can be used for collecting the operation log from each server into the message flow queue kafka, so that subsequent data cleaning is facilitated.
Step S52: and acquiring the business event with the business relation with the target business event and the corresponding business relation based on the database backup log, the link monitoring information and the operation log.
Three types of data describing real-time processing results of the application program from different angles, namely database backup logs, link monitoring information and running logs, are all collected into a message circulation queue kafka in real time; adopting a Flink to clean the message flow of the database backup log in the message flow queue kafka in real time and the message flow of the link monitoring information; the cleansing rules may be configured online by the operation and maintenance/operator and the Flink will update the cleansing rules at regular time.
For example, when the running log of the service system is cleaned, the running log can be configured to record the generation of a certain abnormal/critical service event when the 'log_name' field and the 'level' field are equal to the specified values and when the content is matched from the 'message' field by using the regular expression.
The specific embodiment of step S52 can refer to the above steps S22 and S42, which are not described herein.
Step S53: and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship.
Step S53 is similar to step S13 described above, and is not repeated here.
Based on the above embodiments, the present embodiment uses the running log of the service system as the supplementary data source of the backup log of the database, and the collection of the running log is completely non-invasive to the application program, so that the completeness and reliability of the data can be improved, and the accuracy of the subsequently generated and restored service circulation links can be further improved.
Of course, in other embodiments, only the running log of the business system may be selected as the supplemental data source for the database backup log described above.
The application further proposes a service monitoring method of another embodiment, as shown in fig. 6, where the service monitoring method specifically includes the following steps:
step S61: and acquiring a database backup log and a target business event of the business system.
Step S62: based on the database backup log, acquiring the business event with business relation with the target business event and the corresponding business relation.
Step S63: and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship.
Steps S61 to S63 are similar to steps S11 to S13 described above, and are not repeated here.
Step S64: the traffic flow links are configured as link flow templates.
The steps are used for connecting the business event and the business relationship in series to form a business circulation link, and related data are stored in a distributed type list database such as a clickhouse and the like for drawing the business circulation link.
When drawing the service circulation link, firstly configuring the above-mentioned service circulation link with a bit link circulation template, i.e. templating service event and service relation. Each template node of the link circulation template corresponds to a corresponding service event, and if the same event code is not used between the two upstream and downstream template nodes, the corresponding service relationship needs to be configured on the connecting line before the two template nodes.
If two template nodes use the same event code, the switching relation of the event state can be configured on the connecting line before the two template nodes.
Step S65: obtaining a search instruction, obtaining a target event code from the search instruction, and obtaining a target business event corresponding to the target event code.
Step S66: and acquiring a link circulation template containing the target business event.
Step S67: and acquiring all business events and all business relations in the link circulation template.
Steps S65 to S67 are to draw and display the service circulation link based on the search instruction.
For example, a user may provide a service document code, i.e., a target event code, to query the document for a complete service flow link between different systems of different modules. Specifically, firstly searching the business event matched with the business document code; then, searching a circulation link template configured by the business event; then backtracking to the initial business event at the most upstream of the circulation link template, performing code conversion according to the business relationship in the backtracking process, and finally positioning the business document code of the initial business event; and finally, traversing the whole directed acyclic graph from the top to the bottom of the initial business event, and displaying all the business events, business relations and other relevant information on the whole directed acyclic graph. If the same business document code is used for collecting different business event records of a plurality of processing states, only the latest processing state is displayed. And when the downstream business event cannot be found, stopping drawing if the downstream business event is proved to not occur.
As shown in fig. 7, the circulation link template includes 7 service events, the service event a and the service event B have the same event code, the service event a, the service event B and the service event C have the same event code, the service relationship between the service event 1 and the service event B is the service relationship 1, the service relationship between the service event B and the service event a is the service relationship 3, and the service relationship between the service event 2 and the service event B is the service relationship 2.
The embodiment not only can collect service circulation information in a non-invasive way and ensure the completeness and reliability of the information, but also can describe complex service logics such as bill disassembly, bill combination, manual asynchronous processing, service detention, bill rework and the like, and further can accurately and finely restore a service circulation link.
Similar modifications can be made to the other embodiments described above, and are not repeated here.
In another embodiment, as shown in fig. 8, service processing is submitted according to a request, and an operation log and link monitoring information of a service system are printed; then collecting the operation log, monitoring information and the message record of the database backup log; then extracting a business event and a corresponding business relationship which have a direct business relationship with a target business event based on a data cleaning rule, and analogizing the business event and the corresponding business relationship which have an indirect business relationship with the target business event; and finally, restoring the whole business circulation link containing the target business event according to the input business document number: finding a service event according to the document code, and then determining a node of the service event in a service flow template; then backtracking to an initial node in the business circulation template according to the business relation in the business circulation template; traversing the flow branches downwards from the initial node, acquiring the state change process of the node, and acquiring and displaying the lower-level business flow; and acquiring the completed service flow link.
Meanwhile, failure business events and successful business events can be counted, and trend change amplitude is calculated by comparing two counting periods; then identifying the diapause business event which does not enter a success or failure state for a long time, triggering the alarm and converging the frequent alarm, and sending the alarm according to the cooperation of sponsors and the alarm group, wherein the alarm can be sent in a mode of short message, weChat or mail, etc.
In an application scenario, the business event may include business value information, and the reconciliation logic may be converted into whether the value aggregate of two different events in a period is consistent or not through the business relationship; by means of sampling, two event codes of a business relation are determined to correspond to the business events respectively, the event codes on the side are determined to be upstream event codes, and then a business circulation link of a bill is drawn automatically under the condition that a circulation template is not configured.
The application further provides an electronic device, as shown in fig. 9, and fig. 9 is a schematic structural diagram of an embodiment of the electronic device. Electronic device 80 of the present embodiment includes a processor 81, a memory 82, an input-output device 83, and a bus 84.
The processor 81, the memory 82, and the input/output device 83 are respectively connected to the bus 84, and the memory 82 stores program data, and the processor 81 is configured to execute the program data to implement the service monitoring method of the foregoing embodiment.
In the present embodiment, the processor 81 may also be referred to as a CPU (Central Processing Unit ). The processor 81 may be an integrated circuit chip with signal processing capabilities. Processor 81 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The general purpose processor may be a microprocessor or the processor 81 may be any conventional processor or the like.
The present application further proposes a computer readable storage medium, as shown in fig. 10, where the computer readable storage medium 160 of the present embodiment is configured to store the program data 161 of the above embodiment, and the program data 161 can be executed to implement the above service monitoring method. The program data 161 are described in detail in the above method embodiments, and are not described here again.
The computer readable storage medium 160 of the present embodiment may be, but is not limited to, a usb disk, an SD card, a PD optical drive, a mobile hard disk, a high capacity floppy drive, a flash memory, a multimedia memory card, a server, etc.
Different from the prior art, the service monitoring method comprises the following steps: acquiring a database backup log and a target business event of a business system; based on the database backup log, acquiring a business event with a business relation with a target business event and a corresponding business relation; and determining a service circulation link of the target service event based on the target service event, the service event and the corresponding service relationship. According to the technical scheme, the service event and the corresponding service relation related to the target service event are acquired based on the database backup log, the service circulation information can be acquired in a non-invasive manner, the completeness and the reliability of the information are guaranteed, the service circulation link of the target service event is determined by utilizing the target service event, the service event and the corresponding service relation, and the service circulation link of the target service event can be accurately restored. Therefore, the method and the device can accurately track and restore the service circulation link.
In addition, the above-described functions, if implemented in the form of software functions and sold or used as a separate product, may be stored in a mobile terminal-readable storage medium, that is, the present application also provides a storage device storing program data that can be executed to implement the method of the above-described embodiment, the storage device may be, for example, a U-disk, an optical disk, a server, or the like. That is, the present application may be embodied in a software product that includes instructions for causing a smart terminal to perform all or part of the steps of the methods described in the various embodiments.
In the description of the present application, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, mechanism, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, mechanisms, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "plurality" is at least two, such as two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing mechanisms, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., may be considered as a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device (which can be a personal computer, server, network device, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions). For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
The foregoing description is only of embodiments of the present application, and is not intended to limit the scope of the patent application, and all equivalent mechanisms or equivalent process changes made by the specification and the drawings of the present application, or direct or indirect application in other related technical fields, are equally included in the scope of the patent protection of the present application.
Claims (8)
1. A method for monitoring traffic, comprising:
acquiring a database backup log and a target business event of a business system;
acquiring a business event with a business relationship with the target business event and a corresponding business relationship based on the database backup log;
determining a business circulation link of the target business event based on the target business event, the business event and the corresponding business relationship;
wherein, based on the database backup log, the obtaining the service event having the service relationship with the target service event and the corresponding service relationship includes:
non-invasively acquiring a first message corresponding to the target business event from a change log of the database backup log;
acquiring a first business event associated with the target business event and a first business relationship between the first business event and the target business event from the first message;
wherein, based on the database backup log, obtaining the service event and the corresponding service relationship with the service relationship of the target service event further includes:
non-invasively obtaining a second message corresponding to the first business event from at least a change log of the database backup log;
and acquiring a second business event associated with the first business event and a second business relationship between the second business event and the first business event from at least the second message.
2. The method of claim 1, wherein the obtaining, from the first message, the first business event associated with the target business event and the first business relationship therebetween comprises:
acquiring an event code of the target business event and a first event code of the first business event;
responding to the event code being the same as the first event code, acquiring a service switching relation between the target service event and the first service event, and taking the service switching relation as a first service relation between the target service event and the first service event;
and responding to the event code being different from the first event code, acquiring a switching relation between the event state of the target business event and the event state of the first business event, and taking the switching relation as a first business relation between the event state of the target business event and the event state of the first business event.
3. The traffic monitoring method according to claim 1, further comprising:
acquiring link monitoring information of the service system;
the obtaining the service event and the corresponding service relationship with the service relationship of the target service event based on the database backup log comprises:
and acquiring a business event with a business relationship with the target business event and a corresponding business relationship based on the database backup log and the link monitoring information.
4. The traffic monitoring method according to claim 1, further comprising:
acquiring an operation log of the service system;
the obtaining the service event and the corresponding service relationship with the service relationship of the target service event based on the database backup log comprises:
and acquiring the business event with the business relation with the target business event and the corresponding business relation based on the database backup log and the operation log.
5. The traffic monitoring method according to claim 1, further comprising:
configuring the service circulation link as a link circulation template;
acquiring a search instruction, acquiring a target event code from the search instruction, and acquiring the target business event corresponding to the target event code;
acquiring the link circulation template containing the target business event;
and acquiring all the business events and all the business relations in the link circulation template.
6. The method of claim 1, wherein the obtaining a first message corresponding to the target business event from the database backup log comprises:
and cleaning the data of the database backup log based on a preset cleaning rule to acquire a first message corresponding to the target business event.
7. An electronic device comprising a memory and a processor coupled to each other, the processor configured to execute program data stored in the memory to implement the traffic monitoring method of any of claims 1 to 6.
8. A computer storage medium having stored thereon program data executable to implement the traffic monitoring method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111523317.XA CN114629949B (en) | 2021-12-13 | 2021-12-13 | Service monitoring method, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111523317.XA CN114629949B (en) | 2021-12-13 | 2021-12-13 | Service monitoring method, electronic equipment and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114629949A CN114629949A (en) | 2022-06-14 |
| CN114629949B true CN114629949B (en) | 2023-06-02 |
Family
ID=81897845
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111523317.XA Active CN114629949B (en) | 2021-12-13 | 2021-12-13 | Service monitoring method, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114629949B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115757303B (en) * | 2022-11-14 | 2024-05-03 | 华青融天(北京)软件股份有限公司 | Index tracking method and device in distributed system |
| CN116185767B (en) * | 2023-02-02 | 2024-04-19 | 广东为辰信息科技有限公司 | Method for monitoring data flow direction based on encryption technology |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8108234B2 (en) * | 2007-03-13 | 2012-01-31 | Sap Ag | System and method for deriving business processes |
| CN108647220B (en) * | 2018-03-19 | 2022-04-08 | 南京理工大学 | Scientific workflow mining method based on event indirect prior relationship |
| CN110333983A (en) * | 2019-05-31 | 2019-10-15 | 口口相传(北京)网络技术有限公司 | Business monitoring and searching service monitoring method and device |
| CN112559513A (en) * | 2019-09-10 | 2021-03-26 | 网易（杭州）网络有限公司 | Link data access method, device, storage medium, processor and electronic device |
| CN113760641A (en) * | 2021-01-08 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Service monitoring method, device, computer system and computer readable storage medium |
| CN113157659A (en) * | 2021-05-14 | 2021-07-23 | 中国建设银行股份有限公司 | Log processing method and device |
-
2021
- 2021-12-13 CN CN202111523317.XA patent/CN114629949B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN114629949A (en) | 2022-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114629949B (en) | Service monitoring method, electronic equipment and computer storage medium | |
| CN111241078B (en) | Data analysis system, data analysis method and device | |
| CN110661659B (en) | Alarm method, device and system and electronic equipment | |
| CN106656536B (en) | Method and equipment for processing service calling information | |
| CN110516971B (en) | Anomaly detection method, device, medium and computing equipment | |
| Klemettinen et al. | Rule discovery in telecommunication alarm data | |
| US7681182B1 (en) | Including function call graphs (FCG) generated from trace analysis data within a searchable problem determination knowledge base | |
| US20160026950A1 (en) | Monitoring transactions from distributed applications and using selective metrics | |
| CN111782486A (en) | Alarm implementation method and system based on dynamic configuration | |
| CN111008105A (en) | Distributed system call relation visualization method and device | |
| CN109462507B (en) | Configuration updating method, device and system and electronic equipment | |
| CN112685370A (en) | Log collection method, device, equipment and medium | |
| US20230376372A1 (en) | Multi-modality root cause localization for cloud computing systems | |
| Zeng et al. | Traceark: Towards actionable performance anomaly alerting for online service systems | |
| CN112087320A (en) | Abnormity positioning method and device, electronic equipment and readable storage medium | |
| CN111865673A (en) | Automatic fault management method, device and system | |
| CN106649000A (en) | Fault recovery method for real-time processing engine, and corresponding server | |
| CN112579552A (en) | Log storage and calling method, device and system | |
| CN117389792A (en) | Fault checking method and device, storage medium and electronic equipment | |
| CN115580528A (en) | Fault root cause positioning method, device, equipment and readable storage medium | |
| CN116010244A (en) | Automatic test method, device, electronic equipment and storage medium | |
| CN113918204A (en) | Metadata script management method and device, electronic equipment and storage medium | |
| CN113934595A (en) | Data analysis method and system, storage medium and electronic terminal | |
| CN112597119A (en) | Method and device for generating processing log and storage medium | |
| KR20220069229A (en) | The method of coupling with heterogeneous data using relation of fields in data |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |