CN110968479B

CN110968479B - Service level full-link monitoring method and server for application program

Info

Publication number: CN110968479B
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: 2023-05-23
Anticipated expiration: 2039-11-20
Also published as: CN110968479A

Abstract

The embodiment of the invention provides a business-level full-link monitoring method and a server for application programs, 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 comprising a service tag; 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, corresponding monitoring information results are obtained according to the service labels, the stored service relation model and the full-link request monitoring information, so that the corresponding monitoring information results are obtained according to the service category designated by the monitoring information checking request, and the service level full-link monitoring is realized.

Description

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

Technical Field

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

Background

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

Full link monitoring is request-based, while requests are application instance-based, the underlying implementation of full link monitoring is request-based concatenation. The request level monitoring expresses a request, which subsequent requests are initiated, and can be represented by comparing the underlying views. On a request level basis, a relatively high-level view is formed by aggregating requests through one service instance, so that instance level monitoring is realized, and the fact that one service instance depends on other service instances can be expressed. The request contains a service target, for example: both the IP and port information express which instance handles the service. However, since the service is complex, the requests are thousands of requests, and the subsequent requests initiated according to different request parameters are not identical. Also, enterprise-level systems tend to be clustered, and the same request and subsequent requests that it initiates do not always fall on the same instance, resulting in changes in the IP and port of the request. In summary, if a tree graph is made based on a request, the user is blind and a large number of trees are available. As the most primitive data of a certain request, it is more realistic, but less useful for analyzing problems.

Therefore, the current full-link monitoring technology can only achieve request-level monitoring and instance-level monitoring, and both monitoring modes face the problem of service instance change of the cluster environment, so that the full-link monitoring cannot well express service concepts, and cannot achieve service-level monitoring. Therefore, how to turn request monitoring of a large number of instances into business level monitoring that can be understood and focused by users becomes a great emphasis of modern monitoring schemes.

Disclosure of Invention

In order to solve the problems in the prior art, the embodiment of the invention provides a business-level full-link monitoring method and a server aiming at an application program.

In a first aspect, an embodiment of the present invention provides a service level full link monitoring method for an application, including: 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 all-link request monitoring information of an all-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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs; the monitoring server receives a monitoring information checking request of a monitoring client, wherein the monitoring information checking request comprises a service tag; 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 preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service label.

Further, the request monitoring information also carries a full-link transaction chain identifier, wherein the full-link transaction chain identifier comprises information of the full-link transaction chain to which the local transaction chain belongs and a position relation of the local transaction chain in the full-link transaction chain; the integrating the request monitoring information according to the relation between the request monitoring information to obtain the full-link request monitoring information of the full-link transaction chain comprises the following steps: and integrating the request monitoring information according to the all-link transaction chain identification to obtain the all-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, and specifically includes: the monitoring server obtains the instance identifier corresponding to the service tag in the service relationship model according to the service tag; 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 carried by the request monitoring information and the request time identifier; acquiring access relations among the applications to which each instance belongs according to the access relations among the instances and the service labels; obtaining a service level application access relation view according to the access relation among the applications of the respective examples; each of the applications in the business level application access relationship view is represented by an application icon.

Further, the request monitoring information also carries information of the application server, and the method further comprises: if the click information of the application icon is received, acquiring an application deployment relation topological view of the application corresponding to the application icon according to the service relation model and the full-link request monitoring information, and adding the application deployment relation 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 is preset whether the service corresponding to the service tag is a key service or not; the key business is pre-stored with the included business steps and the request list of the requests included in the business steps, and the requests in the request list are represented by the request identifiers; after the monitoring server obtains the corresponding monitoring information result according to the service label, the stored service relation model and the full-link request monitoring information, the method further comprises: if judging that the service corresponding to the service tag is 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 step icons of the service steps in the key service and a second view comprising statistical information obtained by statistics according to the request monitoring information of the request contained in the key service.

Further, the method further comprises: the application corresponding to the application icon, the instance corresponding to the instance icon and the request monitoring information of the request contained in the business step corresponding to the step icon are respectively obtained, the application health states of the application, the instance and the business step are respectively obtained according to the request monitoring information, and the application health states are displayed by utilizing the colors of the application icon, the instance icon and the step icon; and displaying the running health state of the corresponding application server by utilizing the color of the application server icon in the application deployment relation 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 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 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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs;

