Application monitoring method and system

Abstract

The embodiment of the invention provides an application monitoring method and system, and the method comprises the steps: determining an instance publishing set associated with a target application, and publishing to-be-published instances in the instance publishing set based on the batch record information corresponding to the instance publishing set; performing instance monitoring on the instance publishing set in publishing to obtain monitoring information; and when it is determined that the instance release set contains a change instance according to the monitoring information and the change instance is in a release state, generating instance change information corresponding to the target application based on the monitoring information, and synchronizing the instance change information to a data center node. In the process of publishing the to-be-published instance in the instance publishing set corresponding to the target application, allowing instance change to occur in the instance publishing set. The instance release set is monitored through the application monitoring node, so that the instance change information can be generated based on the determined monitoring information, the release process of the target application is optimized, and the release and elastic efficiency of the target application is improved.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and particularly to an application monitoring method and system. Background Art

[0002] With the development of computer technology, applications have gradually shown diverse development. In the traditional mode, the release and elasticity (scaling in and out) of applications are processed separately. The main reason is that the application release process involves batch processing, and a specific instance is selected for each batch to determine the ratio or the number of instances. If elasticity processing is performed during the application release process, whether it is scaling in or out, there will be a problem of mismatch with the already allocated elastic data, resulting in abnormal release. In the prior art, the release and elasticity processing of applications are mutually exclusive. Elasticity processing of applications cannot be performed during the application release period. Correspondingly, during the process of application elasticity processing, the release needs to be stopped. Therefore, there is an urgent need for a more effective application monitoring method to solve the above problems. Summary of the Invention

[0003] In view of this, the embodiments of this specification provide an application monitoring method. One or more embodiments of this specification also relate to an application monitoring system, a computing device, a computer-readable storage medium, and a computer program product to solve the technical defects existing in the prior art.

[0004] According to the first aspect of the embodiments of this specification, an application monitoring method is provided, including:

[0005] Determine the instance release set associated with the target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set;

[0006] Monitor the instances in the instance release set during the release to obtain monitoring information;

[0007] In the case where it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in the release state, generate instance change information corresponding to the target application based on the monitoring information, and synchronize the instance change information to the data center node.

[0008] According to the second aspect of the embodiments of this specification, another application monitoring method is provided, including:

[0009] Determine the instance release set associated with the target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set;

[0010] Monitor the instances in the instance release set during the release to obtain monitoring information;

[0011] When it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in a to-be-released state, update the batch record information based on the monitoring information;

[0012] Continue to release the instance release set containing the changed instance based on the updated batch record information.

[0013] According to the third aspect of the embodiments of the present specification, an application monitoring system is provided, including a server, an application monitoring node, and a data center node:

[0014] The server is configured to determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set;

[0015] The application monitoring node is configured to perform instance monitoring on the instance release set being released, obtain monitoring information, and send the monitoring information to the server;

[0016] The server is configured to, when it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in a released state, generate instance change information corresponding to the target application based on the monitoring information, and synchronize the instance change information to the data center node.

[0017] According to the fourth aspect of the embodiments of the present specification, another application monitoring system is provided, including:

[0018] Including a server and an application monitoring node:

[0019] The server is configured to determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set;

[0020] The application monitoring node is configured to perform instance monitoring on the instance release set being released, obtain monitoring information, and send the monitoring information to the server;

[0021] The server is configured to, when it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in a to-be-released state, update the batch record information based on the monitoring information; continue to release the instance release set containing the changed instance based on the updated batch record information.

[0022] According to the fifth aspect of the embodiments of the present specification, an application monitoring device is provided, including:

[0023] A publishing module, configured to determine a set of instance publications associated with a target application, and publish the instances to be published in the set of instance publications based on batch record information corresponding to the set of instance publications;

[0024] A monitoring module, configured to perform instance monitoring on the set of instance publications during the publishing process to obtain monitoring information;

[0025] A synchronization module, configured to, when it is determined according to the monitoring information that the set of instance publications contains changed instances and the changed instances are in a published state, generate instance change information corresponding to the target application based on the monitoring information, and synchronize the instance change information to a data center node.

[0026] According to a sixth aspect of the embodiments of the present specification, another application monitoring device is provided, including:

[0027] A publishing module, configured to determine a set of instance publications associated with a target application, and publish the instances to be published in the set of instance publications based on batch record information corresponding to the set of instance publications;

[0028] A monitoring module, configured to perform instance monitoring on the set of instance publications during the publishing process to obtain monitoring information;

[0029] An update module, configured to, when it is determined according to the monitoring information that the set of instance publications contains changed instances and the changed instances are in a state to be published, update the batch record information based on the monitoring information;

[0030] A continue publishing module, configured to continue publishing the set of instance publications including the changed instances based on the updated batch record information.

[0031] According to a seventh aspect of the embodiments of the present specification, a computing device is provided, including:

[0032] A memory and a processor;

[0033] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above application monitoring method are implemented.

[0034] According to an eighth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores computer-executable instructions. When the instructions are executed by a processor, the steps of the above application monitoring method are implemented.

[0035] According to a ninth aspect of the embodiments of the present specification, there is provided a computer program product, including a computer program / instructions, which when executed by a processor implement the steps of the above application monitoring method.

[0036] In an embodiment of the present specification, by determining a set of instance releases associated with a target application and releasing the to-be-released instances in the set of instance releases based on the batch record information corresponding to the set of instance releases; monitoring the instances in the set of instance releases during the release to obtain monitoring information; in the case where it is determined according to the monitoring information that the set of instance releases contains changed instances and the changed instances are in the release state, generating instance change information corresponding to the target application based on the monitoring information and synchronizing the instance change information to the data center node. It realizes that during the process of releasing the to-be-released instances in the set of instance releases corresponding to the target application, the set of instance releases allows instance changes, that is, adding or deleting instances (scaling up or down). Then, by monitoring the set of instance releases through the application monitoring node, instance change information can be generated based on the determined monitoring information and the instance change information can be synchronized to the data center node, realizing elastic processing during the release of the target application. Completing the compatibility between the release and elasticity of the target application, optimizing the release process of the target application, and improving the release and elasticity efficiency of the target application. Description of the Drawings

[0037] Figure 1 is a schematic diagram of the processing process of an application monitoring method provided by an embodiment of the present specification;

[0038] Figure 2 is a flowchart of an application monitoring method provided by an embodiment of the present specification;

[0039] Figure 3 is a flowchart of another application monitoring method provided by an embodiment of the present specification;

[0040] Figure 4 is a flowchart of the processing process of an application monitoring method provided by an embodiment of the present specification;

[0041] Figure 5 is a schematic diagram of the application release of an application monitoring method provided by an embodiment of the present specification;

[0042] Figure 6 is a structural diagram of an application monitoring system provided by an embodiment of the present specification;

[0043] Figure 7 is a structural diagram of another application monitoring system provided by an embodiment of the present specification;

[0044] Figure 8It is a schematic structural diagram of an application monitoring device provided by an embodiment of this specification;

[0045] Figure 9 It is a schematic structural diagram of another application monitoring device provided by an embodiment of this specification;

[0046] Figure 10 It is a structural block diagram of a computing device provided by an embodiment of this specification. Specific implementation manners

[0047] In the following description, many specific details are set forth in order to provide a thorough understanding of this specification. However, this specification can be implemented in many other ways different from those described herein, and those skilled in the art can make similar generalizations without departing from the connotation of this specification. Therefore, this specification is not limited by the specific implementations disclosed below.

[0048] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a", "the", and "said" used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0049] It should be understood that although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0050] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for the user to choose to authorize or reject.

[0051] First, the noun terms involved in one or more embodiments of this specification are explained.

[0052] Automation elasticity: Achieve dynamic elasticity capabilities without manual intervention through metrics or scheduling methods.

[0053] Kubernetes, abbreviated as K8s, is an abbreviation formed by replacing the 8 characters "ubernete" in the middle of the name with 8. It is an open-source container orchestration engine designed to manage containerized applications on multiple hosts in a cloud platform. The goal of Kubernetes is to simplify the deployment and operation of containers and provide an efficient way to manage the lifecycle of containerized applications. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance, which can automate the deployment, scaling, and management of containerized applications. It supports the automatic deployment, automatic scaling, autoscaling, and automatic management of containers, and also provides functions such as service discovery, load balancing, naming and discovery, and resource monitoring.

[0054] Figure 1 It is a schematic diagram of the processing process of an application monitoring method provided by an embodiment of this specification; as Figure 1 shown, in the scenario of releasing a target application, determine the instance release set associated with the target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set. During the release process of the to-be-released instances in the instance release set, monitor the instance release set during release through an application monitoring node to obtain monitoring information. In the case where it is determined based on the monitoring information that the instance release set contains changed instances and the changed instances are in the release state, if it is in the non-release state at this time, generate instance change information corresponding to the target application based on the monitoring information and synchronize the instance change information to the data center node. If it is in the release state at this time, generate instance change information corresponding to the target application based on the monitoring information, and while synchronizing the instance change information to the data center node, use the change engine to update the batch record information based on the monitoring information. Then continue with the release of the target application.

