CN110968479A

CN110968479A - Business-level full-link monitoring method for application program and server

Info

Publication number: CN110968479A
Application number: CN201911154782.3A
Authority: CN
Inventors: 易存道
Original assignee: Beijing Baolande Software Co ltd
Current assignee: Beijing Baolande Software Co ltd
Priority date: 2019-11-20
Filing date: 2019-11-20
Publication date: 2020-04-07
Anticipated expiration: 2039-11-20
Also published as: CN110968479B

Abstract

The embodiment of the invention provides a service-level full-link monitoring method and a server for an application program, wherein the method comprises the following steps: the monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and further obtains full-link request monitoring information of a full-link transaction chain; receiving a monitoring information viewing request of a monitoring client side including a service label; and acquiring a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sending the monitoring information result to the monitoring client. According to the service-level full-link monitoring method and the server for the application program, the corresponding monitoring information result is obtained according to the service label, the stored service relation model and the full-link request monitoring information, so that the corresponding monitoring information result is obtained according to the service type specified by the monitoring information checking request, and the service-level full-link monitoring is realized.

Description

Business-level full-link monitoring method for application program and server

Technical Field

The invention relates to the technical field of computers, in particular to a service-level full-link monitoring method and a server for an application program.

Background

The full link monitoring of the application program can be realized through various modes such as network flow monitoring and application code injection. The full link monitoring is a request-based monitoring and tracking technology, and is characterized in that all subsequent sub-requests directly and indirectly initiated by an entrance request are connected in series from the entrance request, and the request content, time consumption and other information of each request step are recorded. Therefore, the experience management, the transaction full-path monitoring, the end-to-end performance analysis, the anomaly analysis, the fault positioning and the like of a real user can be accurately carried out.

Full link monitoring is request-based, while requests are application instance-based, and the basis for full link monitoring is based on request concatenation. Request level monitoring expresses a request which subsequent requests are raised and may be represented by a comparison of the underlying views. On the basis of a request level, requests are aggregated through a service instance to form a relatively high-level view, instance level monitoring is achieved, and it can be expressed that one service instance depends on other service instances. The request contains a service target, for example: the two pieces of information, IP and port, express which instance handles the service. However, since the service is complex, the requests are thousands of requests, and the subsequent requests caused by different request parameters are different. Also, enterprise-level systems tend to be clustered, and the same request, and subsequent requests that it initiates, may not always fall on the same instance, resulting in a change in the IP and port of the request. To sum up, if a tree diagram is made based on a request, the user is not aware of the tree diagram and a large number of trees are obtained. The most primitive data that is requested at a time is true, but is not useful for analyzing problems.

It can be seen that the current full link monitoring technology can only achieve request level monitoring and instance level monitoring, both of which face the problem of cluster environment service instance change, and cannot enable full link monitoring to express a service concept well and achieve service level monitoring. Therefore, how to convert the request monitoring of a large number of instances into service level monitoring which can be understood and focused by users becomes a central part of modern monitoring schemes.

Disclosure of Invention

In order to solve the problems in the prior art, embodiments of the present invention provide a service-level full link monitoring method for an application program and a server.

In a first aspect, an embodiment of the present invention provides a method for monitoring a service-level full link for an application, including: the method comprises the steps that a monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relation between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs; the monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag; the monitoring server acquires a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sends the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

Further, the request monitoring information also carries a full link transaction chain identifier, where the full link transaction chain identifier includes information of the full link transaction chain to which the local transaction chain belongs and a position relationship of the local transaction chain in the full link transaction chain; the acquiring the full link request monitoring information of the full link transaction chain by integrating the request monitoring information according to the relationship between the request monitoring information comprises the following steps: and integrating the request monitoring information according to the full link transaction chain identifier to obtain the full link request monitoring information.

Further, the monitoring information result includes a service-level application access relationship view, and the monitoring server obtains a corresponding monitoring information result according to the service tag, the stored service relationship model, and the full-link request monitoring information, which specifically includes: the monitoring server acquires the instance identifier corresponding to the service label in the service relation model according to the service label; acquiring corresponding request monitoring information according to the instance identifier, and acquiring access relations among the instances corresponding to the application servers according to the full-link transaction chain identifier and the request time identifier carried by the request monitoring information; acquiring the access relation between the applications to which each instance belongs according to the access relation between the instances and the service label; obtaining the business level application access relation view according to the access relation between the applications to which the instances belong; and each application in the business-level application access relation view is represented by an application icon.

Further, the request monitoring information also carries information of the application server, and the method further includes: if the click information of the application icon is received, acquiring an application deployment relationship topological view of the application corresponding to the application icon according to the service relationship model and the full-link request monitoring information, and adding the application deployment relationship topological view to the monitoring information result; the application deployment relationship topology view comprises relationship information of the application corresponding to the clicked application icon in the full-link request monitoring information, the instance contained in the application and the application server to which the instance belongs, and the application, the instance and the application server are respectively represented by the application icon, the instance icon and the application server icon.