the monitoring information viewing request receiving module is used for: receiving a monitoring information checking request of a monitoring client, wherein the monitoring information checking request comprises a service tag;

the monitoring information result acquisition and transmission 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 transmitting the monitoring information result to the monitoring client; the business relation model is provided with the business labels for preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service label.

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

In a fourth aspect, embodiments of the present invention provide a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method as provided by the first aspect.

According to the service level full-link monitoring method and the server for the application program, corresponding monitoring information results are obtained according to the service labels, the stored service relation model and the full-link request monitoring information, so that the corresponding monitoring information results are obtained according to the service category designated 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 that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method for service level full link monitoring for an application according to an embodiment of the present invention;

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

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;

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

FIG. 5 is an exemplary diagram of a business level application access relationship view in a business level full link monitoring method for an application provided by an embodiment of the present invention;

FIG. 6 is an exemplary diagram of an application deployment relationship topology view in a business level full link monitoring method for an application provided by 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 provided in 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 provided in accordance with 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 diagram of a monitoring server according to an embodiment of the present invention;

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

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the 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 relation between the request monitoring information to obtain all-link request monitoring information of an all-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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from the instance to which the request belongs.

The monitoring server is a background server for realizing the business-level full-link monitoring method for the application program. The application server is for running an instance of the application to be monitored. The application to be monitored can jointly realize corresponding functions by a plurality of examples. Moreover, the same instance can be deployed on a plurality of application servers, and the security is improved through a cluster deployment mode.

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

The application server can preset the full-link transaction chain to which the local transaction chain generated by the instance operation belongs and the position relation in the full-link transaction chain, and carry the information when uploading the request monitoring information so that the monitoring server can acquire the relation among the request monitoring information, and therefore the request monitoring information is integrated according to the relation among 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 occurrence time of the request, so that the request time identifier can identify the occurrence sequence of the request; the request identification is used for distinguishing the request; the instance identification is used to identify the instance to which the request belongs, and may generally represent the request that was uploaded by which application server.

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

And the monitoring server receives a monitoring information checking request of the monitoring client, wherein the monitoring information checking request comprises a service tag. The service tag may be a certain service tag in a service relationship model stored by the monitoring server.

Step 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 preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service label.

The monitoring server stores a service relation model in advance, wherein the service relation model is respectively provided with the service label for a preset application and an instance contained in the application, and the application and the instance are respectively provided with an application identifier and an instance identifier. The instance and the application to which the instance belongs have the same business label for dynamic association. The application may be divided according to actual requirements. The form of the service tag can be preset in a customized mode. Such as including one or more of a business system, business module, business service.

Fig. 2 is a schematic diagram of a business relationship model in a business 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 instance 1-1-1 and the application instance 1-1-2 are provided with the same service label: the business system 1 and business module 1 can thus establish the affiliation of application 1-1 and application instance 1-1-2 by means of the above-described business labels. The application 1-2 and the included application instance 1-2-1 and the application instance 1-2-2 are provided with the same service label: the business system 1 and business module 2 can thus establish the affiliation of the application 1-2 and application instance 1-2-1 and application instance 1-2-2 by means of the above-described business labels. Likewise, application 2-1 and the included application instance 2-1-1 and application instance 2-1-2 are provided with the same service label: the business system 2 and business module 1 can thus establish the affiliation of application 2-1 and application instance 2-1-2 by means of the above-described business labels. The application 2-2 and the included application instance 2-2-1 and the application instance 2-2-2 are provided with the same service label: the business system 2 and business module 2 can thus establish the affiliation of application 2-2 and application instance 2-2-1 and application instance 2-2-2 by means of the above-described business labels.

Therefore, the monitoring server can learn, according to the service tag, which service class of the monitoring information result is to be obtained by the monitoring client, for example, if the service tag is a tag of the service system 1, it indicates that the monitoring client is to obtain the monitoring information result of the service system 1. The application included in the service system 1 and the case of the instance included in the application are further acquired according to the service relation model, so that all the instances included in the service system 1 can be acquired, and all the request monitoring information of the corresponding requests of the corresponding instances in the full-link request monitoring information can be acquired according to the full-link request monitoring information, so that the monitoring information result of the service system 1 can be acquired. The monitoring server acquires the 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 instance of the application server is started, realize the automatic grouping of the instance in the subsequent processing process of the monitoring server, and can keep the original application and service relationship after IP drifting.