[0055] During the process of releasing the to-be-released instances in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, adding or deleting instances (scaling up or down). Then, by monitoring the instance release set through an application monitoring node, instance change information can be generated based on the determined monitoring information and the instance change information can be synchronized to the data center node, realizing elastic processing during the release process of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0056] In this specification, an application monitoring method is provided. This specification also relates to an application monitoring system, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail one by one in the following embodiments.

[0057] See Figure 2 , Figure 2 which shows a flowchart of an application monitoring method provided according to an embodiment of this specification, specifically including the following steps.

[0058] Step 202: Determine the instance release set associated with the target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set.

[0059] Specifically, the target application can be any application that has been developed and is to be released. The fields of the target application include but are not limited to client applications and underlying application services; the instance release set is the function set corresponding to the target application, and the to-be-released instances in the instance release set correspond to the functions or function sets of the target application; the batch record information refers to the information record composed of the release batch information of each to-be-released instance in the instance release set; each to-be-released instance corresponds to a release batch.

[0060] Based on this, determine the target application to be released and the instance release set associated with the target application to be released. Determine the batch record information corresponding to the instance release set, and release the to-be-released instances in the instance release set sequentially according to the batch record information; or, synchronously release each to-be-released instance in the instance release set according to the batch record information.

[0061] In actual application, the to-be-released instances included in the instance release set correspond to the functions or function sets of the target application. Releasing the to-be-released instances can actually be regarded as releasing the target application. Releasing the to-be-released instances in the instance release set based on the batch record information may achieve the purpose of batch release.

[0062] Furthermore, considering that the data center node provides data synchronization services during the release process of the target application, and the data center node records the to-be-released nodes associated with the target application, therefore, when releasing the target application, at least one to-be-released instance can be obtained through the data center node. The specific implementation is as follows:

[0063] Determine the instance attribute information associated with the target application based on the instance information recorded by the data center node; generate an instance acquisition request based on the instance attribute information and send it to the data center node; receive at least one to-be-released instance fed back by the data center node in response to the instance acquisition request, and store the at least one to-be-released instance in the instance release set.

[0064] Specifically, instance information refers to the instance information of the target application stored in the data center node and the instances associated with other applications to be released; instance attribute information can be the ID of the instance, or the name of the instance, etc., which is the instance representation information used to determine the instance; an instance acquisition request refers to a computer instruction for acquiring the instance to be released.

[0065] Based on this, determine the instance attribute information associated with the target application based on the instance information recorded by the data center node. Generate an instance acquisition request based on the instance attribute information and send it to the data center node for acquiring the instance to be released corresponding to the instance attribute information at the data center node. Receive at least one instance to be released fed back by the data center node in response to the instance acquisition request, and store the at least one instance to be released in the instance release set, or construct an instance release set based on the at least one instance to be released.

[0066] For example, the data center node records the instance information of the instances associated with each application to be released. For the target application, the instance attribute information associated with it can be determined, that is, instance name: Instance A, Instance B, Instance C, Instance D; generate an instance acquisition request based on the instance attribute information and send it to the data center node. The data center node determines the instances to be released corresponding to each instance attribute information based on the instance attribute information: Instance A, Instance B, Instance C, Instance D, namely, the instance to be released A, the instance to be released B, the instance to be released C, the instance to be released D, and uses the above 4 instances as the feedback of the instance acquisition request.

[0067] In summary, acquire at least one instance to be released of the target application at the data center node, thereby improving the accuracy of determining the instance to be released.

[0068] Furthermore, considering that the instance release set can contain multiple instances to be released, and each instance to be released can correspond to a different release batch, release the instances to be released in the instance release set based on the batch record information, thereby realizing the ordered release of the instances to be released in the instance release set. The specific implementation is as follows:

[0069] Determine the batch label of each instance to be released in the instance release set according to the instance release policy, where the instance release policy is used to represent the release order of the instances to be released in the instance release set; determine the batch record information corresponding to the instance release set based on the batch label of each instance to be released, and release the instances to be released in the instance release set based on the batch record information.

[0070] Specifically, the instance release strategy is used to determine the release order of the instances to be released in the instance release set; the instance release strategy can be determined according to the instance release priorities of each instance to be released. If the priority of the instance to be released is relatively high, the batch label is the first batch or other previous batches; the batch label represents batch information such as the first batch, the second batch, etc.

[0071] Based on this, batch labels are assigned to each instance to be released in the instance release set according to the instance release strategy. The batch record information corresponding to the instance release set is determined based on the batch labels of each instance to be released, which is used to describe the release batches of each instance to be released in the instance release set. The instances to be released in the instance release set are released sequentially based on the batch record information, or the instances to be released in the instance release set are released simultaneously based on the batch record information.

[0072] Continuing with the above example, the instances to be released are Instance A to be released, Instance B to be released, Instance C to be released, and Instance D to be released. The batch label of each instance is determined according to the instance release strategy. The first batch is used as the batch label of Instance A to be released, the second batch is used as the batch label of Instance B to be released, the third batch is used as the batch label of Instance C to be released, and the fourth batch is used as the batch label of Instance D to be released. By combining the instance labels of each instance, the batch record information can be obtained: First batch: Instance A to be released; Second batch: Instance B to be released; Third batch: Instance C to be released; Fourth batch: Instance D to be released. Then, Instance A to be released, Instance B to be released, Instance C to be released, and Instance D to be released are released according to the batch record information.

[0073] To sum up, the instances to be released in the instance release set are released sequentially based on the batch record information, thereby improving the orderliness of the release of each instance to be released in the instance release set.

[0074] Step 204: Monitor the instances in the instance release set during the release process to obtain monitoring information.

[0075] Specifically, after determining the instance release set associated with the target application and releasing the instances to be released in the instance release set based on the batch record information corresponding to the instance release set, the instances in the instance release set during the release process can be monitored to obtain monitoring information. Among them, the monitoring information is the instance information obtained by monitoring the release status of the original instances to be released in the instance release set, and the instance information obtained by monitoring the newly added instances to be released in the instance release set.

[0076] Based on this, after determining the instance release set associated with the target application as described above, and releasing the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set, the instance monitoring is performed on the instance release set during the release process by the application monitoring node, monitoring the original to-be-released instances in the instance release set, and monitoring whether there are new instances in the instance release set, and taking the instance change information obtained by monitoring the instances in the instance release set as the monitoring information for the instance release set.

[0077] In practical applications, during the process of releasing the to-be-released instances included in the instance release set, capacity reduction can be performed based on the to-be-released instances included in the instance release set, that is, stopping the release of the specified to-be-released instances; capacity expansion can also be performed on the instance release set, that is, adding new to-be-released instances and releasing them based on the original to-be-released instances in the instance release set. The application monitoring node is used to monitor the changes in the instances in the instance release set and generate monitoring information based on the changes in the instances in the instance release set.

[0078] Furthermore, considering that during the release process of the to-be-released instances in the instance release set, the instance release status of the to-be-released instances in the instance release set is also different at different times, and thus the obtained monitoring information is also different. The specific implementation is as follows:

[0079] The application monitoring node monitors the release status of the instances included in the instance release set during the release process, and obtains the to-be-released status information or in-release status information or release-completed status information of each instance in the instance release set; generates the monitoring information based on the to-be-released status information or in-release status information or release-completed status information of each target instance in the instance release set.

[0080] Specifically, the application monitoring node is used to monitor the instance change information of the instance release set; the application monitoring node can be a program software or an installed system service, and has the ability to sense or monitor the changes in the instances in the instance release set; the application monitoring node is used to monitor the changed instances and new instances in the instance release set.

[0081] Based on this, the application monitoring node monitors the release status of each instance included in the instance release set during the release process. The instances in the instance release set can be in the to-be-released state, in-release state or release-completed state. Then each instance in the instance release set corresponds to a release status. By monitoring the release status of each instance included in the instance release set during the release process, the to-be-released status information or in-release status information or release-completed status information of each instance in the instance release set can be obtained. The monitoring information for the instance release set can be composed based on the to-be-released status information or in-release status information or release-completed status information of each target instance in the instance release set.

[0082] In summary, during the release process of the instances to be released in the instance release set, the release status of the instances to be released is monitored, so as to ensure the orderly release of the instances to be released in the instance release set, and the release situation of the instances to be released can be grasped in real time by monitoring the release status.

[0083] Step 206: When it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in the release status, generate instance change information corresponding to the target application based on the monitoring information and synchronize it to the data center node.