Further, the monitoring server presets whether the service corresponding to the service tag is a key service; for the key service, a service step contained in the key service and a request list of the request contained in the service step are stored in advance, and the request in the request list is represented by the request identifier; after the monitoring server obtains a corresponding monitoring information result according to the service label, the stored service relationship model and the full link request monitoring information, the method further comprises: if the service corresponding to the service tag is judged and known to be the key service, acquiring a key service monitoring view of the key service, and adding the key service monitoring view to the monitoring information result; the key service monitoring view comprises a first view formed by sequentially connecting icons according to the service steps in the key service, and a second view comprising statistical information obtained by performing statistics according to the request monitoring information of the request contained in the key service.

Further, the method further comprises: respectively acquiring the request monitoring information of the request contained in the application corresponding to the application icon, the example corresponding to the example icon and the business step corresponding to the step icon, respectively acquiring the application health states of the application, the example and the business step according to the request monitoring information, and displaying the application health states by using the colors of the application icon, the example icon and the step icon; and displaying the running health state corresponding to the application server by using the color of the application server icon in the application deployment relationship topological view.

Further, the method further comprises: if the service corresponding to the service label is the key service, setting a switching label for displaying the key service monitoring view in the service level application access relation view; associating the application icon, the instance icon and the application server icon in the application deployment relationship topological view with the monitoring detail information of the corresponding application, the instance and the application server respectively; and associating the step icon in the key service monitoring view with the corresponding request list.

In a second aspect, an embodiment of the present invention provides a monitoring server, including:

the full link monitoring data acquisition module is used for: receiving request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrating the request monitoring information according to the relationship between the request monitoring information to obtain full-link request monitoring information of the full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs;

a monitoring information viewing request receiving module, configured to: receiving a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag;

the monitoring information result acquiring and sending module is used for: acquiring a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sending the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

In a third aspect, an embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method provided in the first aspect when executing the computer program.

In a fourth aspect, an embodiment of the present invention provides a non-transitory computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the method as provided in the first aspect.

According to the service-level full-link monitoring method and the server for the application program, the corresponding monitoring information result is obtained according to the service label, the stored service relation model and the full-link request monitoring information, so that the corresponding monitoring information result is obtained according to the service type specified by the monitoring information checking request, and the service-level full-link monitoring is realized.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a flowchart of a service-level full link monitoring method for an application according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a service relationship model in a service-level full-link monitoring method for an application according to an embodiment of the present invention;

fig. 3 is a schematic diagram illustrating a process of acquiring full-link request monitoring information in a service-level full-link monitoring method for an application according to an embodiment of the present invention;

FIG. 4 is an exemplary diagram of critical traffic in a traffic level full link monitoring method for an application according to an embodiment of the present invention;

fig. 5 is an exemplary diagram of a service-level application access relationship view in a service-level full-link monitoring method for an application according to an embodiment of the present invention;

fig. 6 is an exemplary diagram of a topology view of an application deployment relationship in a service-level full-link monitoring method for an application according to an embodiment of the present invention;

fig. 7 is an exemplary diagram of a first view of a critical traffic monitoring view in a traffic level full link monitoring method for an application according to an embodiment of the present invention;

fig. 8 is an exemplary diagram of a second view of a critical traffic monitoring view in a traffic level full link monitoring method for an application according to an embodiment of the present invention;

fig. 9 is a flowchart of a method for monitoring a service-level full link for an application according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a monitoring server according to an embodiment of the present invention;

fig. 11 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a flowchart of a service-level full link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 1, the method includes:

step 101, a monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relationship between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain; the request monitoring information is obtained by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time when the request occurs, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs.

The monitoring server is a background server for implementing the service-level full-link monitoring method for the application program provided by the embodiment of the invention. The application server is used to run an instance of the application to be monitored. The application program to be monitored can realize corresponding functions by a plurality of instances together. In addition, the same instance can be deployed on a plurality of application servers, and the security is improved in a cluster deployment mode.

The monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relation between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain. The local transaction chain refers to a chain of transaction steps in the running process of the instance of the application server. One request may trigger multiple transaction steps. The local transaction chain generated by each instance running can be attributed to a full link transaction chain, so that more functions can be realized through the cooperative cooperation of a plurality of instances.

The application server may set in advance a full link transaction chain to which a local transaction chain generated by instance operation belongs and a position relationship in the full link transaction chain, and the request monitoring information is uploaded while carrying the information, so that the monitoring server can acquire the relationship between the request monitoring information, and thus, the request monitoring information is integrated according to the relationship between the request monitoring information to obtain the full link request monitoring information of the full link transaction chain.

The request monitoring information is acquired by the application server in an instance process, and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, so that the request time identifier can identify the sequence of the request; the request identification is used for distinguishing the request; the instance identifier is used to identify the instance to which the request belongs, and may generally represent the request uploaded by which application server.