The embodiment of the invention obtains the corresponding monitoring information result according to the service label, the stored service relation model and the full-link request monitoring information, thereby realizing the service-level full-link monitoring.

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 positional relationship of the local transaction chain in the full-link transaction chain; the integrating the request monitoring information according to the relation between the request monitoring information to obtain the full-link request monitoring information of the full-link transaction chain comprises the following steps: and integrating the request monitoring information according to the all-link transaction chain identification to obtain the all-link request monitoring information.

In order to facilitate the monitoring server to integrate the request monitoring information according to the relation 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 comprises the information of the full-link transaction chain to which the local transaction chain belongs and the position relation of the local transaction chain in the full-link transaction chain. And integrating the request monitoring information according to the all-link transaction chain identifier by the monitoring server to obtain the all-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 application as an example, based on a dynamic injection technology of byte codes (which can be realized by deploying an Agent in an application server), key business logic in the Java application is monitored without modifying own codes by a user, wherein Web service, file operation, database service and the like can be key business logic cut-in points by remotely calling other services through a network. And describing each transaction step passing through in the current example process through the assembly acquisition local transaction chain, and uploading the transaction steps to a data acquisition 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 in the current example, is only a local link and is not a full link. Examples: the current request is a web request, which reads and writes a file, accesses a database once, and the three key business information are collected discretely and need to be combined and reported.

The request monitoring information reported by the instance is only a part of the full link, and the global transaction (full link transaction chain) to which the local transaction chain belongs is indicated by setting the full link transaction chain identification to the request monitoring information. And after the local request monitoring information is distributed and uploaded to the data acquisition center, the data acquisition center shunts to the rear-end big data platform for analysis and integration, and the relationship 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 sends the full-link request monitoring information to a control console of a monitoring server for analysis, so that full-link tracking of the request is completed.

On the basis of the embodiment, the embodiment of the invention facilitates the monitoring server to integrate the request monitoring information according to the relation between the request monitoring information uploaded locally to obtain the full-link request monitoring information of the full-link transaction chain by enabling the request monitoring information to also carry the full-link transaction chain identification.

Further, based on the foregoing embodiment, 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, and specifically includes: the monitoring server obtains the instance identifier corresponding to the service tag in the service relationship model according to the service tag; 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 carried by the request monitoring information and the request time identifier; acquiring access relations among the applications to which each instance belongs according to the access relations among the instances and the service labels; obtaining a service level application access relation view according to the access relation among the applications of the respective examples; each of the applications in the business level application access relationship view is represented by an application icon.

The monitoring information result comprises a business level application access relationship view. The business-level application access relationship view contains access relationships of applications in business categories corresponding to business labels 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 tag in the service relation model according to the service tag, namely the instance identifier of the instance of the service tag in the request monitoring information. Because the request monitoring information carries the instance identifier, the corresponding request monitoring information, namely the request monitoring information to be checked by the client, is acquired according to the instance identifier.

And acquiring the access relation among the instances corresponding to the application servers according to the full-link transaction chain identifier carried by the request monitoring information and the request time identifier. Wherein the request time identification can be used to distinguish the order of request monitoring information sent by a single application server, and the full-link transaction chain identification can be used to distinguish the order of request monitoring information sent by different application servers. And acquiring the access relation among the instances corresponding to the application servers according to the full-link transaction chain identification carried by the request monitoring information and the request time identification because the request corresponds to the instances.

Since an instance and an application to which the instance belongs have the same service tag, the access relationship between the applications to which each instance belongs can be obtained according to the access relationship between the instances and the service tag. Further, the service-level application access relation view is obtained according to the access relation among the applications to which the respective examples belong, and each application in the service-level application access relation view is represented by an application icon.

Based on the embodiment, the embodiment of the invention obtains the service level application access relation view according to the service label, the stored service relation model and the full-link request monitoring information, thereby realizing the obtaining of the service level application access relation view of the service required by the monitoring client.

Further, based on the above embodiment, the request monitoring information further 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 relation topological view of the application corresponding to the application icon according to the service relation model and the full-link request monitoring information, and adding the application deployment relation 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, indicating to which application server the request monitoring information corresponds to an instance running on. The monitoring information result may also include an application deployment relationship topology view. The application deployment relation topological view can be obtained by clicking the application icon.