[0084] Specifically, after the instance monitoring of the instance release set during release is performed through the application monitoring node to obtain the monitoring information, when it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in the release status, generate instance change information corresponding to the target application based on the monitoring information and synchronize it to the data center node. Among them, a changed instance is an instance whose release status changes in the instance release dimension during the instance release process, such as pausing release, adding a release, etc.; a changed instance can be an instance whose release status of the original instance to be released in the instance release set changes, or a newly added instance to be released based on the original instances to be released included in the instance release set; the release status is used to represent the release stage of the instances to be released in the instance release set; the release status can be one of the to-be-released status, releasing status, and released status; the instance change information is the description information of the instances in the instance release set when the instances in the instance release set change; the data center node is used to record the number of instances corresponding to the target application; the data center node provides a data synchronization service during the release process of the target application and records the released instances corresponding to the target application.

[0085] Based on this, after the instance monitoring of the instance release set during release is performed through the application monitoring node to obtain the monitoring information, when it is determined according to the monitoring information that the instance release set contains a changed instance and the changed instance is in the release status, it means that the instances to be released in the instance release set change, or newly added instances to be released are included in the instance release set. Generate instance change information corresponding to the target application based on the monitoring information and synchronize it to the data center node. The instance change information is used to describe the number of instances and the global instance status in the current instance release set.

[0086] In practical applications, the changed instances included in the instance release set can be the instances to be released in the instance release set, or the newly added instances to be released in the instance release set; in the case where the changed instance is the instance to be released in the instance release set, the change of the instance to be released can be the suspension of the instance to be released caused by the scaling down of the target application release. In the case of newly adding an instance to be released in the instance release set, it can be due to the scaling up of the target application release resulting in the addition of new instances to be released in the instance release set.

[0087] In addition, in another embodiment, the monitoring of instance changes can also be combined with a change engine to monitor the instance release set during the release process to obtain monitoring information. Furthermore, an instance number synchronizer is developed inside K8S or outside the non-K8S scenario, and the updated batch record information is directly synchronized to the data center node using the instance number synchronizer, thereby completing the compatibility between the release and elasticity of the target application and optimizing the release process of the target application.

[0088] Furthermore, considering that during the monitoring of the instance release set, the changed instance can be a newly added instance, for the newly added instance, corresponding instance change information can be generated, and the specific implementation is as follows:

[0089] In the case where it is determined based on the monitoring information that the changed instance is a newly added instance, extract the label information of the newly added instance from the monitoring information; generate instance addition information based on the label information of the newly added instance, and use the instance addition information as the instance change information corresponding to the target application.

[0090] Specifically, the newly added instance is the instance added to the instance release set on the basis of the original instances to be released in the instance release set; correspondingly, the instance addition information is the attribute information such as the instance name and instance ID of the newly added instance.

[0091] Based on this, in the case where it is determined based on the monitoring information that the changed instance is a newly added instance, it means that there are newly added instances to the instance release set during the instance release process. Extract the label information of the newly added instance from the monitoring information. Generate instance addition information based on the label information of the newly added instance, and use the instance addition information as the instance change information corresponding to the target application.

[0092] To sum up, during the release process of the instances to be released in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, newly added instances (scaling up). Then, by monitoring the instance release set through the application monitoring node, instance change information can be generated based on the determined monitoring information, and the instance change information can be synchronized to the data center node to achieve elastic processing during the release process of the target application.

[0093] Further, considering that during the monitoring of the instance release set, the changed instance can be a modified instance. For the modified instance, corresponding instance change information can be generated. The specific implementation is as follows:

[0094] In the case where it is determined based on the monitoring information that the changed instance is a modified instance, extract the label information of the modified instance from the monitoring information; generate instance modification information based on the label information of the modified instance, and use the instance modification information as the instance change information corresponding to the target application.

[0095] Specifically, the modified instance is a set obtained by modifying the original instance to be released in the instance release set; the modification can be a release suspension operation for the instance to be released; correspondingly, the instance modification information is the attribute information such as the instance name and instance ID of the modified instance, as well as the modification method information, including but not limited to modification methods such as suspension of release and deletion in the instance set.

[0096] Based on this, in the case where it is determined based on the monitoring information that the changed instance is a modified instance, it means that there is an instance that needs to be modified during the instance release process of the instance release set. Extract the label information of the modified instance from the monitoring information. Generate instance modification information based on the label information of the modified instance, and use the instance modification information as the instance change information corresponding to the target application.

[0097] Continuing with the above example, the instances to be released in the instance release set are instance A to be released, instance B to be released, instance C to be released, and instance D to be released. During the release process of the above instances to be released, a new instance E to be released can be added in the scaling-up scenario, and then generate the instance addition information "add instance E"; the addition information is the instance change information. It is also possible to modify instance D in the scaling-down scenario, and then generate the instance modification information "suspend the release of instance D"; the modification information is the instance change information.

[0098] In summary, during the release process of the instances to be released in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, deleting instances (scaling down). Then, by using the application monitoring node to monitor the instance release set, instance change information can be generated based on the determined monitoring information, and the instance change information can be synchronized to the data center node, realizing elastic processing during the release of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0099] It should be noted that in actual applications, since the release of the target application involves the release of multiple instances in the instance release set, and each instance corresponds to a release batch. Therefore, during the release of the instances to be released in the instance release set, there may be situations where instances are added (scaled out) and instances are deleted (scaled in) simultaneously. For example: during the release of instances in the instance release set (the first batch: instance A to be released; the second batch: instance B to be released; the third batch: instance C to be released; the fourth batch: instance D to be released, instance E to be released), instance scaling out can be performed: adding the fifth batch: instance F to be released, and adding instance G to be released in any batch of corresponding instances; instance scaling in can also be performed: deleting instance D to be released corresponding to the fourth batch. Therefore, the operations of "adding the fifth batch: instance F to be released", "adding instance G to be released in any batch of corresponding instances", and "deleting instance D to be released corresponding to the fourth batch" can be carried out synchronously. The specific implementation method can refer to the above embodiments and will not be elaborated here.

[0100] See Figure 3 , Figure 3 shows a flowchart of another application monitoring method provided according to an embodiment of the present specification, which specifically includes the following steps.

[0101] Step 302: Determine the instance release set associated with the target application, and release the instances to be released in the instance release set based on the batch record information corresponding to the instance release set.

[0102] Based on this, determine the target application to be released and the instance release set associated with the target application to be released. Determine the batch record information corresponding to the instance release set, and release the instances to be released in the instance release set in sequence according to the batch record information; or, synchronously release each instance to be released in the instance release set according to the batch record information.

[0103] In actual applications, the instances to be released included in the instance release set correspond to the functions or function sets of the target application. Releasing the instances to be released can actually be regarded as the release of the target application. Releasing the instances to be released in the instance release set based on the batch record information may achieve the purpose of batch release.

[0104] Furthermore, considering that the data center node provides data synchronization services during the release of the target application, and the data center node records the nodes to be released associated with the target application, therefore, when the target application is released, at least one instance to be released can be obtained through the data center node. The specific implementation is as follows:

[0105] Determine the instance attribute information associated with the target application based on the instance information recorded by the data center node; generate an instance acquisition request based on the instance attribute information and send it to the data center node; receive at least one instance to be published fed back by the data center node in response to the instance acquisition request, and store the at least one instance to be published in the instance publication set.

[0106] Based on this, determine the instance attribute information associated with the target application based on the instance information recorded by the data center node. Generate an instance acquisition request based on the instance attribute information and send it to the data center node for obtaining the instance to be published corresponding to the instance attribute information at the data center node. Receive at least one instance to be published fed back by the data center node in response to the instance acquisition request, and store the at least one instance to be published in the instance publication set, or construct an instance publication set based on the at least one instance to be published.

[0107] In summary, obtain at least one instance to be published of the target application at the data center node, thereby improving the accuracy of determining the instance to be published.

[0108] Furthermore, considering that the instance publication set may contain multiple instances to be published, and each instance to be published may correspond to a different release batch, publish the instances to be published in the instance publication set based on the batch record information, so as to realize the orderly publication of the instances to be published in the instance publication set. The specific implementation is as follows:

[0109] Determine the batch labels of the instances to be published in the instance publication set according to the instance publication strategy, where the instance publication strategy is used to represent the publication order of the instances to be published in the instance publication set; determine the batch record information corresponding to the instance publication set based on the batch labels of the instances to be published, and publish the instances to be published in the instance publication set based on the batch record information.

[0110] Based on this, assign batch labels to the instances to be published in the instance publication set according to the instance publication strategy. Determine the batch record information corresponding to the instance publication set based on the batch labels of the instances to be published, which is used to describe the release batches of the instances to be published in the instance publication set. Publish the instances to be published in the instance publication set sequentially based on the batch record information, or publish the instances to be published in the instance publication set simultaneously based on the batch record information.

[0111] In summary, publish the instances to be published in the instance publication set sequentially based on the batch record information, thereby improving the orderliness when publishing each instance to be published in the instance publication set.