102, the monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag.

The monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service label. The service label may be a certain service label in a service relation model stored by the monitoring server.

103, the monitoring server obtains a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sends the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

The monitoring server stores a business relation model in advance, the business labels are respectively arranged on preset applications and examples contained in the applications in the business relation model, and the application identifiers and the example identifiers are respectively arranged on the applications and the examples. The instance and the application to which the instance belongs have the same business label for dynamic association. Wherein, the application can be divided according to the actual requirement. The form of the service tag can be set in a self-defining mode in advance. Including, for example, one or more of a business system, a business module, and a business service.

Fig. 2 is a schematic diagram of a service relationship model in a service-level full-link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 2, the application 1-1 and the included application examples 1-1-1 and 1-1-2 are all provided with the same service tag: the business system 1 and the business module 1 can establish the subordination relationship between the application 1-1 and the application example 1-1-2 through the business label. The application 1-2 and the included application examples 1-2-1 and 1-2-2 are all provided with the same service label: the business system 1 and the business module 2 can establish the affiliation of the application 1-2 and the application example 1-2-1 and the application example 1-2-2 through the business label. Likewise, application 2-1 and the included application instances 2-1-1 and 2-1-2 are each provided with the same service tag: the business system 2 and the business module 1 can establish the subordination relationship between the application 2-1 and the application instance 2-1-2 through the business label. The application 2-2 and the included application examples 2-2-1 and 2-2-2 are all provided with the same service label: the service system 2 and the service module 2 can establish the affiliation between the application 2-2 and the application instance 2-2-1 and the application instance 2-2-2 through the service label.

Therefore, the monitoring server can obtain the monitoring information result of which service type the monitoring client wants to obtain according to the service tag, for example, if the service tag is the tag of the service system 1, it indicates that the monitoring client wants to obtain the monitoring information result of the service system 1. The application included in the service system 1 and the conditions of the instances included in the application are further obtained according to the service relationship model, so that all the instances included in the service system 1 can be obtained, all the requested monitoring information of all the instances existing in the full link requested monitoring information can be obtained according to the full link requested monitoring information, and the monitoring information result of the service system 1 can be obtained. The monitoring server acquires a monitoring information result of the service system 1 and sends the monitoring information result to the monitoring client for the monitoring client to check. The monitoring information result can be displayed in a preset visual chart mode.

The embodiment of the invention can provide the service label corresponding to the instance when the application server instance is started, realizes the automatic grouping of the instance in the subsequent processing process of the monitoring server, and can keep the original relation between the application and the service after the IP drift.

According to the embodiment of the invention, the corresponding monitoring information result is obtained according to the service label, the stored service relation model and the full link request monitoring information, so that the corresponding monitoring information result is obtained according to the service type specified by the monitoring information checking request, and the service-level full link monitoring is realized.

Further, based on the above embodiment, the request monitoring information further carries a full link transaction chain identifier, where the full link transaction chain identifier includes information of the full link transaction chain to which the local transaction chain belongs and a position relationship of the local transaction chain in the full link transaction chain; the acquiring the full link request monitoring information of the full link transaction chain by integrating the request monitoring information according to the relationship between the request monitoring information comprises the following steps: and integrating the request monitoring information according to the full link transaction chain identifier to obtain the full link request monitoring information.

In order to facilitate the monitoring server to integrate the request monitoring information according to the relationship between the request monitoring information to obtain the full-link request monitoring information of the full-link transaction chain, the request monitoring information also carries a full-link transaction chain identifier, and the full-link transaction chain identifier includes information of the full-link transaction chain to which the local transaction chain belongs and a position relationship of the local transaction chain in the full-link transaction chain. And the monitoring server integrates the request monitoring information according to the full link transaction chain identification to obtain the full link request monitoring information.

Fig. 3 is a schematic diagram of an acquisition process of full-link request monitoring information in a service-level full-link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 3, the method includes:

taking monitoring of Java applications as an example, based on a bytecode dynamic injection technology (which can be implemented by deploying an Agent in an application server), monitoring key business logic in Java applications without modifying own code by a user, wherein Web services, file operations, database services and the like remotely call other services through a network, which can be key business logic entry points. And each transaction step passed in the current instance process is described by assembling and collecting a local transaction chain, and is uploaded to a data collection center of the monitoring server. The collected key service logic information is scattered information packets and needs to be assembled into a link, and the link is only a link inside the current instance, only a local link and not a full link. Example (c): the current request is a web request, the request reads and writes a file and accesses a primary database, and the three key service information are discretely collected and need to be combined and reported.