Thus, the method further comprises: and if the monitoring server receives 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 obtaining 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 the 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 an application server carried by the request monitoring information requested in the instance. Therefore, the acquisition of the instance contained in the application corresponding to the clicked application icon and the server information to which the instance belongs is realized.

And representing the application, the instance contained in the application and the relation among application servers to which the instance belongs by using an application icon, an instance icon and an application server icon connecting line, thereby obtaining the application deployment relation topological view.

On the basis of the embodiment, the embodiment of the invention realizes the acquisition of the application deployment relationship topological view by enabling the request monitoring information to also carry the information of the application server and acquiring the 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 after receiving the click information of the application icon, thereby improving the richness of the monitoring information result.

Further, based on the above embodiment, the monitoring server is preset to determine whether the service corresponding to the service tag is a key service; the key business is pre-stored with the included business steps and the request list of the requests included in the business steps, and the requests in the request list are represented by the request identifiers; after the monitoring server obtains the corresponding monitoring information result according to the service label, the stored service relation model and the full-link request monitoring information, the method further comprises: if judging that the service corresponding to the service tag is 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 step icons of the service steps in the key service and a second view comprising statistical information obtained by statistics according to the request monitoring information of the request contained in the key service.

Fig. 4 is an exemplary diagram of key services in a service level full link monitoring method for an application according to an embodiment of the present invention. The monitoring server is preset with whether the service corresponding to the service label is a key service or not; and pre-storing the included business steps and the request list of the requests included in the business steps for the key business. Url1-1, etc. as in fig. 4, represents the request identification of the request in the request list.

Critical traffic jumps out of applications and instances, from the point of view of pure traffic the system. The underlying basis for aggregation is a request, but may be a plurality of requests that do not directly elicit a relationship. For example, purchase business can be divided into: landing platform, browsing category, browsing commodity, joining shopping cart, paying and other business steps. Each of the above steps corresponds to one to a plurality of requests that have no direct relationship.

After the monitoring server obtains the corresponding monitoring information result according to the service label, the stored service relation model and the full-link request monitoring information, the method further comprises: and if judging that the service corresponding to the service tag is 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 further comprises the key service monitoring view.

The key service monitoring view comprises a first view formed by sequentially connecting step icons of the service steps in the key service and a second view comprising statistical information obtained by statistics according to the request monitoring information of the request contained in the key service. The requests contained by the critical services consist of requests in a request list of the individual service steps contained by the critical services. The statistical information includes, for example, information of total traffic, maximum response time, and number of failed traffic.

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

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

And in the service-level application access relation view, respectively acquiring the application corresponding to the application icon and the request monitoring information of the request contained in the instance corresponding to the instance icon, respectively acquiring the application health states of the application and the instance according to the request monitoring information, and displaying the application health states by utilizing the colors of the application icon and the instance icon. For example, green indicates normal, yellow indicates slow response, red indicates occurrence of an alarm, and the like.

And in the application deployment relationship topological view, respectively acquiring the application corresponding to the application icon and the request monitoring information of the request contained in the instance corresponding to the instance icon, respectively acquiring the application health states of the application and the instance according to the request monitoring information, and displaying the application health states by utilizing the colors of the application icon and the instance icon. And displaying the running health state corresponding to the application server by utilizing the color of the application server icon. For example, an application icon of a slow-response application is yellow, an instance icon of a slow-response instance is yellow, an application server icon is yellow when a 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 utilizing the color of the step icon. For example, the step icon of the business step which responds slower is yellow, the step icon of the business step which has more errors is red, etc.

Based on the embodiment, the embodiment of the invention improves the monitoring visual effect by displaying different health states by using different colors of the application icon, the instance icon, the step icon and the application server icon.

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 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 view a key service monitoring view of the key service on the other hand. Therefore, a switch label for displaying the key service monitoring view can be set in the service level application access relation view, so that the service level application access relation view and the key service monitoring view can be conveniently switched.

And in the application deployment relationship topological view, respectively acquiring the application corresponding to the application icon and the request monitoring information of the request contained in the instance corresponding to the instance icon, respectively acquiring the application health states of the application and the instance according to the request monitoring information, and displaying the application health states by utilizing 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 details refine the description of the monitoring related data such as tps (transactions per second), average response time, total throughput, etc.

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