[0112] Step 304: Monitor the instances in the instance publication set during publication to obtain monitoring information.

[0113] Based on this, after determining the instance release set associated with the target application as described above and releasing the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set, the instance monitoring of the instance release set during the release process is performed through the application monitoring node, monitoring the original to-be-released instances in the instance release set and whether new instances are added to the instance release set, and using the instance change information obtained from monitoring the instances in the instance release set as the monitoring information for the instance release set.

[0114] In practical applications, during the process of releasing the to-be-released instances included in the instance release set, it is possible to perform capacity reduction based on the to-be-released instances included in the instance release set, that is, stop the release of the specified to-be-released instances; it is also possible to perform capacity expansion on the instance release set, that is, based on the original to-be-released instances in the instance release set, add new to-be-released instances and perform the release. The application monitoring node is used to monitor the changes in the instances in the instance release set and generate monitoring information based on the changes in the instances in the instance release set.

[0115] Furthermore, considering that during the release process of the to-be-released instances in the instance release set, the instance release status of the to-be-released instances in the instance release set is also different at different times, and thus the obtained monitoring information is also different. The specific implementation is as follows:

[0116] The application monitoring node performs release status monitoring on the instances included in the instance release set during the release process to obtain the to-be-released status information or in-release status information or release-completed status information of each instance in the instance release set; and generates the monitoring information based on the to-be-released status information or in-release status information or release-completed status information of each target instance in the instance release set.

[0117] Based on this, the application monitoring node performs release status monitoring on each instance included in the instance release set during the release process. The instances in the instance release set can be in the to-be-released state or in-release state or release-completed state. Then each instance in the instance release set corresponds to a release status. By performing release status monitoring on each instance included in the instance release set during the release process, the to-be-released status information or in-release status information or release-completed status information of each instance in the instance release set can be obtained. The monitoring information for the instance release set can be formed based on the to-be-released status information or in-release status information or release-completed status information of each target instance in the instance release set.

[0118] In summary, during the release process of the to-be-released instances in the instance release set, release status monitoring is performed on the to-be-released instances, so as to ensure the orderly release of the to-be-released instances in the instance release set and be able to grasp the release situation of the to-be-released instances in real time through monitoring the release status.

[0119] Step 306: When it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a to-be-released state, update the batch record information based on the monitoring information.

[0120] Specifically, after monitoring the instances in the instance release set during the release to obtain the monitoring information, when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a to-be-released state, the batch record information can be updated based on the monitoring information, where the changed instances refer to the instances whose states have changed or new instances have been added.

[0121] Based on this, after monitoring the instances in the instance release set during the release to obtain the monitoring information, when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a to-be-released state, update the batch record information based on the monitoring information. When it is determined according to the monitoring information that the instance release set contains changed instances, it means that the instance states of the to-be-released instances in the instance release set have changed, or there are new instances in the instance release set. The changed instances being in a to-be-released state means that the changed instances have not been released yet.

[0122] Furthermore, considering that the to-be-released instances in the instance release set may cause the instance release to stop due to scale-down, or new instances to be released may be added to the instance release set due to scale-up, therefore, when the instance release set changes, it is necessary to update the batch record information to ensure information consistency. The specific implementation is as follows:

[0123] Match the instance batch information contained in the monitoring information with the batch record information, and determine the correction information according to the matching result; correct the batch record information based on the correction information.

[0124] Specifically, the instance batch information refers to the instance name information and batch information of each instance contained in the instance release set; the matching result refers to the comparison information between the batch information of each batch contained in the instance batch information and the batch information of each batch in the batch record information; the matching result can be a complete match, a partial match, or a non-match; for example: if the instance batch information contains the fourth batch and the batch record information does not contain the fourth batch, it is determined as "non-match"; if the instance batch information contains the third batch, and the third batch corresponds to instance B and instance C, while the third batch in the batch record information corresponds to instance B, it is determined as "partial match"; the correction information is used to modify the batch record information according to the instance batch information.

[0125] Based on this, the instance batch information included in the monitoring information is matched with the batch record information, and the difference information between the instance batch information and the batch record information is used as the matching result, and the correction information is determined according to the matching result. The batch record information is updated based on the correction information.

[0126] Continuing with the previous example, when the instance batch information is "First batch: instances A to be released; Second batch: instances B to be released; Third batch: instances C to be released, instances D to be released" and the batch record information is "First batch: instances A to be released; Second batch: instances B to be released; Third batch: instances C to be released", the matching result is partial match for the third batch. Then, "Third batch: instances C to be released, instances D to be released" is used as the correction information to modify "Third batch: instances C to be released" in the batch record information.

[0127] In summary, when the instance release set changes, the batch record information is updated to ensure information consistency and achieve information synchronization.

[0128] Furthermore, considering that there may be cases of deleting instances or adding new instances in the instance release set, the batch record information needs to be updated accordingly for various cases. The specific implementation is as follows:

[0129] When it is determined based on the correction information that there are deleted instances in the instance release set, the batch information to be deleted is determined in the batch record information based on the deletion batch information of the deleted instances, and the batch information to be deleted is deleted; when it is determined based on the correction information that there are newly added priority release instances in the instance release set, the new position information is determined in the batch record information based on the priority information of the newly added priority release instances, and the information of the newly added priority release instances of the newly added priority release instances is recorded in the batch record information based on the new position information; when it is determined based on the correction information that there are newly added sequential release instances in the instance release set, the information of the newly added sequential release instances of the newly added sequential release instances is sequentially added to the batch record information based on the sequential information of the newly added sequential release instances.

[0130] Specifically, a deleted instance refers to an instance in the instance release set that is in a stopped release state, and the deleted instance needs to be removed from the instance release set; the deleted batch information is the batch information corresponding to the deleted instance; the batch information to be deleted is the batch information in the batch record information that is associated with the deleted instance; a newly added instance with higher priority for release is an instance that needs to be released between any instances in the instance release set; the priority information indicates the release urgency of the newly added instance with higher priority for release; the newly added location information is the location information of the target location where the newly added instance with higher priority for release is added to the instance release set; the information of the newly added instance with higher priority for release is the batch information corresponding to the newly added instance with higher priority for release; a newly added instance for sequential release is an instance that needs to be released after the instance at the end of the release position in the instance release set; the sequence information indicates the release sequence of the newly added instance for sequential release; the information of the newly added instance for sequential release is the batch information of the newly added instance for sequential release.

[0131] Based on this, when it is determined based on the correction information that there is a deleted instance in the instance release set, it means that there is an instance in the instance release set that needs to be stopped from being released. The batch information to be deleted is determined in the batch record information based on the deleted batch information of the deleted instance, and the batch information to be deleted in the batch record information is deleted. When it is determined based on the correction information that there is a newly added instance with higher priority for release in the instance release set, it means that the newly added instance with higher priority for release needs to be released between any instances in the instance release set. The newly added location information is determined in the batch record information based on the priority information of the newly added instance with higher priority for release, and the information of the newly added instance with higher priority for release of the newly added instance with higher priority for release is recorded in the batch record information based on the newly added location information, and the batch information after the information of the newly added instance with higher priority for release is appropriately modified. When it is determined based on the correction information that there is a newly added instance for sequential release in the instance release set, it means that the newly added instance for sequential release can be released after the instance at the end of the release position included in the instance release set. The information of the newly added instance for sequential release of the newly added instance for sequential release is sequentially added to the batch record information based on the sequence information of the newly added instance for sequential release.

[0132] Continuing with the above example, when the instance release set includes instances to be released such as "First batch: Instance A to be released; Second batch: Instance B to be released; Third batch: Instance C to be released, Instance D to be released", the batch record information is "First batch: Instance A to be released; Second batch: Instance B to be released; Third batch: Instance C to be released, Instance D to be released". In the scenario of capacity reduction, it is to delete the instances included in the instance release set. When deleting Instance D to be released, the instance information corresponding to the third batch in the batch record information needs to be deleted according to the deletion situation; in the scenario of capacity expansion, the newly added instances can be arranged to be released after Instance C to be released in the third batch; or the newly added instances can be arranged before any instance.

[0133] In summary, when there are deleted instances, newly added instances with priority for release, and newly added instances for sequential release in the instance release set, the batch record information is updated respectively to achieve the consistency between the batch record information and the instance release situation in the instance release set.

[0134] Step 308: Continue to release the instance release set containing the changed instances based on the updated batch record information.

[0135] Specifically, when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in the to-be-released state, after updating the batch record information based on the monitoring information, the instance release set containing the changed instances can be continuously released based on the updated batch record information. Here, continuously releasing the instance release set containing the changed instances means that when some of the to-be-released instances in the instance release set have been released, continue to release the unreleased instances in the instance release set containing the changed instances.