The request monitoring information reported by the example is only a part of the full link, and the global transaction (full link transaction chain) to which the local transaction chain belongs is represented by setting a full link transaction chain identifier for the request monitoring information. Local request monitoring information is uploaded to a data acquisition center in a distributed mode, then is distributed to a rear-end big data platform by the data acquisition center for analysis and integration, the relation among local transaction chains is combed to form a global transaction chain, namely the request monitoring information uploaded locally obtains full-link request monitoring information, and the full-link request monitoring information is sent to a console of a monitoring server for analysis, so that full-link tracking of the request is completed.

On the basis of the above embodiment, the embodiment of the present invention facilitates the monitoring server to integrate the request monitoring information according to the relationship between the locally uploaded request monitoring information by making the request monitoring information also carry the full-link transaction chain identifier, so as to obtain the full-link request monitoring information of the full-link transaction chain.

Further, based on the above embodiment, the monitoring information result includes a service-level application access relationship view, and the acquiring, by the monitoring server, the corresponding monitoring information result according to the service tag, the stored service relationship model, and the full-link request monitoring information specifically includes: the monitoring server acquires the instance identifier corresponding to the service label in the service relation model according to the service label; acquiring corresponding request monitoring information according to the instance identifier, and acquiring access relations among the instances corresponding to the application servers according to the full-link transaction chain identifier and the request time identifier carried by the request monitoring information; acquiring the access relation between the applications to which each instance belongs according to the access relation between the instances and the service label; obtaining the business level application access relation view according to the access relation between the applications to which the instances belong; and each application in the business-level application access relation view is represented by an application icon.

The monitoring information result comprises a service level application access relation view. The business level application access relation view comprises the access relation of the applications in the business category corresponding to the business label in the monitoring information viewing request. The specific acquisition process is as follows:

and the monitoring server acquires the instance identifier corresponding to the service label in the service relation model according to the service label, namely the instance identifier of the instance with the service label in the request monitoring information. Because the request monitoring information carries the instance identifier, the corresponding request monitoring information, that is, the request monitoring information to be viewed by the client, is obtained according to the instance identifier.

And acquiring the access relation between the instances corresponding to the application servers according to the full-link transaction chain identifier and the request time identifier carried by the request monitoring information. The request time identifier may be used to distinguish an order of request monitoring information sent by a single application server, and the full link transaction chain identifier may be used to distinguish an order of request monitoring information sent by different application servers. Because the request corresponds to an instance, the access relationship between the instances corresponding to each application server is obtained according to the full link transaction chain identifier and the request time identifier carried by the request monitoring information.

Since the instances and the applications to which the instances belong have the same service tags, the access relationship between the applications to which the instances belong can be acquired according to the access relationship between the instances and the service tags. Further, the business-level application access relation view is obtained according to the access relation between the applications to which the instances belong, and each application in the business-level application access relation view is represented by an application icon.

On the basis of the above embodiment, the embodiment of the present invention obtains the service-level application access relationship view according to the service label, the stored service relationship model, and the full-link request monitoring information, thereby achieving obtaining the service-level application access relationship view of the service required by the monitoring client.

Further, based on the above embodiment, the request monitoring information also carries information of the application server, and the method further includes: if the click information of the application icon is received, acquiring an application deployment relationship topological view of the application corresponding to the application icon according to the service relationship model and the full-link request monitoring information, and adding the application deployment relationship topological view to the monitoring information result; the application deployment relationship topology view comprises relationship information of the application corresponding to the clicked application icon in the full-link request monitoring information, the instance contained in the application and the application server to which the instance belongs, and the application, the instance and the application server are respectively represented by the application icon, the instance icon and the application server icon.

The request monitoring information also carries information of the application server, and the information indicates that the request monitoring information corresponds to an instance running on which application server. The monitoring information result can also comprise an application deployment relationship topological view. The application deployment relationship topological view can be realized by clicking the application icon to acquire the application deployment relationship topological view of the application corresponding to the application icon.

Thus, the method further comprises: and if the monitoring server receives the click information of the application icon, acquiring an application deployment relationship topological view of the application corresponding to the application icon according to the service relationship model and the full-link request monitoring information, and adding the application deployment relationship topological view to the monitoring information result.

The application deployment relationship topology view comprises relationship information of the application corresponding to the clicked application icon in the full-link request monitoring information, the instance contained in the application and the application server to which the instance belongs, and the application, the instance and the application server are respectively represented by the application icon, the instance icon and the application server icon.

The acquiring the application deployment relationship topology view of the application corresponding to the application icon according to the service relationship model and the full link request monitoring information includes: acquiring a service label of an application corresponding to the application icon, acquiring an instance identifier of an instance contained in the application corresponding to the service label according to the service relation model, acquiring the corresponding instance in the full-link request monitoring information according to the instance identifier, and acquiring information of an application server corresponding to the instance according to information of the application server carried by the request monitoring information requested in the instance. Therefore, the instance contained in the application corresponding to the clicked application icon and the information of the server to which the instance belongs are obtained.

And representing the application, the example contained by the application and the relation among the application servers to which the examples belong by using an application icon, an example icon and an application server icon connecting line, thereby obtaining the application deployment relation topology view.