On the basis of the embodiment, the embodiment of the invention improves the visualization performance and the convenience and richness of information acquisition by setting the switching label for displaying the key service monitoring view in the service-level application access relation view of the key service, associating the icon in the application deployment relation topological view with the monitoring detail information, and associating the step icon in the key service monitoring view with the corresponding request list.

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 an application of another system is called (for example, 2-1 belongs to the service system 2 in the figure), a corresponding icon is also displayed, but only the icon of the interface application may be displayed without continuing to extend.

The service level application access relation view divides the service view based on the service level relation and displays the service system and service module level application access relation view to the user; the access relation topological graph among all the applications in the specified business category is embodied, and the health state of the applications is applied. And can be associated with an application deployment relationship view and a critical traffic 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 deployment relationship of all applications, application associated instances, instance associated hosts in the specified service category to the user, and can be associated to the monitoring details of 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 monitor view shows the user the service information based on service aggregation, such as total amount of service, maximum response time, failure service number, etc., in the specified service category, and can be associated to the 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 the method for implementing service level full link monitoring for an application program according to the embodiment of the present invention may include obtaining full link request monitoring information of a full link transaction chain, service tag definition and key service definition, 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 convert 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. Thereby exposing the user with a simple and understandable view of the traffic service monitoring status.

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

After the monitoring object is labeled, the monitoring object is self-associated according to the label relation, for example: the application server instance deploys or belongs to which application module. And then the service system level view is connected in series based on the relation between the request and the service. For the containerized environment, service labels corresponding to the examples can be provided when the examples are started, automatic grouping of the examples is realized, and the original application and service relation can be maintained after IP drifting.

The embodiment of the invention realizes service model, service hierarchy division and instance grouping through the definition of free labels and key services; constructing a business-level application access relation view based on the request and the instance-level full-link monitoring information; constructing an application deployment relationship topology view based on the labels, the physical topological relation between the instance and the host and the association relation between the instance and the application; a critical business monitoring view is constructed based on the business definition, the instance-to-business relationship, and the request monitoring information on the instance.

The embodiment of the invention supports free service model and hierarchy definition and highly complex service scenes; the service level application access relation view which is more fit with the view angle of the user can be provided, and the health state of the application related to the specified service module and the calling relation among the application can be clearly shown to the user; the joint service level application access relation view provides a longitudinal application deployment relation topological view, clearly shows to a user how the application is deployed on the examples and distributed on the hosts, and how the relevant examples and the states of the hosts are; based on the key service monitoring view, the health state of each service step is clearly shown to the user, the service step with the problem of the current service state is intuitively reflected, and the root cause of the service step 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 transmitting module 30, where:

the full link monitoring data acquisition module 10 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 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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs;

the monitoring information viewing request receiving module 20 is configured to: receiving a monitoring information checking request of a monitoring client, wherein the monitoring information checking 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 transmitting the monitoring information result to the monitoring client; the business relation model is provided with the business labels for preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service 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 positional relationship of the local transaction chain in the full-link transaction chain; the full link monitoring data acquisition module 10 is specifically configured to, when 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: and integrating the request monitoring information according to the all-link transaction chain identification to obtain the all-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 used for obtaining 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 tag in the service relationship model according to the service tag; 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 carried by the request monitoring information and the request time identifier; acquiring access relations among the applications to which each instance belongs according to the access relations among the instances and the service labels; obtaining a service level application access relation view according to the access relation among the applications of the respective examples; each of the applications in the business level application access relationship view is represented by an application icon.

Further, based on the above embodiment, the request monitoring information further 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 relation topological view of the application corresponding to the application icon according to the service relation model and the full-link request monitoring information, and adding the application deployment relation 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 is preset to determine whether the service corresponding to the service tag is a key service; the key business is pre-stored with the included business steps and the request list of the requests included in the business steps, and the requests in the request list are represented by the request identifiers; the monitoring information result obtaining and sending module 30 is further configured to: if judging that the service corresponding to the service tag is 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 step icons of the service steps in the key service and a second view comprising statistical information obtained by 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: the application corresponding to the application icon, the instance corresponding to the instance icon and the request monitoring information of the request contained in the business step corresponding to the step icon are respectively obtained, the application health states of the application, the instance and the business step are respectively obtained according to the request monitoring information, and the application health states are displayed by utilizing the colors of the application icon, the instance icon and the step icon; and displaying the running health state of the corresponding application server by utilizing the color of the application server icon in the application deployment relation 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 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 in the embodiment of the present invention is used in the above method, and specific functions may refer to the above method flow, which is not described herein again.