[0136] Based on this, when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in the to-be-released state, after updating the batch record information based on the monitoring information, continue to release the instance release set containing the changed instances based on the updated batch record information, and continue to release the instances that need to be released in the instance release set.

[0137] Furthermore, considering that during the process of releasing the to-be-released instances in the instance release set, there may be situations where to-be-released instances are added to the instance release set or to-be-released instances in the instance release set are deleted. At this time, it is necessary to continue to release the instance release set containing the changed instances. The specific implementation is as follows:

[0138] When the changed instance included in the instance release set is a newly added instance, determine the first release instance and the changed instance included in the instance release set based on the updated batch record information, where the first release instance is used to represent the original to-be-released instances in the instance release set; when the first release instance is successfully released, continue to release the changed instance based on the updated batch record information; when the first release instance is not released yet, continue to release the first release instance and the changed instance based on the updated batch record information; when the changed instance included in the instance release set is a modified instance, continuing to release the instance release set containing the changed instance based on the updated batch record information includes: determining the second release instance included in the instance release set based on the updated batch record information, and continuing to release the second release instance, where the second release instance is used to represent the modified instances in the instance release set that are in the to-be-released state.

[0139] Specifically, a newly added instance refers to an instance added to the instance release set on the basis that the instance release set contains to-be-released instances; the first release instance represents the original to-be-released instances in the instance release set; the changed instance is the newly added instance in the instance release set; a modified instance refers to an instance in which the original to-be-released instance in the instance release set is modified; a modified instance can be a modification of the instance release status. For example, if the to-be-released instance in the instance release set changes from the to-be-released state to the stopped release state, then the to-be-released instance is a modified instance; the second release instance refers to the modified instances in the instance release set that are in the to-be-released state.

[0140] Based on this, when the changed instance included in the instance release set is a newly added instance, it means that the instance release set is in an expanded state, and new to-be-released instances are added on the basis of the original to-be-released instances in the instance release set. Determine the first release instance and the changed instance included in the instance release set based on the updated batch record information; when the first release instance is successfully released, it means that all the original to-be-released instances in the instance release set have completed the instance release, and continue to release the changed instance based on the updated batch record information. When the first release instance is not released yet, it means that the original to-be-released instances in the instance release set have not been fully released, and continue to release the first release instance and the changed instance based on the updated batch record information. When the changed instance included in the instance release set is a modified instance, it means that the instance release set is in a contracted state, determine the second release instance that needs to be released included in the instance release set based on the updated batch record information, and continue to release the second release instance.

[0141] Continuing with the above example, in the scenario of capacity expansion, based on the original batches "First batch: instances A to be released; Second batch: instances B to be released; Third batch: instances C to be released", "Fourth batch: instances D to be released" can be added. Then, it is necessary to continue the release for the instance release set that includes the newly added instances D to be released. When instances A to be released, instances B to be released, and instances C to be released are all released, continue to release instances D to be released. When there are unreleased instances among instances A to be released, instances B to be released, and instances C to be released, release instances D to be released after instances A to be released, instances B to be released, and instances C to be released are released. In the scenario of capacity reduction, on the basis of the original batches "First batch: instances A to be released; Second batch: instances B to be released; Third batch: instances C to be released", instances C to be released can be deleted or the release can be paused. Then, only instances A to be released and instances B to be released need to be released.

[0142] In summary, in the case where the changed instances included in the instance release set are newly added instances, and in the case where the changed instances included in the instance release set are modified instances, continue to release the instances included in the instance release set respectively, so as to improve the instance release efficiency.

[0143] Furthermore, considering that the data center node records the number of instances corresponding to the target application and provides data synchronization services during the release process of the target application, when the batch record information is updated, it is necessary to perform data synchronization based on the updated batch record information and synchronize it to the data center node. The specific implementation is as follows:

[0144] Synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node.

[0145] Specifically, the instance record information refers to the instance information of the instances associated before and during the release of the target application; the instance record information includes but is not limited to the number of instances to be released associated with the target application, the release status of each instance to be released, and during the release process of the target application, instance capacity expansion information and instance capacity reduction information.

[0146] Based on this, synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node, and record information such as the number of instances, instance names, instance release status, and instance capacity expansion and reduction associated during the release process of the target application.

[0147] Continuing with the above example, in the scenario of capacity expansion, a fourth batch and the corresponding to-be-released instances D, E, and F are added to the original batch; "Fourth batch: To-be-released instance D, To-be-released instance E, To-be-released instance F" is sent to the data center node. Update the "To-be-released instance A, To-be-released instance B, To-be-released instance C" recorded by the data center node to "To-be-released instance A, To-be-released instance B, To-be-released instance C, To-be-released instance D, To-be-released instance E, To-be-released instance F".

[0148] In summary, during the process of releasing the to-be-released instances in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, adding or deleting instances (capacity expansion or contraction). Then, by monitoring the instance release set through the application monitoring node, the batch record information can be updated based on the determined monitoring information, thereby guiding the instance release set with instance changes to continue the release, realizing elastic processing during the release of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0149] It should be noted that in actual applications, since the release process of the target application involves the release of multiple instances in the instance release set, and each instance corresponds to a release batch. Therefore, during the process of releasing the to-be-released instances in the instance release set, there may be situations of both instance addition (capacity expansion) and instance deletion (contraction) at the same time. For example: during the release of instances in the instance release set (First batch: To-be-released instance A; Second batch: To-be-released instance B; Third batch: To-be-released instance C; Fourth batch: To-be-released instances D, E), capacity expansion of instances can be carried out: adding a fifth batch: To-be-released instance F, and adding a to-be-released instance G to the instances corresponding to any batch; instance contraction can also be carried out: deleting the to-be-released instance D corresponding to the fourth batch. Therefore, the operations of "adding a fifth batch: To-be-released instance F", "adding a to-be-released instance G to the instances corresponding to any batch", and "deleting the to-be-released instance D corresponding to the fourth batch" can be carried out synchronously. The specific implementation method can refer to the above embodiments and will not be elaborated here.

[0150] The following combines the attached Figure 4 , taking the application monitoring method provided in this specification in the example of application release as an example, to further illustrate the application monitoring method. Among them, Figure 4 shows the processing process flow chart of an application monitoring method provided in an embodiment of this specification, which specifically includes the following steps.

[0151] Step 402: Obtain the to-be-released instances associated with the target application stored in the metadata center and form an instance release set.

[0152] Combine Figure 5 Illustrate the release and elastic process of the application. For example Figure 5 As shown, the metadata center is used to store data such as resource data, batch data, elastic data, and release data. When the application publisher has a release requirement for the target application, obtain the instance to be released in the metadata center and construct the instance release set to be released.

[0153] Step 404: Batch process the instances to be released in the instance release set based on the batching strategy to obtain batch record information.

[0154] The application publisher formulates a batching strategy and batch processes instances 1, 2, and 3 included in the instance release set based on the batching strategy to obtain batch record information: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3". The batch record information is the original batch data.

[0155] Step 406: Release the instances to be released in the instance release set according to the batch record information.

[0156] In actual applications, when releasing the instances to be released, they can be released in the order of batch information or the instances to be released can be synchronously released. This embodiment does not make any restrictions on the release method.

[0157] During the release process of the instances to be released in the instance release set, there are two cases of compatibility between release and automated scaling out and compatibility between release and automated scaling in. The automated elastic service realizes scaling out and scaling in during the instance release process, assigns a scaling out label to the scaling out instance, and assigns a scaling in label to the scaling in instance.

[0158] Step 408: Monitor the instances in the instance release set during release through the application monitoring node to obtain monitoring information.

[0159] The application monitoring node is used to monitor the instance release set, monitor instance change data, and use the instance change data as monitoring information. The application monitoring node can be a resource coordination corrector, with the ability to monitor instance change data, synchronize data to the metadata center, and send instance change data to the change engine.

[0160] In instance applications, after obtaining the monitoring information, if it is not during the instance release period, the monitoring information can be only synchronized to the metadata center to modify the number of instances; if it is during the instance release period, while synchronizing the monitoring information to the metadata center, it is also necessary to correct the batch record information recorded by the change engine.

[0161] Step 410: Match the instance batch information included in the monitoring information with the batch record information, and determine the correction information according to the matching result.

[0162] In the expansion scenario, the instance change data monitored can be the increase in batches and the increase in instances. Based on the original instances 1, 2, and 3, instances 4, 5, and 6 are added as the fourth batch.

[0163] In the contraction scenario, the instance change data monitored can be the deletion of batches and the deletion of instances. Based on the original instances 1, 2, and 3, instance 3 is deleted, and there are no instances in the third batch.

[0164] Step 412: When it is determined based on the correction information that there are instances to be deleted in the instance release set, determine the batch information to be deleted in the batch record information based on the deletion batch information of the instances to be deleted, and delete the batch information to be deleted.