On the basis of the above embodiment, in the embodiment of the present invention, the request monitoring information also carries information of the application server, and after receiving the click information of the application icon, the application deployment relationship topology view of the application corresponding to the application icon is obtained according to the service relationship model and the full-link request monitoring information, so that the obtaining of the application deployment relationship topology view is realized, and the richness of the monitoring information result is improved.

Further, based on the above embodiment, the monitoring server presets whether the service corresponding to the service tag is a key service; for the key service, a service step contained in the key service and a request list of the request contained in the service step are stored in advance, and the request in the request list is represented by the request identifier; after the monitoring server obtains a corresponding monitoring information result according to the service label, the stored service relationship model and the full link request monitoring information, the method further comprises: if the service corresponding to the service tag is judged and known to be the key service, acquiring a key service monitoring view of the key service, and adding the key service monitoring view to the monitoring information result; the key service monitoring view comprises a first view formed by sequentially connecting icons according to the service steps in the key service, and a second view comprising statistical information obtained by performing statistics according to the request monitoring information of the request contained in the key service.

Fig. 4 is an exemplary diagram of a critical service in a service-level full link monitoring method for an application according to an embodiment of the present invention. The monitoring server presets whether the service corresponding to the service label is a key service; and storing the included service steps and the request list of the requests included in the service steps in advance for the key services. Such as url1-1 in fig. 4, etc., represents the request identification requested in the request list.

Critical services are jumping out of applications and instances, from a pure service perspective of the system. The underlying basis for aggregation is a request, but can be a plurality of requests that do not directly raise a relationship. For example, the purchase service can be divided into: landing a platform, browsing categories, browsing commodities, adding a shopping cart, paying and the like. Each step corresponds to one or more requests which have no direct relation.

After the monitoring server obtains a corresponding monitoring information result according to the service label, the stored service relationship model and the full link request monitoring information, the method further comprises: if the service corresponding to the service tag is judged to be the key service, acquiring a key service monitoring view of the key service, and adding the key service monitoring view to the monitoring information result, namely the monitoring information result also comprises the key service monitoring view.

The key service monitoring view comprises a first view formed by sequentially connecting icons according to the service steps in the key service, and a second view comprising statistical information obtained by performing statistics according to the request monitoring information of the request contained in the key service. The request included in the critical service is constituted by a request in a request list of each of the service steps included in the critical service. The statistical information includes information such as a total amount of traffic, a maximum response time, and a number of failed traffic.

On the basis of the embodiment, the embodiment of the invention improves the monitoring capability of the key service concerned by the user, improves the practicability of the monitoring system and improves the richness of the monitoring information result by acquiring the key service monitoring view according to the set key service.

Further, based on the above embodiment, the method further includes: respectively acquiring the request monitoring information of the request contained in the application corresponding to the application icon, the example corresponding to the example icon and the business step corresponding to the step icon, respectively acquiring the application health states of the application, the example and the business step according to the request monitoring information, and displaying the application health states by using the colors of the application icon, the example icon and the step icon; displaying the running health state corresponding to the application server by using the color of the application server icon in the application deployment relationship topological view; and displaying the running health state corresponding to the application server by using the color of the application server icon in the application deployment relationship topological view.

In the service level application access relation view, the application corresponding to the application icon and the request monitoring information of the request contained in the instance corresponding to the instance icon are respectively obtained, the application health states of the application and the instance are respectively obtained according to the request monitoring information, and the application health states are displayed by using the colors of the application icon and the instance icon. For example, green indicates normal, yellow indicates slow response, red indicates alarm, etc.

In the application deployment relationship topological view, the request monitoring information of the request contained in the application corresponding to the application icon and the instance corresponding to the instance icon is respectively obtained, the application health states of the application and the instance are respectively obtained according to the request monitoring information, and the application health states are displayed by using the colors of the application icon and the instance icon. And displaying the running health state corresponding to the application server by using the color of the icon of the application server. For example, the application icon of the slow-responding application appears yellow, the instance icon of the slow-responding instance appears yellow, the application server icon appears yellow when the host (application server) cpu is insufficient, and the like.

And in the key business monitoring view, acquiring the request monitoring information of the request contained in the business step corresponding to the step icon, acquiring the application health state of the business step according to the request monitoring information, and displaying the application health state by using the color of the step icon. For example, the step icon of the business step which responds slower is yellow, and the step icon of the business step which has more errors is red, etc.

On the basis of the embodiment, the embodiment of the invention displays different health states by using different colors of the application icon, the instance icon, the step icon and the application server icon, thereby improving the monitoring visualization effect.

Further, based on the above embodiment, the method further includes: if the service corresponding to the service label is the key service, setting a switching label for displaying the key service monitoring view in the service level application access relation view; associating the application icon, the instance icon and the application server icon in the application deployment relationship topological view with the monitoring detail information of the corresponding application, the instance and the application server respectively; and associating the step icon in the key service monitoring view with the corresponding request list.