Fig. 11 is a schematic physical structure of an electronic device according to an embodiment of the invention. As shown in fig. 11, the electronic device may include: processor 1110, communication interface Communications Interface 1120, memory 1130 and communication bus 1140, wherein processor 1110, communication interface 1120 and memory 1130 communicate with each other via communication bus 1140. Processor 1110 may call logic instructions in memory 1130 to perform the following methods: 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 all-link request monitoring information of an all-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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs; the monitoring server receives a monitoring information checking request of a monitoring client, wherein the monitoring information checking request comprises a service tag; 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 preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service label.

Further, the logic instructions in the memory 1130 described above may be implemented in the form of software functional units and sold or used as a stand-alone product, stored on a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform 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, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In another aspect, embodiments of the present invention also provide a non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor is implemented to perform the method provided in the above embodiments, for example, including: 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 all-link request monitoring information of an all-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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs; the monitoring server receives a monitoring information checking request of a monitoring client, wherein the monitoring information checking request comprises a service tag; 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 preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same service label.

The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A business-level full-link monitoring method for an application program, comprising:

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 all-link request monitoring information of an all-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 occurrence time of the request, and the request identifier and the instance identifier are respectively used for distinguishing the request from an instance to which the request belongs;

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

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 preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same business label;

the request monitoring information also carries a full-link transaction chain identification, wherein the full-link transaction chain identification comprises information of the full-link transaction chain to which the local transaction chain belongs and the position relation of the local transaction chain in the full-link transaction chain;

the monitoring information result comprises a service level application access relation view, and 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 the method specifically comprises the following steps:

The monitoring server obtains the instance identifier corresponding to the service tag in the service relationship model according to the service tag; 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 carried by the request monitoring information and the request time identifier; acquiring access relations among the applications to which each instance belongs according to the access relations among the instances and the service labels; and obtaining the service level application access relation view according to the access relation among the applications to which the respective examples belong.

2. The method for monitoring all links of a service level for an application program according to claim 1, wherein integrating the request monitoring information according to the relation between the request monitoring information to obtain all link request monitoring information of all link transaction chains comprises: and integrating the request monitoring information according to the all-link transaction chain identification to obtain the all-link request monitoring information.

3. The business-level full link monitoring method for an application program according to claim 2, wherein each of said applications in said business-level application access relationship view is represented by an application icon.

4. A service level full link monitoring method for an application program according to claim 3, wherein said request monitoring information further carries information of said application server, said method further comprising:

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

5. The method for monitoring a service level full link for an application program according to claim 4, wherein the monitoring server is preset to determine whether a service corresponding to the service tag is a critical service; the key business is pre-stored with the included business steps and the request list of the requests included in the business steps, and the requests in the request list are represented by the request identifiers;

After the monitoring server obtains the corresponding monitoring information result according to the service label, the stored service relation model and the full-link request monitoring information, the method further comprises: if judging that the service corresponding to the service tag is 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 step icons of the service steps in the key service and a second view comprising statistical information obtained by statistics according to the request monitoring information of the request contained in the key service.

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

the application corresponding to the application icon, the instance corresponding to the instance icon and the request monitoring information of the request contained in the business step corresponding to the step icon are respectively obtained, the application health states of the application, the instance and the business step are respectively obtained according to the request monitoring information, and the application health states are displayed by utilizing the colors of the application icon, the instance icon and the step icon; and displaying the running health state of the corresponding application server by utilizing the color of the application server icon in the application deployment relation topological view.

7. The method for traffic-level full link monitoring for an application 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 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:

the monitoring information result acquisition and transmission 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 transmitting the monitoring information result to the monitoring client; the business relation model is provided with the business labels for preset applications and examples contained in the applications respectively, and the applications and the examples are provided with application identifiers and example identifiers respectively; wherein the instance and the application to which the instance belongs have the same business label;

the monitoring information result comprises a service level application access relation view, and the monitoring information result acquisition and transmission module is specifically 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 when being used for acquiring the corresponding monitoring information result: acquiring the instance identifier corresponding to the service tag in the service relationship model according to the service tag; 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 carried by the request monitoring information and the request time identifier; acquiring access relations among the applications to which each instance belongs according to the access relations among the instances and the service labels; and obtaining the service level application access relation view according to the access relation among the applications to which the respective examples belong.

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the business-level full link monitoring method for an application according to any of claims 1 to 7 when the computer program is executed by the processor.

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