[0165] When there are instances to be deleted in the instance release set, it indicates a contraction situation. When the batch record information composed of the original instances and batches is "First batch: Instance 1; Second batch: Instances 2, 3; Third batch: Instances 4, 5; Fourth batch: Instance 6", if it is monitored that instances 1, 4, and 6 have been contracted, then modify the batch record information "First batch: Instance 1; Second batch: Instances 2, 3; Third batch: Instances 4, 5; Fourth batch: Instance 6" to: "First batch: -; Second batch: Instances 2, 3; Third batch: -, Instance 5; Fourth batch: -". The modified batch record information is the corrected batch data.

[0166] In addition, when it is determined based on the monitoring information that instance 1 has been deleted, but instance 1 has been released at the current moment, the change engine can be informed to take an ignore operation on instance 1 and synchronize the release status of instance 1. Thus, ensuring the orderly release of the target application.

[0167] Step 414: When it is determined based on the correction information that there are newly added priority release instances in the instance release set, determine the new position information in the batch record information based on the priority information of the newly added priority release instances, and record the new priority release instance information of the newly added priority release instances to the batch record information based on the new position information.

[0168] In the expansion scenario, batches and instances can be added before or after any of the three batches, or instances can be added after the original batches. Then, based on the original batch data: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3", after the addition is completed, the corrected batch data is obtained.

[0169] Step 416: When it is determined that there are newly added sequential release instances in the instance release set based on the correction information, add the newly added sequential release instance information of the newly added sequential release instances to the batch record information in sequence based on the sequence information of the newly added sequential release instances.

[0170] In the capacity expansion scenario, a fourth batch can also be added after the third batch. Then, based on the original batch data: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3", add "Fourth batch: Instance 4, Instance 5, Instance 6" to obtain the corrected batch data.

[0171] Step 418: Synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node.

[0172] Synchronize the updated batch record information to the metadata center to correct the actual number of instances in the metadata center.

[0173] Step 420: Continue to release the instance release set containing the changed instances based on the updated batch record information.

[0174] By adding a resource collaboration corrector to provide a resource collaboration repair service, a non-invasive application release and elastic method are realized, solving the problem that automation elasticity cannot be performed while the application is being released, and at the same time, the data can be kept synchronized, thus solving the compatibility problem between application release and elasticity.

[0175] In addition, the monitoring of instance changes can also be combined with the change engine to monitor the instance release set during the release to obtain monitoring information. Then, develop an instance number synchronizer inside K8S or outside the non-K8S scenario, and directly use the instance number synchronizer to synchronize the updated batch record information to the metadata center, thereby completing the compatibility between the release and elasticity of the target application and optimizing the release process of the target application.

[0176] In summary, during the process of releasing the to-be-released instances in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, adding or deleting instances (capacity expansion or contraction). Then, by monitoring the instance release set through the application monitoring node, the batch record information can be updated based on the determined monitoring information, and further guide the instance release set with instance changes to continue the release, realizing elastic processing during the release of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0177] Corresponding to the above method embodiments, this specification also provides application monitoring system embodiments. Figure 6The figure shows a structural diagram of an application monitoring system provided by an embodiment of this specification. As Figure 6 shown, the application monitoring system 600 includes a server 610, an application monitoring node 620, and a data center node 630: The server 610 is configured to determine an instance release set associated with a target application, and publish the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; The application monitoring node 620 is configured to perform instance monitoring on the instance release set during the release process, obtain monitoring information, and send the monitoring information to the server 610; The server 610 is configured to generate instance change information corresponding to the target application based on the monitoring information and synchronize the instance change information to the data center node 630 when it is determined according to the monitoring information that the instance release set includes changed instances and the changed instances are in the release state.

[0178] In actual application, the application monitoring system 600 includes a server 610, an application monitoring node 620, and a data center node 630: The server 610 determines an instance release set associated with a target application based on a release request submitted by an application publisher, determines a batching strategy corresponding to the application publisher, and determines batch record information corresponding to the instance release set based on the batching strategy. The to-be-released instances in the instance release set are published based on the batch record information. The application monitoring node 620 performs instance monitoring on the instance release set during the release process, obtains monitoring information, and sends the monitoring information to the server 610. The server 610 generates instance change information corresponding to the target application based on the monitoring information and synchronizes the instance change information to the data center node 630 when it is determined according to the monitoring information that the instance release set includes changed instances and the changed instances are in the release state, thereby changing the number of instances associated with the target application.

[0179] The server 610 is configured to extract label information of the newly added instances from the monitoring information; generate instance addition information based on the label information of the newly added instances, and use the instance addition information as the instance change information corresponding to the target application; when it is determined based on the monitoring information that the changed instance is a modified instance, generating the instance change information corresponding to the target application based on the monitoring information includes: extracting label information of the modified instance from the monitoring information; generating instance modification information based on the label information of the modified instance, and using the instance modification information as the instance change information corresponding to the target application.

[0180] The server 610 is configured to determine instance attribute information associated with the target application based on the instance information recorded by the data center node 630; generate an instance acquisition request based on the instance attribute information, and send the instance acquisition request to the data center node 630; receive at least one instance to be published fed back by the data center node 630 in response to the instance acquisition request, and store the at least one instance to be published into the instance publication set.

[0181] The server 610 is configured to determine batch tags of each instance to be published in the instance publication set according to an instance publication policy, where the instance publication policy is used to represent the publication order of the instances to be published in the instance publication set; determine batch record information corresponding to the instance publication set based on the batch tags of each instance to be published, and publish the instances to be published in the instance publication set based on the batch record information.

[0182] The server 610 is configured to monitor the publication status of the instances included in the instance publication set being published through the application monitoring node 620, to obtain the to-be-published status information, in-publishing status information, or published-completed status information of each instance in the instance publication set; generate the monitoring information based on the to-be-published status information, in-publishing status information, or published-completed status information of each target instance in the instance publication set.

[0183] In summary, during the process of publishing the instances to be published in the instance publication set corresponding to the target application, the instance publication set allows instance changes, that is, adding or deleting instances (scaling up or down). Then, by monitoring the instance publication set through the application monitoring node, instance change information can be generated based on the determined monitoring information, and the instance change information can be synchronized to the data center node, so as to perform elastic processing during the publication of the target application. The compatibility between the publication and elasticity of the target application is completed, the publication process of the target application is optimized, and the publication and elasticity efficiency of the target application is improved.

[0184] The above is a schematic solution of an application monitoring system according to this embodiment. It should be noted that the technical solution of this application monitoring system and the technical solution of the above application monitoring method belong to the same concept. For the details not described in detail in the technical solution of the application monitoring system, reference can be made to the description of the technical solution of the above application monitoring method.

[0185] Corresponding to the above method embodiment, this specification also provides an embodiment of an application monitoring system. Figure 7 shows a structural diagram of another application monitoring system provided by an embodiment of this specification. As Figure 7As shown, the application monitoring system 700 includes a server 710 and application monitoring nodes 720: The server 710 is configured to determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; The application monitoring nodes 720 are configured to perform instance monitoring on the instance release set during the release process, obtain monitoring information, and send the monitoring information to the server 710; The server 710 is configured to update the batch record information based on the monitoring information when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a to-be-released state; and continue to release the instance release set containing the changed instances based on the updated batch record information.

[0186] In actual applications, the application monitoring system 700 includes a server 710 and application monitoring nodes 720; The server 710 determines an instance release set associated with a target application based on a release request submitted by an application publisher, determines a batching strategy corresponding to the application publisher, and determines batch record information corresponding to the instance release set based on the batching strategy. The to-be-released instances in the instance release set are released based on the batch record information. The application monitoring nodes 720 perform instance monitoring on the instance release set during the release process, obtain monitoring information, and send the monitoring information to the server 710. The server 710 updates the batch record information based on the monitoring information when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a to-be-released state; continues to release the instance release set containing the changed instances based on the updated batch record information, and simultaneously generates instance change information corresponding to the target application based on the monitoring information, and synchronizes the instance change information to the data center node to change the number of instances associated with the target application.

[0187] The server 710 is configured to determine instance attribute information associated with the target application based on the instance information recorded by the data center node; generate an instance acquisition request based on the instance attribute information, and send the instance acquisition request to the data center node; receive at least one to-be-released instance fed back by the data center node in response to the instance acquisition request, and store the at least one to-be-released instance in the instance release set.

[0188] The server 710 is configured to determine batch tags for each to-be-released instance in the instance release set according to an instance release strategy, where the instance release strategy is used to represent the release order of the to-be-released instances in the instance release set; determine the batch record information corresponding to the instance release set based on the batch tags of each to-be-released instance, and release the to-be-released instances in the instance release set based on the batch record information.

[0189] The server 710 is configured to monitor the release status of the instances included in the instance release set being released through the application monitoring node 720, and obtain the to-be-released status information, in-release status information, or released-completed status information of each instance in the instance release set; generate the monitoring information based on the to-be-released status information, in-release status information, or released-completed status information of each target instance in the instance release set.