If the service corresponding to the service tag is the key service, the user may need to view a service level application access relationship view of the key service on the one hand, and also need to view a key service monitoring view of the key service on the other hand. Therefore, a switching label for displaying the key business monitoring view can be set in the business-level application access relation view, so as to facilitate the switching between the business-level application access relation view and the key business monitoring view.

In the application deployment relationship topological view, the request monitoring information of the request contained in the application corresponding to the application icon and the instance corresponding to the instance icon is respectively obtained, the application health states of the application and the instance are respectively obtained according to the request monitoring information, and the application health states are displayed by using the colors of the application icon and the instance icon. And the application icon, the instance icon and the application server icon in the application deployment relationship topological view are respectively associated with the monitoring detail information of the corresponding application, the instance and the application server. The monitoring detail information detail describes monitoring related data, such as tps (transaction number/second), average response time, total throughput and the like.

And associating the step icon in the key service monitoring view with the corresponding request list. Since the service steps included in the key service are preset with the included request list, the step icons in the key service monitoring view can be associated with the corresponding request list, so that the specific request list is switched to when the corresponding step icon is clicked.

On the basis of the above embodiment, the embodiment of the present invention sets the switch tag for displaying the key service monitoring view in the service level application access relationship view of the key service, associates the icon in the topology view of the application deployment relationship with the monitoring detail information, and associates the step icon in the monitoring view of the key service with the corresponding request list, thereby improving the visualization performance and the convenience and richness of information acquisition.

Fig. 5 is an exemplary diagram of a service-level application access relationship view in a service-level full-link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 5, each of the applications in the business-level application access relationship view is represented by an application icon. If the application of other system is called (e.g. 2-1 in the figure belongs to the business system 2), the corresponding icon is also displayed, but only the icon of the interface application can be displayed without extending.

The business level application access relation view is divided based on the business level relation, and the application access relation view of the business system and the business module level is displayed for the user; and the access relationship topological graph and the application health state among all the applications in the specified service category are embodied. And can be associated to the application deployment relationship view and the key business monitoring view through the portal.

Fig. 6 is an exemplary diagram of an application deployment relationship topology view in a service-level full-link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 6, the application deployment relationship topology view shows the health status and the deployment relationship of all applications, application associated instances, instance associated hosts in a specified business category to the user, and may associate the monitoring detail information to each monitoring object through the portal.

Fig. 7 is an exemplary diagram of a first view of a critical traffic monitoring view in a traffic level full link monitoring method for an application according to an embodiment of the present invention. Fig. 8 is an exemplary diagram of a second view of a critical traffic monitoring view in a traffic level full link monitoring method for an application according to an embodiment of the present invention. As shown in fig. 7 and 8, the key service monitoring view shows service information based on service aggregation in a specified service category, such as total service amount, maximum response time, number of failed services, and the like, to a user, and may be associated to a specific request list through the entry.

Fig. 9 is a flowchart of a method for monitoring a service-level full link for an application according to an embodiment of the present invention. As shown in fig. 9, the main steps of implementing the service-level full link monitoring method for an application program according to the embodiment of the present invention may include acquiring full link request monitoring information of a full link transaction chain, defining a service tag, and defining a key service, and by analyzing and sorting the full link request monitoring information, a service-level application access relationship view, an application deployment relationship topology view, and a key service monitoring view are respectively obtained.

The embodiment of the invention can conveniently and flexibly define the service concept to automatically group the examples according to the requirements of users, and converts a large amount of example-level and request-level monitoring information into service-level monitoring data by combining the capability of self-defining key services. Therefore, a simple and understandable business service monitoring state view is displayed for a user.

The embodiment of the invention realizes the hierarchy division and the grouping of the service through the definition of free labels and key services, constructs the relation views of the application and the service level based on the request and the monitoring information of the full link of the service level, and summarizes the monitoring information based on the service. The user can define key services, define which requests the service steps contain, and define which service steps the service chain contains.

After the monitored object is labeled, the monitored object is associated according to the label relationship, for example: the application server instance deploys or belongs to which application module. And then, based on the relation between the request and the service, a service system level view is connected in series. For the containerization environment, a service label corresponding to the instance can be provided when the instance is started, automatic grouping of the instance is realized, and the original application and service relation can be kept after IP drift.

The embodiment of the invention realizes the business model, the business hierarchy division and the instance grouping through the definition of free labels and key business; constructing a service level application access relation view based on the request and the instance level full link monitoring information; constructing an application deployment relationship topological view based on the label, the physical topological relation between the instance and the host and the incidence relation between the instance and the application; and constructing a key business monitoring view based on the business definition, the relation between the instances and the business and the request monitoring information on the instances.