[0190] The server 710 is configured to match the instance batch information included in the monitoring information with the batch record information, and determine the correction information according to the matching result; correct the batch record information based on the correction information.

[0191] The server 710 is configured to, when it is determined based on the correction information that there are deleted instances in the instance release set, determine the to-be-deleted batch information in the batch record information based on the deletion batch information of the deleted instances, and delete the to-be-deleted batch information; when it is determined based on the correction information that there are newly added preferentially released instances in the instance release set, determine the newly added position information in the batch record information based on the priority information of the newly added preferentially released instances, and record the newly added preferentially released instance information of the newly added preferentially released instances to the batch record information based on the newly added position information; when it is determined based on the correction information that there are newly added sequentially released instances in the instance release set, sequentially add the newly added sequentially released instance information of the newly added sequentially released instances to the batch record information based on the sequence information of the newly added sequentially released instances.

[0192] The server 710 is configured to determine the first released instances and the changed instances included in the instance release set based on the updated batch record information, where the first released instances are used to represent the to-be-released instances originally in the instance release set; when the first released instances are released completed, continue to release the changed instances based on the updated batch record information; when the first released instances are not released completed, continue to release the first released instances and the changed instances based on the updated batch record information; when the changed instances included in the instance release set are modified instances, the continuing to release the instance release set including the changed instances based on the updated batch record information includes: determining the second released instances included in the instance release set based on the updated batch record information, and continuing to release the second released instances, where the second released instances are used to represent the modified instances in the to-be-released state in the instance release set.

[0193] The server 710 is used to synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node.

[0194] In summary, during the process of publishing the to-be-published instances in the instance publishing set corresponding to the target application, the instance publishing set allows instance changes, that is, adding or deleting instances (scaling out or scaling in). Then, by monitoring the instance publishing set through the application monitoring node, the batch record information can be updated based on the determined monitoring information, and further guide the instance publishing set with instance changes to continue publishing, realizing elastic processing during the publishing of the target application. Completing the compatibility between the publishing and elasticity of the target application, optimizing the publishing process of the target application, and improving the publishing and elasticity efficiency of the target application.

[0195] The above is a schematic solution of another application monitoring system according to this embodiment. It should be noted that the technical solution of this application monitoring system and the technical solution of the above application monitoring method belong to the same concept. For the details not described in detail in the technical solution of the application monitoring system, reference can be made to the description of the technical solution of the above application monitoring method.

[0196] Corresponding to the above method embodiment, this specification also provides an embodiment of an application monitoring device. Figure 8 The structure diagram of an application monitoring device provided by an embodiment of this specification is shown. As Figure 8 shown, the application monitoring device includes:

[0197] A publishing module 802, configured to determine an instance publishing set associated with a target application and publish the to-be-published instances in the instance publishing set based on the batch record information corresponding to the instance publishing set;

[0198] A monitoring module 804, configured to perform instance monitoring on the instance publishing set during publishing to obtain monitoring information;

[0199] A synchronization module 806, configured to generate instance change information corresponding to the target application based on the monitoring information and synchronize the instance change information to the data center node when it is determined according to the monitoring information that the instance publishing set includes changed instances and the changed instances are in a publishing state.

[0200] In an optional embodiment, the synchronization module 806 is further configured to:

[0201] Extract the tag information of the newly added instances from the monitoring information;

[0202] Generate instance addition information based on the label information of the newly added instance, and use the instance addition information as the instance change information corresponding to the target application;

[0203] An optional embodiment, the synchronization module 806 is further configured to:

[0204] Extract the label information of the modified instance from the monitoring information;

[0205] Generate instance modification information based on the label information of the modified instance, and use the instance modification information as the instance change information corresponding to the target application.

[0206] An optional embodiment, the publishing module 802 is further configured to:

[0207] Determine the instance attribute information associated with the target application based on the instance information recorded by the data center node;

[0208] Generate an instance acquisition request based on the instance attribute information and send it to the data center node;

[0209] Receive at least one instance to be published fed back by the data center node in response to the instance acquisition request, and store the at least one instance to be published in the instance publishing set.

[0210] An optional embodiment, the publishing module 802 is further configured to:

[0211] Determine the batch labels of the instances to be published in the instance publishing set according to the instance publishing policy, where the instance publishing policy is used to represent the publishing order of the instances to be published in the instance publishing set;

[0212] Determine the batch record information corresponding to the instance publishing set based on the batch labels of the instances to be published, and publish the instances to be published in the instance publishing set based on the batch record information.

[0213] An optional embodiment, the monitoring module 804 is further configured to:

[0214] Monitor the publishing status of the instances included in the instance publishing set being published through the application monitoring node, and obtain the to-be-published status information or in-publishing status information or published-completed status information of each instance in the instance publishing set; generate the monitoring information based on the to-be-published status information or in-publishing status information or published-completed status information of each target instance in the instance publishing set.

[0215] In summary, during the process of releasing the to-be-released instances in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, adding or deleting instances (scaling up or down). Then, by monitoring the instance release set through the application monitoring node, instance change information can be generated based on the determined monitoring information, and the instance change information can be synchronized to the data center node, so as to perform elastic processing during the release of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0216] The above is a schematic solution of an application monitoring device according to this embodiment. It should be noted that the technical solution of this application monitoring device and the technical solution of the above application monitoring method belong to the same concept. For the details not described in the technical solution of the application monitoring device, reference can be made to the description of the technical solution of the above application monitoring method.

[0217] Corresponding to the above method embodiment, this specification also provides another embodiment of the application monitoring device. Figure 9 The structure diagram of another application monitoring device provided by an embodiment of this specification is shown. As Figure 9 shown, the application monitoring device includes:

[0218] A release module 902, configured to determine an instance release set associated with the target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set;

[0219] A monitoring module 904, configured to perform instance monitoring on the instance release set during release to obtain monitoring information;

[0220] An update module 906, configured to update the batch record information based on the monitoring information when it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in the to-be-released state;

[0221] A continue release module 908, configured to continue to release the instance release set including the changed instances based on the updated batch record information.

[0222] In an optional embodiment, the release module 902 is further configured to:

[0223] Determine the instance attribute information associated with the target application based on the instance information recorded by the data center node;

[0224] Generate an instance acquisition request based on the instance attribute information and send it to the data center node;

[0225] Receive at least one instance to be published fed back by the data center node in response to the instance acquisition request, and store the at least one instance to be published in the instance publishing set.

[0226] In an optional embodiment, the publishing module 902 is further configured to:

[0227] Determine the batch tags of the instances to be published in the instance publishing set according to the instance publishing policy, where the instance publishing policy is used to represent the publishing order of the instances to be published in the instance publishing set;

[0228] Determine the batch record information corresponding to the instance publishing set based on the batch tags of the instances to be published, and publish the instances to be published in the instance publishing set based on the batch record information.

[0229] In an optional embodiment, the monitoring module 904 is further configured to:

[0230] Monitor the publishing status of the instances included in the instance publishing set being published through the application monitoring node, and obtain the to-be-published status information or in-publishing status information or published-completed status information of each instance in the instance publishing set; generate the monitoring information based on the to-be-published status information or in-publishing status information or published-completed status information of each target instance in the instance publishing set.

[0231] In an optional embodiment, the updating module 906 is further configured to:

[0232] Match the instance batch information included in the monitoring information with the batch record information, and determine the correction information according to the matching result;

[0233] Correct the batch record information based on the correction information.

[0234] In an optional embodiment, the updating module 906 is further configured to:

[0235] In the case where it is determined based on the correction information that there are deleted instances in the instance publishing set, determine the batch information to be deleted in the batch record information based on the deletion batch information of the deleted instances, and delete the batch information to be deleted;

[0236] In the case where it is determined based on the correction information that there are newly added instances with priority for publishing in the instance publishing set, determine the new position information in the batch record information based on the priority information of the newly added instances with priority for publishing, and record the information of the newly added instances with priority for publishing to the batch record information based on the new position information;

[0237] When it is determined based on the corrected information that there are newly added sequential release instances in the instance release set, add the newly added sequential release instance information of the newly added sequential release instances to the batch record information sequentially based on the sequential information of the newly added sequential release instances.

[0238] An optional embodiment, the continue release module 908 is further configured to:

[0239] Determine a first release instance and the change instance included in the instance release set based on the updated batch record information, where the first release instance is used to represent the original to-be-released instance in the instance release set; when the first release instance is released, continue to release the change instance based on the updated batch record information; when the first release instance is not released, continue to release the first release instance and the change instance based on the updated batch record information;

[0240] When the change instance included in the instance release set is a modified instance, the continuing to release the instance release set including the change instance based on the updated batch record information includes:

[0241] Determine a second release instance included in the instance release set based on the updated batch record information, and continue to release the second release instance, where the second release instance is used to represent the modified instance in the instance release set in a to-be-released state.

[0242] An optional embodiment, the continue release module 908 is further configured to:

[0243] Synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node.

[0244] In summary, during the process of releasing the to-be-released instances in the instance release set corresponding to the target application, the instance release set allows instance changes, that is, adding or deleting instances (scaling up or down). By monitoring the instance release set through the application monitoring node, the batch record information can be updated based on the determined monitoring information, and then guide the instance release set with instance changes to continue to be released, realizing elastic processing during the release of the target application. Complete the compatibility between the release and elasticity of the target application, optimize the release process of the target application, and improve the release and elasticity efficiency of the target application.

[0245] The above is a schematic solution of another application monitoring device according to this embodiment. It should be noted that the technical solution of this application monitoring device and the technical solution of the above application monitoring method belong to the same concept. For the details not described in the technical solution of the application monitoring device, reference can be made to the description of the technical solution of the above application monitoring method.

[0246] Figure 10 FIG. 4 shows a structural block diagram of a computing device 1000 according to an embodiment of the present specification. The components of the computing device 1000 include, but are not limited to, a memory 1010 and a processor 1020. The processor 1020 is connected to the memory 1010 through a bus 1030, and a database 1050 is used to store data.

[0247] The computing device 1000 further includes an access device 1040, which enables the computing device 1000 to communicate via one or more networks 1060. Examples of these networks include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 1040 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (WiMAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0248] In an embodiment of the present specification, the above components of the computing device 1000 and Figure 10 other components not shown in FIG. 4 may also be connected to each other, for example, through a bus. It should be understood that Figure 10 the structural block diagram of the computing device shown in FIG. 4 is for illustrative purposes only and is not a limitation on the scope of the present specification. Those skilled in the art can add or replace other components as needed.

[0249] The computing device 1000 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.) or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 1000 can also be a mobile or stationary server.

[0250] Wherein, the processor 1020 is used to execute the following computer-executable instructions, and when the computer-executable instructions are executed by the processor, the steps of the above application monitoring method are implemented.

[0251] The above is a schematic solution of a computing device according to this embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above application monitoring method belong to the same concept. For the details not described in detail in the technical solution of the computing device, reference can be made to the description of the technical solution of the above application monitoring method.

[0252] An embodiment of this specification also provides a computer-readable storage medium, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the above application monitoring method are implemented.

[0253] The above is a schematic solution of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the above application monitoring method belong to the same concept. For the details not described in detail in the technical solution of the storage medium, reference can be made to the description of the technical solution of the above application monitoring method.

[0254] An embodiment of this specification also provides a computer program product, including a computer program / instructions, and when the computer program / instructions are executed by a processor, the steps of the above application monitoring method are implemented.

[0255] The above is a schematic solution of a computer program according to this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above application monitoring method belong to the same concept. For the details not described in detail in the technical solution of the computer program, reference can be made to the description of the technical solution of the above application monitoring method.

[0256] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0257] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, removable hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0258] It should be noted that for the foregoing method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of this specification are not limited by the described order of actions, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments of this specification.

[0259] In the above embodiments, the descriptions of each embodiment have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0260] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The alternative embodiments do not elaborate on all the details and do not limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can well understand and utilize this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. An application monitoring method, comprising: Determining an instance release set associated with a target application, and releasing the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; Performing instance monitoring on the instance release set during the release to obtain monitoring information; When it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in a released state, generating instance change information corresponding to the target application based on the monitoring information, and synchronizing the instance change information to a data center node.

2. The application monitoring method according to claim 1, when it is determined based on the monitoring information that the changed instance is a newly added instance, the generating the instance change information corresponding to the target application based on the monitoring information includes: Extracting the tag information of the newly added instance from the monitoring information, and using the tag information of the newly added instance as the changed tag information; Generating instance addition information based on the changed tag information, and using the instance addition information as the instance change information corresponding to the target application.

3. The application monitoring method according to claim 1, when it is determined based on the monitoring information that the changed instance is a modified instance, the generating the instance change information corresponding to the target application based on the monitoring information includes: Extracting the tag information of the modified instance from the monitoring information; Generating instance modification information based on the tag information of the modified instance, and using the instance modification information as the instance change information corresponding to the target application.

4. The application monitoring method according to claim 1, the determining the instance release set associated with the target application includes: Determining the instance attribute information associated with the target application based on the instance information recorded by the data center node; Generating an instance acquisition request based on the instance attribute information, and sending the instance acquisition request to the data center node; Receiving at least one to-be-released instance fed back by the data center node in response to the instance acquisition request, and storing the at least one to-be-released instance in the instance release set.

5. The application monitoring method according to claim 1, the releasing the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set includes: Determining the batch tags of the to-be-released instances in the instance release set according to an instance release policy, where the instance release policy is used to represent the release order of the to-be-released instances in the instance release set; Determining the batch record information corresponding to the instance release set based on the batch tags of the to-be-released instances, and releasing the to-be-released instances in the instance release set based on the batch record information.

6. The application monitoring method according to claim 1, the performing instance monitoring on the instance release set during the release to obtain monitoring information includes: By applying a monitoring node to monitor the release status of the instances included in the instance release set during release, the to-be-released status information, in-release status information, or released-completed status information of each instance in the instance release set is obtained; Based on the to-be-released status information, in-release status information, or released-completed status information of each target instance in the instance release set, the monitoring information is generated.

7. An application monitoring method, comprising: Determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; Perform instance monitoring on the instance release set during release to obtain monitoring information; When it is determined according to the monitoring information that the instance release set contains changed instances and the changed instances are in the to-be-released status, update the batch record information based on the monitoring information; Continue to release the instance release set containing the changed instances based on the updated batch record information.

8. According to the application monitoring method described in claim 7, the updating the batch record information based on the monitoring information includes: Match the instance batch information included in the monitoring information with the batch record information, and determine correction information according to the matching result; Correct the batch record information based on the correction information.

9. According to the application monitoring method described in claim 8, the correcting the batch record information based on the correction information includes: When it is determined based on the correction information that there are deleted instances in the instance release set, determine the to-be-deleted batch information in the batch record information based on the deletion batch information of the deleted instances, and delete the to-be-deleted batch information; When it is determined based on the correction information that there are newly added preferentially released instances in the instance release set, determine the newly added position information in the batch record information based on the priority information of the newly added preferentially released instances, and record the newly added preferentially released instance information of the newly added preferentially released instances to the batch record information based on the newly added position information; When it is determined based on the correction information that there are newly added sequentially released instances in the instance release set, sequentially add the newly added sequentially released instance information of the newly added sequentially released instances to the batch record information based on the sequence information of the newly added sequentially released instances.

10. According to the application monitoring method described in claim 7, when the changed instances included in the instance release set are newly added instances, the continuing to release the instance release set containing the changed instances based on the updated batch record information includes: Determine a first release instance and the change instance included in the instance release set based on the updated batch record information, where the first release instance is used to represent the original to-be-released instance in the instance release set; when the release of the first release instance is completed, continue to release the change instance based on the updated batch record information; when the release of the first release instance is not completed, continue to release the first release instance and the change instance based on the updated batch record information; When the change instance included in the instance release set is a modification instance, the continuing to release the instance release set including the change instance based on the updated batch record information includes: Determine a second release instance included in the instance release set based on the updated batch record information, and continue to release the second release instance, where the second release instance is used to represent the modification instance in the instance release set that is in a to-be-released state.

11. The application monitoring method according to any one of claims 7-10, further comprising: Synchronize the updated batch record information to the data center node for updating the instance record information recorded by the data center node.

12. An application monitoring system, comprising a server, an application monitoring node, and a data center node: The server is configured to determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; The application monitoring node is configured to perform instance monitoring on the instance release set being released, obtain monitoring information, and send the monitoring information to the server; The server is configured to, when it is determined according to the monitoring information that the instance release set includes a change instance and the change instance is in a released state, generate instance change information corresponding to the target application based on the monitoring information and synchronize it to the data center node.

13. An application monitoring system, comprising a server and an application monitoring node: The server is configured to determine an instance release set associated with a target application, and release the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set; The application monitoring node is configured to perform instance monitoring on the instance release set being released, obtain monitoring information, and send the monitoring information to the server; The server is configured to, when it is determined according to the monitoring information that the instance release set includes a change instance and the change instance is in a to-be-released state, update the batch record information based on the monitoring information; continue to release the instance release set including the change instance based on the updated batch record information.

14. A computing device, comprising: A memory and a processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, and when the computer-executable instructions are executed by the processor, the steps of the application monitoring method according to any one of claims 1 to 11 are implemented.

15. A computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the application monitoring method according to any one of claims 1 to 11 are implemented.

16. A computer program product includes a computer program / instructions, and when the computer program / instructions are executed by a processor, the steps of the application monitoring method according to any one of claims 1 to 11 are implemented.

Images