The embodiment of the invention supports free service model and hierarchy definition, and supports highly complex service scenes; the service-level application access relation view which is more suitable for the user view can be provided, and the health state of the application related to the specified service module and the calling relation among the applications are clearly shown to the user; the method comprises the steps that a longitudinal application deployment relation topological view is provided by combining a business-level application access relation view, the topological view is clearly shown to a user, the application is deployed on instances and distributed on hosts, and the states of the relevant instances and the hosts are different; based on the key business monitoring view, the health state of each business step is clearly shown to the user, the business steps with the problem of the current service state are visually reflected, and the root causes of the business steps can be drilled down.

Fig. 10 is a schematic structural diagram of a monitoring server according to an embodiment of the present invention. As shown in fig. 10, the monitoring server includes a full-link monitoring data acquisition module 10, a monitoring information viewing request receiving module 20, and a monitoring information result obtaining and sending module 30, where:

the full link monitoring data acquisition module 10 is configured to: receiving request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrating the request monitoring information according to the relationship between the request monitoring information to obtain full-link request monitoring information of the full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs;

the monitoring information viewing request receiving module 20 is configured to: receiving a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag;

the monitoring information result obtaining and sending module 30 is configured to: acquiring a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sending the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

Further, based on the above embodiment, the request monitoring information further carries a full link transaction chain identifier, where the full link transaction chain identifier includes information of the full link transaction chain to which the local transaction chain belongs and a position relationship of the local transaction chain in the full link transaction chain; when the full-link monitoring data acquisition module 10 is configured to integrate the request monitoring information according to the relationship between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain, the full-link monitoring data acquisition module is specifically configured to: and integrating the request monitoring information according to the full link transaction chain identifier to obtain the full link request monitoring information.

Further, based on the above embodiment, the monitoring information result includes a service-level application access relationship view, and the monitoring information result obtaining and sending module 30 is specifically configured to, when being configured to obtain a corresponding monitoring information result according to the service tag, the stored service relationship model, and the full-link request monitoring information: acquiring the instance identifier corresponding to the service label in the service relation model according to the service label; acquiring corresponding request monitoring information according to the instance identifier, and acquiring access relations among the instances corresponding to the application servers according to the full-link transaction chain identifier and the request time identifier carried by the request monitoring information; acquiring the access relation between the applications to which each instance belongs according to the access relation between the instances and the service label; obtaining the business level application access relation view according to the access relation between the applications to which the instances belong; and each application in the business-level application access relation view is represented by an application icon.

Further, based on the above embodiment, the request monitoring information also carries information of the application server, and the monitoring information result obtaining and sending module 30 is further configured to: if the click information of the application icon is received, acquiring an application deployment relationship topological view of the application corresponding to the application icon according to the service relationship model and the full-link request monitoring information, and adding the application deployment relationship topological view to the monitoring information result; the application deployment relationship topology view comprises relationship information of the application corresponding to the clicked application icon in the full-link request monitoring information, the instance contained in the application and the application server to which the instance belongs, and the application, the instance and the application server are respectively represented by the application icon, the instance icon and the application server icon.

Further, based on the above embodiment, the monitoring server presets whether the service corresponding to the service tag is a key service; for the key service, a service step contained in the key service and a request list of the request contained in the service step are stored in advance, and the request in the request list is represented by the request identifier; the monitoring information result obtaining and sending module 30 is further configured to: if the service corresponding to the service tag is judged and known to be the key service, acquiring a key service monitoring view of the key service, and adding the key service monitoring view to the monitoring information result; the key service monitoring view comprises a first view formed by sequentially connecting icons according to the service steps in the key service, and a second view comprising statistical information obtained by performing statistics according to the request monitoring information of the request contained in the key service.

Further, based on the above embodiment, the monitoring information result obtaining and sending module 30 is further configured to: respectively acquiring the request monitoring information of the request contained in the application corresponding to the application icon, the example corresponding to the example icon and the business step corresponding to the step icon, respectively acquiring the application health states of the application, the example and the business step according to the request monitoring information, and displaying the application health states by using the colors of the application icon, the example icon and the step icon; and displaying the running health state corresponding to the application server by using the color of the application server icon in the application deployment relationship topological view.

Further, based on the above embodiment, the monitoring information result obtaining and sending module 30 is further configured to: if the service corresponding to the service label is the key service, setting a switching label for displaying the key service monitoring view in the service level application access relation view; associating the application icon, the instance icon and the application server icon in the application deployment relationship topological view with the monitoring detail information of the corresponding application, the instance and the application server respectively; and associating the step icon in the key service monitoring view with the corresponding request list.

The device provided by the embodiment of the present invention is used for the method, and specific functions may refer to the above method flow, which is not described herein again.

Fig. 11 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 11, the electronic device may include: a processor (processor)1110, a communication Interface (Communications Interface)1120, a memory (memory)1130, and a communication bus 1140, wherein the processor 1110, the communication Interface 1120, and the memory 1130 communicate with each other via the communication bus 1140. Processor 1110 may call logic instructions in memory 1130 to perform the following method: the method comprises the steps that a monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relation between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs; the monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag; the monitoring server acquires a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sends the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

In addition, the logic instructions in the memory 1130 may be implemented in software functional units and stored in a computer readable storage medium when sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

In another aspect, an embodiment of the present invention further provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is implemented by a processor to perform the method provided by the foregoing embodiments, for example, including: the method comprises the steps that a monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relation between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs; the monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag; the monitoring server acquires a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sends the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A service level full link monitoring method for an application program is characterized by comprising the following steps:

the method comprises the steps that a monitoring server receives request monitoring information of a local transaction chain uploaded by at least one application server of an application program to be monitored, and integrates the request monitoring information according to the relation between the request monitoring information to obtain full-link request monitoring information of a full-link transaction chain; the request monitoring information is acquired by the application server in an instance process and carries a request time identifier, a request identifier and an instance identifier, wherein the request time identifier is used for indicating the time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request and identifying the instance to which the request belongs;

the monitoring server receives a monitoring information viewing request of a monitoring client, wherein the monitoring information viewing request comprises a service tag;

the monitoring server acquires a corresponding monitoring information result according to the service label, the stored service relation model and the full link request monitoring information, and sends the monitoring information result to the monitoring client; the business relation model is provided with the business labels for a preset application and an example contained in the application respectively, and the application and the example are provided with an application identifier and an example identifier respectively; wherein the instance and the application to which the instance belongs have the same business label.

2. The service-level full-link monitoring method for an application program according to claim 1, wherein the request monitoring information further carries a full-link transaction chain identifier, and the full-link transaction chain identifier includes information of the full-link transaction chain to which the local transaction chain belongs and a position relationship of the local transaction chain in the full-link transaction chain;

the acquiring the full link request monitoring information of the full link transaction chain by integrating the request monitoring information according to the relationship between the request monitoring information comprises the following steps: and integrating the request monitoring information according to the full link transaction chain identifier to obtain the full link request monitoring information.

3. The service-level full-link monitoring method for an application program according to claim 2, wherein the monitoring information result includes a service-level application access relationship view, and the monitoring server obtains a corresponding monitoring information result according to the service tag, the stored service relationship model, and the full-link request monitoring information, specifically including:

the monitoring server acquires the instance identifier corresponding to the service label in the service relation model according to the service label; acquiring corresponding request monitoring information according to the instance identifier, and acquiring access relations among the instances corresponding to the application servers according to the full-link transaction chain identifier and the request time identifier carried by the request monitoring information; acquiring the access relation between the applications to which each instance belongs according to the access relation between the instances and the service label; obtaining the business level application access relation view according to the access relation between the applications to which the instances belong; and each application in the business-level application access relation view is represented by an application icon.

4. The traffic-level full-link monitoring method for application programs according to claim 3, wherein the request monitoring information also carries information of the application server, the method further comprising:

if the click information of the application icon is received, acquiring an application deployment relationship topological view of the application corresponding to the application icon according to the service relationship model and the full-link request monitoring information, and adding the application deployment relationship topological view to the monitoring information result;

5. The service-level full-link monitoring method for the application program according to claim 4, wherein the monitoring server is preset whether the service corresponding to the service tag is a key service; for the key service, a service step contained in the key service and a request list of the request contained in the service step are stored in advance, and the request in the request list is represented by the request identifier;

after the monitoring server obtains a corresponding monitoring information result according to the service label, the stored service relationship model and the full link request monitoring information, the method further comprises: if the service corresponding to the service tag is judged and known to be the key service, acquiring a key service monitoring view of the key service, and adding the key service monitoring view to the monitoring information result; the key service monitoring view comprises a first view formed by sequentially connecting icons according to the service steps in the key service, and a second view comprising statistical information obtained by performing statistics according to the request monitoring information of the request contained in the key service.

6. The method for service level full link monitoring for an application program of claim 5, further comprising:

respectively acquiring the request monitoring information of the request contained in the application corresponding to the application icon, the example corresponding to the example icon and the business step corresponding to the step icon, respectively acquiring the application health states of the application, the example and the business step according to the request monitoring information, and displaying the application health states by using the colors of the application icon, the example icon and the step icon; and displaying the running health state corresponding to the application server by using the color of the application server icon in the application deployment relationship topological view.

7. The method for service level full link monitoring for an application program of claim 6, further comprising: if the service corresponding to the service label is the key service, setting a switching label for displaying the key service monitoring view in the service level application access relation view;

associating the application icon, the instance icon and the application server icon in the application deployment relationship topological view with the monitoring detail information of the corresponding application, the instance and the application server respectively;

and associating the step icon in the key service monitoring view with the corresponding request list.

8. A monitoring server, comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method for service level full link monitoring for an application program according to any one of claims 1 to 7 when executing the computer program.

10. A non-transitory computer readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps of the traffic level full link monitoring method for an application program according to any one of claims 1 to 7.