Application monitoring methods and system

Abstract

Provided in the embodiments of the present disclosure are application monitoring methods and system. An application monitoring method comprises: determining an instance release set associated with a target application, and on the basis of batch record information corresponding to the instance release set, releasing instances to be released in the instance release set; performing instance monitoring on the instance release set under releasing, so as to obtain monitoring information; when it is determined, on the basis of the monitoring information, that the instance release set contains a changed instance and the changed instance is in a release state, generating instance change information corresponding to the target application on the basis of the monitoring information, and synchronizing the instance change information to a data center node. The present disclosure allows for the occurrence of instance changes in instance release sets during processes of releasing instances to be released in instance release sets corresponding to target applications, and monitors the instance release sets by means of application monitoring nodes, so as to generate instance change information on the basis of the determined monitoring information, thus optimizing release processes of target applications, and improving the release and elasticity efficiency of target applications.

Description

[0001] Application Monitoring Method and System This disclosure claims priority to Chinese patent application number 202410084614.6, filed with the China Patent Office on January 19, 2024, entitled "Application Monitoring Method and System," the entire contents of which are incorporated herein by reference. Technical Field: Embodiments of the present disclosure relate to the field of computer technology, and more particularly to an application monitoring method and system. Background: With the advancement of computer technology, applications are becoming increasingly diverse. Traditionally, application release and elasticity (scaling) are handled separately. This is primarily because application release involves batch processing, and each batch selects specific instances, with a specific ratio or number of instances. If elasticity processing is performed during application release, whether scaling up or down, there will be a mismatch with the allocated elasticity data, resulting in release anomalies. In existing technologies, application release and elasticity processing are mutually exclusive. Application elasticity processing cannot be performed during the application release period. Accordingly, release must be stopped during application elasticity processing. Therefore, a more effective application monitoring method is urgently needed to address the aforementioned issues. In view of this, embodiments of the present disclosure provide an application monitoring method. One or more embodiments of the present disclosure simultaneously relate to an application monitoring system, a computing device, a computer-readable storage medium, and a computer program product to address technical deficiencies in the prior art. According to a first aspect of an embodiment of the present disclosure, an application monitoring method is provided, comprising: determining an instance release set associated with a target application, and publishing pending instances in the instance release set based on batch record information corresponding to the instance release set; performing instance monitoring on the instance release set being published to obtain monitoring information; and, upon determining, based on the monitoring information, that the instance release set includes a changed instance and that the changed instance is in a published 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. According to a second aspect of an embodiment of the present disclosure, another application monitoring method is provided, comprising: determining an instance release set associated with a target application, and publishing to-be-released instances in the instance release set based on batch record information corresponding to the instance release set; performing instance monitoring on the instance release set being released to obtain monitoring information; if it is determined based on the monitoring information that the instance release set includes a changed instance and the changed instance is in a to-be-released state, updating the batch record information based on the monitoring information; and continuing to publish the instance release set including the changed instance based on the updated batch record information.According to a third aspect of an embodiment of the present disclosure, an application monitoring system is provided, 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 publish instances to be published in the instance release set based on 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 published, obtain monitoring information, and send the monitoring information to the server; the server is configured to, upon determining, based on the monitoring information, that the instance release set contains a changed instance and that the changed instance is 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 the data center node. According to a fourth aspect of an embodiment of the present disclosure, another application monitoring system is provided, comprising: a server and an application monitoring node: the server is configured to determine an instance release set associated with a target application, and publish to-be-released instances in the instance release set based on 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, upon determining, based on 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; and continue to publish the instance release set containing the changed instance based on the updated batch record information. According to a fifth aspect of an embodiment of the present disclosure, an application monitoring device is provided, comprising: a publishing module, configured to determine an instance publishing set associated with a target application, and publish to-be-published instances in the instance publishing set based on batch record information corresponding to the instance publishing set; a monitoring module, configured to perform instance monitoring on the instance publishing set being published to obtain monitoring information; and a synchronization module, configured to, when it is determined according to the monitoring information that the instance publishing set contains a changed instance and the changed instance is 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.According to a sixth aspect of an embodiment of the present disclosure, another application monitoring apparatus is provided, comprising: a publishing module configured to determine an instance release set associated with a target application and, based on batch record information corresponding to the instance release set, publish pending instances in the instance release set; a monitoring module configured to monitor instances of the instance release set being published to obtain monitoring information; an updating module configured to, upon determining, based on the monitoring information, that the instance release set includes a change instance and the change instance is in a pending release state, update the batch record information based on the monitoring information; and a continuing publishing module configured to continue publishing the instance release set including the change instance based on the updated batch record information. According to a seventh aspect of an embodiment of the present disclosure, a computing device is provided, comprising: a memory and a processor; the memory being configured to store computer-executable instructions; the processor being configured to execute the computer-executable instructions, wherein the computer-executable instructions, when executed by the processor, implement the steps of the aforementioned application monitoring method. According to an eighth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, storing computer-executable instructions, wherein the instructions, when executed by the processor, implement the steps of the aforementioned application monitoring method. According to a ninth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the aforementioned application monitoring method. One embodiment of the present disclosure determines an instance release set associated with a target application and, based on batch record information corresponding to the instance release set, releases pending instances in the instance release set; performs instance monitoring on the instance release set in progress to obtain monitoring information; and, upon determining, based on the monitoring information, that the instance release set contains a changed instance and that the changed instance is in a released state, generates instance change information corresponding to the target application based on the monitoring information and synchronizes the instance change information to a data center node. This allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction), to occur during the release of pending instances in the instance release set corresponding to the target application. Furthermore, the application monitoring node monitors the instance release set, generates instance change information based on the determined monitoring information, and synchronizes the instance change information to the data center node, thereby implementing elastic processing during the target application release process. This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency.BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a schematic diagram of the processing process of an application monitoring method provided by one embodiment of the present disclosure; Figure 2 is a flow chart of an application monitoring method provided by one embodiment of the present disclosure; Figure 3 is a flow chart of another application monitoring method provided by one embodiment of the present disclosure; Figure 4 is a flow chart of the processing process of an application monitoring method provided by one embodiment of the present disclosure; Figure 5 is a schematic diagram of application publishing according to an application monitoring method provided by one embodiment of the present disclosure; Figure 6 is a structural diagram of an application monitoring system provided by one embodiment of the present disclosure; Figure 7 is a structural diagram of another application monitoring system provided by one embodiment of the present disclosure; Figure 8 is a schematic diagram of the structure of an application monitoring device provided by one embodiment of the present disclosure; Figure 9 is a schematic diagram of the structure of another application monitoring device provided by one embodiment of the present disclosure; and Figure 10 is a block diagram of the structure of a computing device provided by one embodiment of the present disclosure. DETAILED DESCRIPTION The following description sets forth numerous specific details to facilitate a thorough understanding of the present disclosure. However, the present disclosure can be implemented in many other ways than those described herein, and those skilled in the art may make similar generalizations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the specific implementations disclosed below. The terminology used in one or more embodiments of the present disclosure is for the purpose of describing specific embodiments only and is not intended to limit the present disclosure. As used in one or more embodiments of the present disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of the present disclosure refers to and encompasses any and all possible combinations of one or more of the associated listed items. It should be understood that although the terms first, second, etc. may be employed in one or more embodiments of the present disclosure to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, the first could be referred to as the second, and similarly, the second could be referred to as the first, without departing from the scope of one or more embodiments of the present disclosure. Depending on the context, the word "if," as used herein, could be interpreted as "when..." or "when..." or "in response to determining."Furthermore, 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 used for analysis, storage, and display) involved in one or more embodiments of this disclosure are all authorized by the user or fully authorized by all parties. The collection, use, and processing of such data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding entry points are provided for users to choose to authorize or deny such data. First, let's explain the terminology used in one or more embodiments of this disclosure. Automated elasticity: Dynamic elasticity capabilities are achieved without human intervention through indicators or timing.

[0002] Kubernetes, abbreviated as K8s, is an abbreviation formed by replacing the eight characters in the middle of its name, "ubernete." It is an open-source container orchestration engine designed to manage containerized applications across multiple hosts in a cloud platform. Kubernetes aims to simplify container deployment and operation and provide an efficient method for managing the lifecycle of containerized applications. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance, enabling automated deployment, scaling, and management of containerized applications. It supports automatic deployment, scaling, and management of containers, and also offers features such as service discovery, load balancing, naming and discovery, and resource monitoring. Figure 1 illustrates the processing of an application monitoring method provided in one embodiment of the present disclosure. As shown in Figure 1, in the scenario of releasing a target application, an instance release set associated with the target application is determined, and the pending instances in the instance release set are released based on the batch record information corresponding to the instance release set. During the release of the pending instances in the instance release set, the application monitoring node monitors the instances in the release set to obtain monitoring information. If monitoring information determines that the instance release set contains a changed instance and the changed instance is in the release state, if the instance is currently in the non-release state, instance change information for the target application is generated based on the monitoring information and synchronized to the data center node. If the instance is currently in the release state, instance change information for the target application is generated based on the monitoring information and synchronized to the data center node. At the same time, the change engine updates the batch record information based on the monitoring information. The target application is then released. During the release process of the pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance release set and generates instance change information based on the determined monitoring information. This information is synchronized to the data center node, enabling elastic processing during the target application release process. This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency. The present disclosure provides an application monitoring method, an application monitoring system, a computing device, a computer-readable storage medium, and a computer program product, each of which is described in detail in the following embodiments. Referring to FIG. 2 , a flowchart of an application monitoring method according to one embodiment of the present disclosure is shown, specifically including the following steps.Step 202: Determine the instance release set associated with the target application and, based on the batch record information corresponding to the instance release set, publish the pending instances in the instance release set. Specifically, the target application can be any developed application to be released. The domain of the target application includes, but is not limited to, client applications and underlying application services. The instance release set is the function set corresponding to the target application, and the pending instances in the instance release set correspond to the functions or function sets of the target application. Batch record information refers to the information record consisting of the release batch information of each pending instance in the instance release set; each pending instance corresponds to a release batch. Based on this, the target application to be released and the instance release set associated with the target application to be released are determined. The batch record information corresponding to the instance release set is determined, and the pending instances in the instance release set are released sequentially according to the batch record information. Alternatively, the pending instances in the instance release set can be released simultaneously according to the batch record information. In practical applications, the pending instances in the instance release set correspond to the functions or function sets of the target application. Publishing the pending instances can be considered as publishing the target application. Publishing pending instances in an instance publishing set based on batch record information can achieve the goal of batch publishing. Furthermore, considering that the data center node provides data synchronization services during the target application publishing process and records the pending nodes associated with the target application, at least one pending instance can be obtained from the data center node when the target application is published. This is specifically implemented as follows: determining 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 it to the data center node; receiving at least one pending instance fed back by the data center node in response to the instance acquisition request, and storing the at least one pending instance in the instance publishing set. Specifically, instance information refers to instance information associated with the target application and other pending applications stored in the data center node; instance attribute information can be instance IDs, instance names, or other instance identifiers used to identify instances; and an instance acquisition request is a computer instruction for obtaining a pending instance. Therefore, instance attribute information associated with the target application is determined based on the instance information recorded by the data center node. An instance acquisition request is generated based on the instance attribute information and sent to the data center node for acquiring the to-be-published instance corresponding to the instance attribute information at the data center node.The data center node receives at least one to-be-released instance as feedback from the data center node in response to the instance acquisition request, and stores the at least one to-be-released instance in an instance release set, or constructs an instance release set based on the at least one to-be-released instance. For example, the data center node records instance information of instances associated with each to-be-released application. For a target application, instance attribute information associated with the target application can be determined, namely, instance names: Instance A, Instance B, Instance C, Instance D. Based on the instance attribute information, the data center node generates an instance acquisition request and sends it to the data center node. Based on the instance attribute information: Instance A, Instance B, Instance C, Instance D, the data center node determines the to-be-released instances corresponding to each instance attribute information: To-be-released Instance A, To-be-released Instance B, To-be-released Instance C, To-be-released Instance D, respectively, and uses these four instances as feedback for the instance acquisition request. In summary, obtaining at least one to-be-released instance of the target application at the data center node improves the accuracy of determining the to-be-released instances. Furthermore, considering that an instance release set may contain multiple pending instances, each of which may correspond to a different release batch, the pending instances in the instance release set are released based on batch record information, thereby achieving orderly release of the pending instances in the instance release set. Specifically, the batch tag for each pending instance in the instance release set is determined based on an instance release policy, where the instance release policy indicates the release order of the pending instances in the instance release set. The batch record information corresponding to the instance release set is determined based on the batch tag of each pending instance, and the pending instances in the instance release set are released based on the batch record information. Specifically, the instance release policy determines the release order of the pending instances in the instance release set. The instance release policy can be determined based on the instance release priority of each pending instance. If the pending instance has a higher priority, the batch tag is assigned to the first batch, or a preceding batch. The batch tag indicates batch information such as the first batch, the second batch, and so on. Based on this, a batch tag is assigned to each pending instance in the instance release set based on the instance release policy. Based on the batch tag of each pending instance, the batch record information corresponding to the instance release set is determined. This record describes the release batches of each pending instance in the instance release set. Based on the batch record information, the pending instances in the instance release set are released sequentially or simultaneously. Using the above example, the pending instances are instance A, instance B, instance C, and instance Do. The batch tag for each instance is determined based on the instance release policy.The first batch is used as the batch label for pending instance A, the second batch as the batch label for pending instance B, the third batch as the batch label for pending instance C, and the fourth batch as the batch label for pending instance D. By combining the instance labels of each instance, batch record information is obtained: First batch: pending instance A; Second batch: pending instance B; Third batch: pending instance C; Fourth batch: pending instance D. Instances A, B, C, and D are then published based on the batch record information. In summary, the pending instances in the instance release set are published sequentially based on the batch record information, thereby improving the orderliness of the release of each pending instance in the instance release set. Step 204: Instance monitoring is performed on the instance release set being published to obtain monitoring information. Specifically, after determining the instance release set associated with the target application and publishing the pending instances in the instance release set based on the batch record information corresponding to the instance release set, instance monitoring can be performed on the instance release set in progress to obtain monitoring information. This monitoring information includes instance information obtained by monitoring the release status of existing pending instances in the instance release set and instance information obtained by monitoring newly added pending instances in the instance release set. Therefore, after determining the instance release set associated with the target application and publishing the pending instances in the instance release set based on the batch record information corresponding to the instance release set, instance monitoring can be performed on the instance release set in progress via the application monitoring node. This monitoring information monitors existing pending instances in the instance release set and whether newly added instances exist in the instance release set. Instance change information obtained from monitoring instances in the instance release set is used as monitoring information for the instance release set. In actual applications, during the release of pending instances in an instance release set, you can scale down the pending instances within the set, stopping the release of a specific pending instance. You can also scale up the set by adding and releasing a new pending instance to the existing pending instances. Application monitoring nodes monitor changes in instances within the set and generate monitoring information based on these changes.Furthermore, considering that during the publishing process of pending instances in an instance publishing set, the instance publishing status of the pending instances in the instance publishing set varies at different times, and thus the monitoring information obtained also varies, a specific implementation is as follows: An application monitoring node monitors the publishing status of instances included in the instance publishing set being published, obtaining pending status information, publishing status information, or publishing completed status information for each instance in the instance publishing set; and generates the monitoring information based on the pending status information, publishing status information, or publishing completed status information for each target instance in the instance publishing set. Specifically, the application monitoring node is used to monitor instance change information in the instance publishing set. The application monitoring node can be program software or an installed system service with the ability to sense or monitor instance changes in the instance publishing set. The application monitoring node is used to monitor modified instances and newly added instances in the instance publishing set. Based on this, the application monitoring node monitors the publishing status of each instance included in the instance publishing set being published. Instances in the instance publishing set can be in the pending status, publishing status, or publishing completed status. Each instance in the instance publishing set corresponds to a publishing status. By monitoring the publishing status of each instance included in the publishing instance set, the pending publishing status, publishing status, or publishing completion status of each instance in the instance set can be obtained. Monitoring information for the instance set can be generated based on the pending publishing status, publishing status, or publishing completion status of each target instance in the instance set. In summary, during the publishing process of pending instances in the instance set, the publishing status of the pending instances is monitored to ensure the orderly publishing of the pending instances in the instance set. Furthermore, by monitoring the publishing status, the publishing status of the pending instances can be monitored in real time. Step 206: If it is determined, based on the monitoring information, that the instance set contains a changed instance and that the changed instance is in the published state, instance change information corresponding to the target application is generated based on the monitoring information and synchronized to the data center node.Specifically, after the application monitoring node monitors the instance release set in progress and obtains monitoring information, if it is determined based on the monitoring information that the instance release set contains a changed instance and the changed instance is in the published state, instance change information corresponding to the target application is generated based on the monitoring information and synchronized to the data center node. A changed instance is an instance whose release state changes during the instance release process, such as a paused release or a newly added release. A changed instance can be an instance whose release state changes for an existing pending instance in the instance release set, or a newly added pending instance in addition to an existing pending instance in the instance release set. The release state indicates the release stage of the pending instance in the instance release set, which can be one of: pending, publishing, or published. Instance change information is descriptive information about instances in the instance release set when a change occurs. The data center node is used to record the number of instances corresponding to the target application. The data center node provides data synchronization services during the target application release process, recording the published instances corresponding to the target application. Based on this, after obtaining monitoring information by performing instance monitoring on the instance release set in progress through the application monitoring node, if the monitoring information determines that the instance release set contains a changed instance and the changed instance is in the published state, this indicates that a pending instance in the instance release set has changed, or a new pending instance has been added to the instance release set. Instance change information corresponding to the target application is generated based on the monitoring information and synchronized to the data center node. The instance change information describes the number of instances in the current instance release set and the global instance status. In actual applications, the changed instances included in the instance release set can be pending instances in the instance release set or newly added pending instances in the instance release set. If the changed instances are pending instances in the instance release set, the change in the pending instance may be due to the suspension of the pending instance due to the scaling down of the target application. If the newly added pending instance in the instance release set is due to the scaling up of the target application, it may be due to the addition of the pending instance to the instance release set. In another embodiment, instance change monitoring can be combined with the change engine to perform instance monitoring on the pending instance release set in progress to obtain monitoring information. Then, an instance number synchronizer is developed within K8S or outside non-K8S scenarios. The updated batch record information is directly synchronized to the data center node using the instance number synchronizer, thereby achieving compatibility between the release of the target application and elasticity, and optimizing the release process of the target application.Furthermore, considering that during the monitoring of an instance release set, a changed instance may be a newly added instance, corresponding instance change information can be generated for the newly added instance. Specifically, if the changed instance is determined to be a newly added instance based on the monitoring information, the tag information of the newly added instance is extracted from the monitoring information; newly added instance information is generated based on the tag information of the newly added instance, and the newly added instance information is used as the instance change information corresponding to the target application. Specifically, a newly added instance is an instance added to the instance release set in addition to an existing instance to be released in the instance release set; accordingly, the newly added instance information is attribute information such as the instance name and instance ID of the newly added instance. Therefore, if the changed instance is determined to be a newly added instance based on the monitoring information, this indicates that a newly added instance has been added to the instance release set during the instance release process. The tag information of the newly added instance is extracted from the monitoring information; the newly added instance information is generated based on the tag information of the newly added instance, and the newly added instance information is used as the instance change information corresponding to the target application. In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition of new instances (capacity expansion). By monitoring the instance release set through the application monitoring node, instance change information can be generated based on the determined monitoring information and synchronized to the data center node, enabling flexible processing during the target application release process. Furthermore, considering that during the monitoring of the instance release set, the changed instance can be a modified instance, corresponding instance change information can be generated for the modified instance. This is specifically implemented as follows: if the changed instance is determined to be a modified instance based on the monitoring information, the tag information of the modified instance is extracted from the monitoring information; instance modification information is generated based on the tag information of the modified instance, and the instance modification information is used as the instance change information corresponding to the target application. Specifically, a modified instance is a set of instances obtained by modifying existing instances to be released in the instance release set. The modification can be a pause operation on the instance to be released. Accordingly, instance modification information includes attribute information such as the instance name and instance ID of the modified instance, as well as modification methods, including but not limited to pausing release and deleting from the instance set. Therefore, if the modified instance is determined to be a modified instance based on monitoring information, it indicates that an instance in the instance release set needs to be modified during the instance release process. The tag information of the modified instance is extracted from the monitoring information.Instance modification information is generated based on the tag information of the modified instance, and this instance modification information is used as the instance change information for the target application. Continuing with the above example, the instances to be released in the instance release set are instance A, instance B, instance C, and instance D. During the release of these pending instances, instance E can be added in a capacity expansion scenario, generating instance modification information "Added instance E." This modification information is instance change information. Alternatively, instance D can be modified in a capacity reduction scenario, generating instance modification information "Pause release of instance D." This modification information is instance change information. In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, instance deletion (scaling). The application monitoring node then monitors the instance release set and generates instance change information based on the determined monitoring information. This instance change information is then synchronized to the data center node, enabling flexible processing during the target application release process. This ensures compatibility between the target application's release and elasticity, optimizes the target application's release process, and improves both the target application's release and elasticity efficiency. It's important to note that in actual applications, the release of a target application involves the release of multiple instances within an instance release set, each corresponding to a release batch. Therefore, during the release of pending instances within the instance release set, instances may be added (scaled up) or deleted (scaled down). For example, during the release of instances within an instance release set (first batch: pending instance A; second batch: pending instance B; third batch: pending instance C; fourth batch: pending instance D and pending instance E), instances can be scaled up by adding the fifth batch: pending instance F, and by adding pending instance G to any of the instances in the corresponding batch. Alternatively, instances can be scaled down by deleting pending instance D from the fourth batch. Therefore, the above-mentioned operations of "adding the fifth batch: to-be-released instances F," "adding to-be-released instances G to the corresponding instances of any batch," and "deleting to-be-released instances D corresponding to the fourth batch" can be performed simultaneously. For specific implementation methods, please refer to the above-mentioned embodiments and will not be repeated here. Referring to FIG3 , FIG3 shows a flowchart of another application monitoring method provided according to an embodiment of the present disclosure, which specifically includes the following steps. Step 302: Determine the instance release set associated with the 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. Based on this, the target application to be released is determined, as well as the instance release set associated with the target application to be released.Batch record information corresponding to an instance release set is determined, and to-be-released instances in the instance release set are sequentially released according to the batch record information; alternatively, each to-be-released instance in the instance release set is released synchronously according to the batch record information. In practical applications, the to-be-released instances included in the instance release set correspond to functions or function sets of the target application. Publishing the to-be-released instances in the instance release set based on the batch record information can achieve the purpose of batch release. Furthermore, considering that the data center node provides data synchronization services during the target application release process and records the to-be-released nodes associated with the target application, at least one to-be-released instance can be obtained from the data center node when the target application is released. This is specifically implemented as follows: instance attribute information associated with the target application is determined based on the instance information recorded by the data center node; an instance acquisition request is generated based on the instance attribute information and sent to the data center node; at least one to-be-released instance is received from the data center node in response to the instance acquisition request, and the at least one to-be-released instance is stored in the instance release set. Based on this, instance attribute information associated with the target application is determined based on the instance information recorded by the data center node. An instance acquisition request is generated based on the instance attribute information and sent to a data center node, for acquiring, at the data center node, a to-be-released instance corresponding to the instance attribute information. At least one to-be-released instance, as fed back by the data center node in response to the instance acquisition request, is received and stored in an instance release set, or an instance release set is constructed based on the at least one to-be-released instance. In summary, acquiring at least one to-be-released instance of the target application at the data center node improves the accuracy of determining the to-be-released instance. Furthermore, considering that an instance release set may contain multiple to-be-released instances, each of which may correspond to a different release batch, the to-be-released instances in the instance release set are released based on batch record information, thereby achieving orderly release of the to-be-released instances in the instance release set. This is specifically implemented as follows: a batch tag is determined for each to-be-released instance in the instance release set according to an instance release policy, wherein the instance release policy indicates the release order of the to-be-released instances in the instance release set; the batch record information corresponding to the instance release set is determined based on the batch tag of each to-be-released instance, and the to-be-released instances in the instance release set are released based on the batch record information. Based on this, a batch label is assigned to each to-be-released instance in the instance release set according to the instance release strategy.Based on the batch tags of each to-be-released instance, batch record information corresponding to the instance release set is determined to describe the release batches of each to-be-released instance in the instance release set. Based on the batch record information, the to-be-released instances in the instance release set are released sequentially, or simultaneously. In summary, the to-be-released instances in the instance release set are released sequentially based on the batch record information, thereby improving the orderliness of the release of each to-be-released instance in the instance release set. Step 304: Instance monitoring is performed on the instance release set being released to obtain monitoring information. Based on this, after determining the instance release set associated with the target application and publishing the to-be-released instances in the instance release set based on the batch record information corresponding to the instance release set, instance monitoring is performed on the instance release set being released via the application monitoring node. This monitors existing to-be-released instances in the instance release set and detects whether new instances have been added to the instance release set. Instance change information obtained from monitoring the instances in the instance release set is used as monitoring information for the instance release set. In actual applications, during the release of pending instances in an instance release set, the instance release set can be scaled down based on the pending instances, i.e., the release of a specific pending instance can be stopped. Alternatively, the instance release set can be expanded, i.e., a new pending instance can be added to the existing pending instances in the instance release set and released. The application monitoring node is used to monitor changes in instances in the instance release set and generate monitoring information based on these changes. Furthermore, considering that the instance release status of pending instances in the instance release set varies at different times during the release of pending instances in the instance release set, and thus the monitoring information obtained also varies, this is specifically implemented as follows: The application monitoring node monitors the release status of instances in the publishing instance release set, obtaining pending release status information, publishing status information, or release completion status information for each instance in the instance release set; and the monitoring information is generated based on the pending release status information, publishing status information, or release completion status information for each target instance in the instance release set. Based on this, the application monitoring node monitors the release status of each instance in the publishing instance release set. Instances in an instance release set can be in the pending release state, the releasing state, or the released state. Each instance in the instance release set corresponds to a release state. By monitoring the release state of each instance in the releasing instance release set, you can obtain the pending release state, the releasing state, or the released state information for each instance in the instance release set.Monitoring information for the instance release set can be generated based on the pending release status information, the in-progress release status information, or the completed release status information of each target instance in the instance release set. In summary, during the release process of pending instances in the instance release set, the release status of the pending instances is monitored to ensure the orderly release of the pending instances in the instance release set. Monitoring the release status allows real-time monitoring of the release status of the pending instances. Step 306: If the monitoring information determines that the instance release set contains a modified instance and that the modified instance is in the pending release state, the batch record information is updated based on the monitoring information. Specifically, after obtaining monitoring information through instance monitoring of the in-progress instance release set, if the monitoring information determines that the instance release set contains a modified instance and that the modified instance is in the pending release state, the batch record information is updated based on the monitoring information. A modified instance refers to an instance whose instance status has changed or has been newly added. Based on this, after monitoring the instance release set for the instance being released and obtaining monitoring information, if the monitoring information determines that the instance release set contains a changed instance and the changed instance is in the pending release state, the batch record information is updated based on the monitoring information. If the monitoring information determines that the instance release set contains a changed instance, this indicates that the instance state of the pending instance in the instance release set has changed, or that a new instance has been added to the instance release set. The pending release state of the changed instance indicates that the changed instance has not yet been released. Furthermore, considering that the pending instances in the instance release set may be suspended due to scaling down, or that new instances may be added to the instance release set due to scaling up, the batch record information needs to be updated when the instance release set changes to ensure information consistency. This is specifically achieved by matching the instance batch information contained in the monitoring information with the batch record information, determining correction information based on the matching result, and correcting the batch record information based on the correction information.Specifically, instance batch information refers to the instance name and batch information of each instance included in the instance release set. The matching result refers to the comparison between the batch information of each batch 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 mismatch. For example, if the instance batch information includes the fourth batch, but the batch record information does not, it is determined to be a "mismatch." If the instance batch information includes the third batch, and the third batch corresponds to instances B and C, but the third batch in the batch record information corresponds to instance B, it is determined to be a "partial match." The correction information is used to modify the batch record information according to the instance batch information. Based on this, the instance batch information contained in the monitoring information is matched with the batch record information. The difference between the instance batch information and the batch record information is used as the matching result. The correction information is then determined based on the matching result. The batch record information is then updated based on the correction information. Continuing with the above example, if the instance batch 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" and 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," the matching result is a partial match for the third batch. "Third batch: Instance C to be released, Instance D to be released" is used as the correction information to modify the batch record information "Third batch: Instance C to be released." In summary, when the instance release set changes, the batch record information is updated to ensure information consistency and achieve information synchronization. Furthermore, considering that there may be deleted instances or newly added instances in the instance release set, the batch record information needs to be updated accordingly for each situation, which is specifically implemented as follows: when it is determined based on the correction information that there is a deleted instance in the instance release set, 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 is deleted; when it is determined based on the correction information that there is a newly added priority release instance in the instance release set, new position information is determined in the batch record information based on the priority information of the newly added priority release instance, and the newly added priority release instance information of the newly added priority release instance is recorded in the batch record information based on the new position information; when it is determined based on the correction information that there is a newly added sequential release instance in the instance release set, the newly added sequential release instance information of the newly added sequential release instance is sequentially added to the batch record information based on the sequence information of the newly added sequential release instance.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 associated with the deleted instance in the batch record information; the newly added priority release instance is the 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 priority release instance; the newly added position information is the position information of the target position where the newly added priority release instance is added to the instance release set; the newly added priority release instance information is the batch information corresponding to the newly added priority release instance; the newly added sequential release instance is the 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 sequential release instance; the newly added sequential release instance information is the batch information of the newly added sequential release instance. Based on this, if the revised information determines that a deleted instance exists in the instance release set, this indicates that an instance in the instance release set needs to be stopped. Based on the deleted batch information of the deleted instance, the batch information to be deleted is determined in the batch record information, and the batch information to be deleted is deleted. If the revised information determines that a new priority release instance exists in the instance release set, this indicates that the new priority release instance needs to be released between any instances in the instance release set. Based on the priority information of the new priority release instance, new position information is determined in the batch record information, and based on the new position information, the new priority release instance information is recorded in the batch record information. The batch information after the new priority release instance information is appropriately modified. If the revised information determines that a new sequential release instance exists in the instance release set, this indicates that the new sequential release instance can be released after the instance at the end of the instance release set. Based on the sequence information of the new sequential release instance, the new sequential release instance information is sequentially added to the batch record information. Continuing with the above example, if the instance release set includes "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" waiting for release instances, 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 a scaling-down scenario, instances are deleted from the instance release set. If pending instance D is deleted, the instance information corresponding to the third batch in the batch record needs to be deleted based on the deletion. In an expansion scenario, the newly added instance can be published after pending instance C in the third batch. Alternatively, the newly added instance can be listed before any other instance. In summary, when there are deleted instances, newly added priority release instances, and newly added sequential release instances in the instance release set, the batch record information is updated accordingly, ensuring consistency between the batch record information and the instance release information in the instance release set. Step 308: Continuing to publish the instance release set containing the changed instance based on the updated batch record information. Specifically, when it is determined based on monitoring information that the instance release set includes a changed instance and the changed instance is in a pending release state, after the batch record information is updated based on the monitoring information, the instance release set including the changed instance can be continued to be released based on the updated batch record information. Continuing to release the instance release set including the changed instance means continuing to release unreleased instances in the instance release set including the changed instance even if some pending instances in the instance release set have already been released. Based on this, when it is determined based on monitoring information that the instance release set includes a changed instance and the changed instance is in a pending release state, after the batch record information is updated based on the monitoring information, the instance release set including the changed instance can be continued to be released based on the updated batch record information, and instances in the instance release set that need to be released can be continued to be released.Furthermore, considering that during the process of publishing pending instances in an instance publication set, a pending instance may be added to the instance publication set or deleted from the instance publication set, in this case, it is necessary to continue publishing for the instance publication set containing the changed instance. This is specifically implemented as follows: if the changed instance contained in the instance publication set is a newly added instance, determining a first publication instance and the changed instance contained in the instance publication set based on updated batch record information, wherein the first publication instance represents the original pending instance in the instance publication set; if the first publication instance is published completely, continuing to publish the changed instance based on the updated batch record information; if the first publication instance is not published completely, continuing to publish the first publication instance and the changed instance based on the updated batch record information; if the changed instance contained in the instance publication set is a modified instance, continuing to publish the instance publication set containing the modified instance based on the updated batch record information includes: determining a second publication instance contained in the instance publication set based on the updated batch record information, and continuing to publish the second publication instance, wherein the second publication instance represents the modified instance in the instance publication set that is in a pending state. Specifically, a newly added instance refers to an instance added to an instance release set after the instance release set already contains pending instances. A first published instance represents an existing pending instance in the instance release set. A changed instance represents a newly added instance in the instance release set. A modified instance represents an instance in which an existing pending instance in the instance release set has been modified. A modified instance can be a change in the instance release state. For example, if an instance in the instance release set changes from the pending state to the stopped state, the pending instance is considered a modified instance. A second published instance represents a modified instance in the instance release set that is in the pending state. Therefore, if a changed instance in the instance release set is a newly added instance, it indicates that the instance release set is expanding, with a new pending instance added to the existing pending instances in the instance release set. The first published instance and the changed instance in the instance release set are determined based on the updated batch record information. If the first published instance is successfully published, it indicates that all the existing pending instances in the instance release set have completed their instance releases. The changed instance can then be published based on the updated batch record information. If the first release instance is not fully released, it means that the original instances to be released in the instance release set are not fully released. The first release instance and the changed instance are continued to be released based on the updated batch record information.If the change instance included in the instance release set is a modified instance, the instance release set is in a scaled-down state. Based on the updated batch record information, the second release instance included in the instance release set that needs to be released is determined, and the second release instance is released. Using the above example, in a scale-up scenario, "Batch 1: Instance A to be released; Batch 2: Instance B to be released; C to be released" can be added to the original batches. Therefore, the instance release set containing the newly added instance D needs to be released. If instances A, B, and C are all released, instance D is released. If there are unreleased instances among instances A, B, and C, instance D is released after instances A, B, and C are released. In a scale-down scenario, based on the original batches ("First batch: Instance A to be released; Second batch: Instance B to be released; Third batch: Instance C to be released"), instance C to be released can be deleted or suspended. Only instance A and instance B to be released need to be released. In summary, when the changed instances included in the instance release set are newly added instances, and when the changed instances included in the instance release set are modified instances, releases are continued for the instances included in the instance release set, thereby improving instance release efficiency. Furthermore, considering that the data center node records the number of instances corresponding to the target application and provides data synchronization services during the target application release process, when batch record information is updated, data synchronization based on the updated batch record information is required, and synchronization is performed with the data center node. This is specifically implemented as follows: the updated batch record information is synchronized with the data center node to update the instance record information recorded by the data center node. Specifically, instance record information refers to instance information associated with the target application before and during its release. This information includes, but is not limited to, the number of pending instances associated with the target application, the release status of each pending instance, and instance scaling information during the target application release process. Based on this information, the updated batch record information is synchronized to the data center node to update the instance record information recorded by the data center node. This information includes the number of instances associated with the target application, instance name, instance release status, and instance scaling information during the target application release process.Continuing with the above example, in a capacity expansion scenario, a fourth batch is added to the original batch, along with its corresponding pending instances D, E, and F. "Fourth batch: pending instances D, E, and F" is sent to the data center node. The data center node's record of "pending instances A, B, and C" is updated to "pending instances A, B, C, D, E, and F." In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance release set and, based on this monitoring information, updates the batch record. This instructs the instance release set with changes to continue releasing, enabling flexible processing during the target application release process. This ensures compatibility between the target application's release and elasticity, optimizes the target application's release process, and improves both the target application's release and elasticity efficiency. It's important to note that in actual applications, the release of a target application involves the release of multiple instances within an instance release set, each corresponding to a release batch. Therefore, during the release of pending instances within the instance release set, instances may be added (scaled up) or deleted (scaled down). For example, during the release of instances within an instance release set (first batch: pending instance A; second batch: pending instance B; third batch: pending instance C; fourth batch: pending instance D and pending instance E), instances can be scaled up by adding the fifth batch: pending instance F, and by adding pending instance G to any of the instances in the corresponding batch. Alternatively, instances can be scaled down by deleting pending instance D from the fourth batch. Therefore, the aforementioned operations of "adding the fifth batch: to-be-released instances F," "adding to-be-released instances G to any corresponding batch," and "deleting to-be-released instances D corresponding to the fourth batch" can be performed simultaneously. For specific implementations, please refer to the above-described embodiments and will not be further described here. The following, combined with Figure 4, further illustrates the application monitoring method provided by the present disclosure using the application release as an example. Figure 4 illustrates a process flow chart of an application monitoring method provided by one embodiment of the present disclosure, specifically including the following steps: Step 402: Obtain to-be-released instances associated with the target application stored in the metadata center to form an instance release set.The application publishing and elasticity process is illustrated with reference to Figure 5. As shown in Figure 5, the metadata center is used to store resource data, batch data, elasticity data, and publishing data. When an application publisher requests a publication for a target application, it obtains pending instances from the metadata center and constructs a pending instance publication set. Step 404: Based on a batching strategy, the pending instances in the instance publication set are batched to obtain batch record information. The application publisher formulates a batching strategy and batches instances 1, 2, and 3 included in the instance publication set based on the batching strategy, obtaining batch record information: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3." The batch record information is the original batch data. Step 406: The pending instances in the instance publication set are published according to the batch record information. In actual applications, the pending instances can be published in batch order or simultaneously. This embodiment does not impose any restrictions on the publishing method. During the release process of pending instances in an instance release set, there are two scenarios: compatibility between release and automated scaling, and compatibility between release and automated scaling. The automated elasticity service implements scaling in and out during instance release, assigning scaling tags to scaling instances and scaling tags to scaling instances. Step 408: The application monitoring node monitors the instance release set in progress and obtains monitoring information. The application monitoring node monitors the instance release set, monitors instance change data, and uses this instance change data as monitoring information. The application monitoring node can be a resource coordination modifier, capable of monitoring instance change data, synchronizing data with the metadata center, and sending instance change data to the change engine. After obtaining monitoring information, in the instance application, if the instance is not being released, only the monitoring information can be synchronized to the metadata center to modify the instance count. If the instance is being released, the batch record information recorded by the change engine must be modified while the monitoring information is synchronized to the metadata center. Step 410: The instance batch information contained in the monitoring information is matched with the batch record information, and correction information is determined based on the matching results. In a capacity expansion scenario, the monitored instance change data may include batch additions and instance additions. For example, instances 4, 5, and 6 are added as the fourth batch, based on the existing instances 1, 2, and 3. In a capacity reduction scenario, the monitored instance change data may include batch deletions and instance deletions. For example, instance 3 is deleted from the existing instances 1, 2, and 3, and there are no instances in the third batch.Step 412: When it is determined based on the revision information that a deleted instance exists in the instance release set, 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 is deleted. If an instance is deleted from the instance release set, it indicates a downscaling situation. If the original batch record information for the instance and batch components is "First batch: Instance 1; Second batch: Instance 2, Instance 3; Third batch: Instance 4, Instance 5; Fourth batch: Instance 6," and it is detected that instances 1, 4, and 6 have been downsized, the batch record information "First batch: Instance 1; Second batch: Instance 2, Instance 3; Third batch: Instance 4, Instance 5; Fourth batch: Instance 6" is modified to: "First batch: -; Second batch: Instance 2, Instance 3; Third batch: -, Instance 5; Fourth batch: ." The modified batch record information is the revised batch data. Furthermore, if the monitoring information determines that instance 1 has been deleted, but instance 1 has already been released, the change engine can be instructed to ignore instance 1 and synchronize its release status. This ensures the orderly release of the target application. Step 414: If, based on the revised information, it is determined that a new priority release instance exists in the instance release set, new position information is determined in the batch record based on the priority information of the new priority release instance, and the new priority release instance information of the new priority release instance is recorded in the batch record based on the new position information. In a capacity expansion scenario, a new batch and instance can be added before or after any of the three batches, or an instance can be added after the original batch, thereby adding to the original batch data: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3." After the addition is completed, revised batch data is obtained. Step 416: If, based on the revised information, it is determined that a new sequential release instance exists in the instance release set, the new sequential release instance information of the new sequential release instance is sequentially added to the batch record based on the sequence information of the new sequential release instance. In a capacity expansion scenario, a fourth batch can also be added after the third batch, thereby adding "Fourth batch: Instance 4, Instance 5, Instance 6" to the original batch data: "First batch: Instance 1; Second batch: Instance 2; Third batch: Instance 3." Obtain the corrected batch data. 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.The updated batch record information is synchronized to the metadata center, and the actual instance count in the metadata center is corrected. Step 420: Continuing to publish the instance release set containing the changed instances based on the updated batch record information. By adding a new resource coordination modifier and providing resource coordination services, a non-invasive application release and elasticity approach is achieved, resolving the issue of application releases being unable to implement automated elasticity while maintaining data synchronization, thus addressing the compatibility issue between application release and elasticity. Furthermore, instance change monitoring can be integrated with the change engine to monitor instances in the instance release set being released and obtain monitoring information. Furthermore, an instance count synchronizer can be developed within Kubernetes or externally in non-Kubernetes scenarios. This instance count synchronizer can be used to directly synchronize the updated batch record information to the metadata center, thereby achieving compatibility between the target application's release and elasticity, and optimizing the target application's release process. In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). By monitoring the instance release set through the application monitoring node, batch record information can be updated based on the determined monitoring information, thereby guiding the continued release of instance release sets with instance changes, enabling flexible processing during the target application release process. This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency. Corresponding to the above method embodiments, the present disclosure also provides an application monitoring system embodiment. Figure 6 shows a structural diagram of an application monitoring system provided by one embodiment of the present disclosure. As shown in Figure 6, the application monitoring system 600 includes a server 610, an application monitoring node 620 and a data center node 630: the server 610 is used to determine the instance release set associated with the 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 used to perform instance monitoring on the instance release set being released, obtain monitoring information, and send the monitoring information to the server 610; the server 610 is used to generate instance change information corresponding to the target application based on the monitoring information when it is determined that the instance release set contains a changed instance and the changed instance is in a released state according to the monitoring information, and synchronize the instance change information to the data center node 630.In actual applications, application monitoring system 600 includes a server 610, an application monitoring node 620, and a data center node 630. Server 610 determines the instance release set associated with the target application based on a release request submitted by the application publisher, determines a batch policy corresponding to the application publisher, and determines batch record information corresponding to the instance release set based on the batch policy. Based on the batch record information, the server publishes pending instances in the instance release set. Application monitoring node 620 monitors the instance release set in progress, obtains monitoring information, and sends the monitoring information to server 610. oIf server 610 determines, based on the monitoring information, that the instance release set includes a changed instance and that the changed instance is in the released state, it generates instance change information corresponding to the target application based on the monitoring information and synchronizes the instance change information to data center node 630, thereby changing the number of instances associated with the target application. Server 610 is configured to extract tag information of the newly added instance from the monitoring information; generate instance new information based on the tag information of the newly added instance; and use the instance new information as the instance change information corresponding to the target application. If the monitoring information determines that the changed instance is a modified instance, generating instance change information corresponding to the target application based on the monitoring information includes: extracting 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. 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 it to the data center node 630; receive at least one to-be-released instance fed back by the data center node 630 in response to the instance acquisition request, and store the at least one to-be-released instance in the instance release set. The server 610 is configured to determine a batch tag for each to-be-released instance in the instance release set based on an instance release policy, wherein the instance release policy indicates 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 tag of each to-be-released instance, and release the to-be-released instances in the instance release set based on the batch record information. The server 610 is configured to monitor the publishing status of instances included in the instance publishing set in progress through the application monitoring node 620, obtain pending publishing status information, publishing status information, or publishing completion status information for each instance in the instance publishing set, and generate the monitoring information based on the pending publishing status information, publishing status information, or publishing completion status information for each target instance in the instance publishing set. In summary, during the publishing process of pending instances in the instance publishing set corresponding to the target application, the instance publishing set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance publishing set, generates instance change information based on the determined monitoring information, and synchronizes the instance change information to the data center node, thereby achieving flexible processing during the target application publishing process.This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency. The above is a schematic diagram of an application monitoring system according to this embodiment. It should be noted that the technical solution of this application monitoring system shares the same concept as the technical solution of the aforementioned application monitoring method. For details not described in detail in the technical solution of the application monitoring system, please refer to the description of the technical solution of the aforementioned application monitoring method. Corresponding to the aforementioned method embodiment, the present disclosure also provides an application monitoring system embodiment. Figure 7 shows a structural diagram of another application monitoring system according to one embodiment of the present disclosure. As shown in Figure 7, application monitoring system 700 includes a server 710 and an application monitoring node 720. Server 710 is configured to determine an instance release set associated with a target application and publish pending instances in the instance release set based on batch record information corresponding to the instance release set. Application monitoring node 720 is configured to monitor instances of the instance release set being published, obtain monitoring information, and send the monitoring information to server 710. If server 710 determines, based on the monitoring information, that the instance release set contains a modified instance and the modified instance is in a pending release state, it is configured to update the batch record information based on the monitoring information. The instance release set containing the modified instance is then continued to be published based on the updated batch record information. In actual applications, application monitoring system 700 includes server 710 and application monitoring node 720. Server 710 determines the instance release set associated with a target application based on a release request submitted by an application publisher, determines a batch policy corresponding to the application publisher, and determines batch record information corresponding to the instance release set based on the batch policy. The pending instances in the instance release set are released based on the batch record information. Application monitoring node 720 monitors the instance release set in progress, obtains monitoring information, and sends the monitoring information to server 710. If server 710 determines from the monitoring information that the instance release set contains a changed instance and that the changed instance is in a pending release state, it updates the batch record information based on the monitoring information. Based on the updated batch record information, server 710 continues to release the instance release set containing the changed instance. Simultaneously, it generates instance change information corresponding to the target application based on the monitoring information, synchronizes the instance change information with the data center node, and changes the number of instances associated with the target application.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 retrieval 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 retrieval request, and store the at least one to-be-released instance in the instance release set. The server 710 is configured to determine a batch tag for each to-be-released instance in the instance release set based on an instance release policy, wherein the instance release policy indicates 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 tag of each to-be-released instance, and release the to-be-released instances in the instance release set based on the batch record information. The server 710 is configured to monitor the release status of instances included in the instance release set being released, through the application monitoring node 720, to obtain to-be-released status information, in-progress status information, or release completion status information of each instance in the instance release set; and generate the monitoring information based on the to-be-released status information, in-progress status information, or release completion status information of each target instance in the instance release set. The server 710 is configured to match the instance batch information included in the monitoring information with the batch record information, determine correction information based on the matching result, and correct the batch record information based on the correction information. The server 710 is configured to, if it is determined based on the correction information that a deleted instance exists in the instance release set, determine batch information to be deleted from the batch record information based on the deleted batch information of the deleted instance, and delete the batch information to be deleted. If it is determined based on the correction information that a new priority release instance exists in the instance release set, determine new location information in the batch record information based on the priority information of the new priority release instance, and record the new priority release instance information of the new priority release instance in the batch record information based on the new location information. If it is determined based on the correction information that a new sequential release instance exists in the instance release set, add the new sequential release instance information of the new sequential release instance to the batch record information sequentially based on the sequence information of the new sequential release instance.The server 710 is configured to determine, based on the updated batch record information, a first publication instance and the change instance included in the instance publication set, where the first publication instance represents an instance to be published in the instance publication set. If the first publication instance is published, the change instance is continued to be published based on the updated batch record information. If the first publication instance is not published, the first publication instance and the change instance are continued to be published based on the updated batch record information. If the change instance included in the instance publication set is a modified instance, the continuing to publish the instance publication set including the modified instance based on the updated batch record information includes: determining, based on the updated batch record information, a second publication instance included in the instance publication set, and continuing to publish the second publication instance, where the second publication instance represents a modified instance in the instance publication set that is in a pending publication state. The server 710 is configured to synchronize the updated batch record information to a data center node to update the instance record information recorded by the data center node. In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance release set and updates batch record information based on the determined monitoring information, thereby guiding the continued release of instance release sets with instance changes, thus enabling flexible processing during the target application release process. This achieves compatibility between target application release and flexibility, optimizes the target application release process, and improves target application release and flexibility efficiency. The above is a schematic diagram of another application monitoring system according to this embodiment. It should be noted that the technical solutions of this application monitoring system and the technical solutions of the aforementioned application monitoring method share the same concept. For details not described in detail in the technical solutions of the application monitoring system, please refer to the description of the technical solutions of the aforementioned application monitoring method. Corresponding to the aforementioned method embodiments, the present disclosure also provides an embodiment of an application monitoring device. Figure 8 shows a schematic structural diagram of an application monitoring device according to one embodiment of the present disclosure.As shown in Figure 8, the application monitoring device includes: 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 batch record information corresponding to the instance publishing set; a monitoring module 804, configured to perform instance monitoring on the instance publishing set being published to obtain monitoring information; a synchronization module 806, configured to generate instance change information corresponding to the target application based on the monitoring information when it is determined according to the monitoring information that the instance publishing set contains a changed instance and the changed instance is in a published state, and synchronize the instance change information to a data center node. In an optional embodiment, the synchronization module 806 is further configured to: extract the tag information of the newly added instance from the monitoring information; generate instance new information based on the tag information of the newly added instance, and use the instance new information as the instance change information corresponding to the target application; In an optional embodiment, the synchronization module 806 is further configured to: extract the tag information of the modified instance from the monitoring information; generate instance modification information based on the tag information of the modified instance, and use the instance modification information as the instance change information corresponding to the target application. In an optional embodiment, the publishing module 802 is further 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 it to the data center node; receive at least one to-be-published instance fed back by the data center node in response to the instance acquisition request, and store the at least one to-be-published instance in the instance publication set. In an optional embodiment, the publishing module 802 is further configured to: determine a batch tag for each to-be-published instance in the instance publishing set based on an instance publishing policy, wherein the instance publishing policy indicates the publishing order of the to-be-published instances in the instance publishing set; determine the batch record information corresponding to the instance publishing set based on the batch tag of each to-be-published instance, and publish the to-be-published instances in the instance publishing set based on the batch record information. In an optional embodiment, the monitoring module 804 is further configured to: monitor the publishing status of instances included in the publishing instance publishing set using a monitoring node to obtain to-be-published status information, publishing status information, or publishing completion status information of each instance in the instance publishing set; and generate the monitoring information based on the to-be-published status information, publishing status information, or publishing completion status information of each target instance in the instance publishing set.In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance release set, generates instance change information based on the determined monitoring information, and synchronizes this instance change information to the data center node, enabling elastic processing during the target application release process. This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency. The above is a schematic diagram 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 aforementioned application monitoring method share the same concept. For details not described in detail in the technical solution of the application monitoring device, please refer to the description of the technical solution of the aforementioned application monitoring method. Corresponding to the aforementioned method embodiment, the present disclosure also provides another embodiment of an application monitoring device. Figure 9 shows a schematic structural diagram of another application monitoring device according to one embodiment of the present disclosure. As shown in Figure 9, the application monitoring apparatus includes: a publishing module 902 configured to determine an instance release set associated with a target application and, based on the batch record information corresponding to the instance release set, publish pending instances in the instance release set; a monitoring module 904 configured to monitor instances of the instance release set being published and obtain monitoring information; an updating module 906 configured to, upon determining, based on the monitoring information, that the instance release set includes a modified instance and the modified instance is in a pending release state, update the batch record information based on the monitoring information; and a continuing publishing module 908 configured to continue publishing the instance release set including the modified instance based on the updated batch record information. In an optional embodiment, the publishing module 902 is further 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 it to the data center node; receive at least one pending instance fed back by the data center node in response to the instance acquisition request, and store the at least one pending instance in the instance release set.In an optional embodiment, the publishing module 902 is further configured to: determine a batch tag for each pending instance in the instance publishing set based on an instance publishing policy, wherein the instance publishing policy indicates the publishing order of the pending instances in the instance publishing set; determine the batch record information corresponding to the instance publishing set based on the batch tag of each pending instance; and publish the pending instances in the instance publishing set based on the batch record information. In an optional embodiment, the monitoring module 904 is further configured to: monitor the publishing status of instances included in the instance publishing set in progress by applying a monitoring node to obtain pending status information, publishing status information, or publishing completed status information of each instance in the instance publishing set; and generate the monitoring information based on the pending status information, publishing status information, or publishing completed status information of each target instance in the instance publishing set. In an optional embodiment, the updating module 906 is further configured to: match the instance batch information included in the monitoring information with the batch record information, determine correction information based on the matching result, and correct the batch record information based on the correction information. In an optional embodiment, the update module 906 is further configured to: when it is determined based on the correction information that there is a deleted instance in the instance release set, determine the batch information to be deleted in the batch record information based on the deleted batch information of the deleted instance, and delete the batch information to be deleted; when it is determined based on the correction information that there is a newly added priority release instance 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 priority release instance, and record the newly added priority release instance information of the newly added priority release instance to the batch record information based on the newly added position information; when it is determined based on the correction information that there is a newly added sequential release instance in the instance release set, add the newly added sequential release instance information of the newly added sequential release instance in sequence to the batch record information based on the sequence information of the newly added sequential release instance.In an optional embodiment, the continuing publishing module 908 is further configured to: determine a first publishing instance and the change instance included in the instance publication set based on the updated batch record information, wherein the first publishing instance represents an instance to be published in the instance publication set; if the first publishing instance is published, continue publishing the change instance based on the updated batch record information; if the first publishing instance is not published, continue publishing the first publishing instance and the change instance based on the updated batch record information; if the change instance included in the instance publication set is a modified instance, continuing publishing the instance publication set including the modified instance based on the updated batch record information includes: determining a second publishing instance included in the instance publication set based on the updated batch record information, and continuing publishing the second publishing instance, wherein the second publishing instance represents a modified instance in the instance publication set that is in a pending state. In an optional embodiment, the continuing publishing module 908 is further configured to: synchronize the updated batch record information to a data center node to update the instance record information recorded by the data center node. In summary, during the release of pending instances in the instance release set corresponding to the target application, the instance release set allows instance changes, namely, the addition or deletion of instances (capacity expansion or reduction). The application monitoring node then monitors the instance release set and updates batch record information based on the determined monitoring information, thereby guiding the continued release of instance release sets with instance changes, thus enabling elastic processing during the target application release process. This achieves compatibility between target application release and elasticity, optimizes the target application release process, and improves target application release and elasticity efficiency. The above is a schematic diagram of another application monitoring device according to this embodiment. It should be noted that the technical solutions of this application monitoring device and the technical solutions of the aforementioned application monitoring method share the same concept. For details not described in detail in the technical solution of the application monitoring device, please refer to the description of the technical solution of the aforementioned application monitoring method. Figure 10 shows a block diagram of a computing device 1000 according to one embodiment of the present disclosure. Components of 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 via a bus 1030. The database 1050 is used to store data. The computing device 1000 also includes an access device 1040, which enables the computing device 1000 to communicate via one or more networks 1060.Examples of these networks include the 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 (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, or a near field communication (NFC) interface. In one embodiment of the present disclosure, the aforementioned components of the computing device 1000 and other components not shown in FIG. 10 may also be connected to each other, for example, via a bus. It should be understood that the computing device structure block diagram shown in FIG. 10 is for illustrative purposes only and does not limit the scope of the present disclosure. Those skilled in the art may add or replace other components as needed. 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, personal digital assistant, laptop computer, notebook computer, netbook, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). Computing device 1000 can also be a mobile or stationary server. Processor 1020 is configured to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the aforementioned application monitoring method. The above is a schematic diagram of a computing device according to this embodiment.It should be noted that the technical solution of this computing device and the technical solution of the aforementioned application monitoring method are based on the same concept. Any details not described in detail in the technical solution of the computing device can be found in the description of the technical solution of the aforementioned application monitoring method. One embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these computer-executable instructions implement the steps of the aforementioned application monitoring method. The above is a schematic diagram of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the aforementioned application monitoring method are based on the same concept. Any details not described in detail in the technical solution of the storage medium can be found in the description of the technical solution of the aforementioned application monitoring method. One embodiment of the present disclosure also provides a computer program product comprising a computer program / instructions. When executed by a processor, these computer program / instructions implement the steps of the aforementioned application monitoring method. The above is a schematic diagram of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the aforementioned application monitoring method are based on the same concept. Any details not described in detail in the technical solution of the computer program can be found in the description of the technical solution of the aforementioned application monitoring method. The above describes specific embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the figures do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous. The computer instructions include computer program code, which may be in source code form, object code form, executable files, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, removable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media. It should be noted that the content of the computer-readable medium may be appropriately increased or decreased based on the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media does not include electrical carrier signals and telecommunication signals.It should be noted that, for ease of description, the aforementioned method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present disclosure are not limited by the order of the actions described, as certain steps may be performed in a different order or simultaneously, depending on the embodiments of the present disclosure. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are preferred embodiments, and the actions and modules described are not necessarily required for the embodiments of the present disclosure. In the above embodiments, the description of each embodiment has its own emphasis. For portions not described in detail in a particular embodiment, reference should be made to the relevant descriptions of other embodiments. The preferred embodiments disclosed above are merely intended to help illustrate the present disclosure. The optional embodiments do not describe all details in detail, nor do they limit the invention to the specific implementations described. Obviously, many modifications and variations are possible based on the content of the embodiments of the present disclosure. The present disclosure selects and describes these embodiments in detail to better explain the principles and practical applications of the embodiments of the present disclosure, thereby enabling those skilled in the art to better understand and utilize the present disclosure. The present disclosure is limited only by the claims and their full scope and equivalents.

Claims

Claims 1. An application monitoring method, comprising: 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; perform 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 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.

2. The application monitoring method according to claim 1, in the case where it is determined based on the monitoring information that the change instance is a newly added instance, the generating of the instance change information corresponding to the target application based on the monitoring information includes: Extract the label information of the newly added instances from the monitoring information, and use the label information of the newly added instances as the changed label information; Generate instance addition information based on the changed label information, and use 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 change instance is a modification instance, generating the instance change information corresponding to the target application based on the monitoring information includes: Extract the label information of the modified instances from the monitoring information; Generate instance modification information based on the label information of the modified instances, and use the instance modification information as the instance change information corresponding to the target application.

4. The application monitoring method according to any one of claims 1-3, wherein the determining the instance release set associated with the target application comprises: 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 the instance acquisition request to 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.

5. The application monitoring method according to any one of claims 1-4, wherein the step of publishing the instance to be published in the instance publishing set based on the batch record information corresponding to the instance publishing set comprises: Determine the batch labels of the instances 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 labels of the instances to be released, and release the instances to be released in the instance release set based on the batch record information.

6. The application monitoring method according to any one of claims 1-5, wherein the instance monitoring of the instance release set being released to obtain monitoring information includes: 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 by monitoring the release status of the instances included in the instance release set during the release through the application monitoring node; Generate 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.

7. An application monitoring method, comprising: 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; perform 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 the to-be-released state, 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. The application monitoring method according to claim 7, wherein the updating of the batch record information based on the monitoring information comprises: 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.

9. The application monitoring method according to claim 8, wherein the correcting the batch record information based on the correction information comprises: In the case where it is determined based on the correction information that there are deleted instances 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 deleted instances, and delete the batch information to be deleted; In the case where 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 information of the newly added priority release instances of the newly added priority release instances to the batch record information based on the new position information; in the case where it is determined based on the correction information that there are newly added sequential release instances in the instance release set, sequentially add the information of the newly added sequential release instances of the newly added sequential release instances to the batch record information based on the sequential information of the newly added sequential release instances.

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

11. The application monitoring method according to any one of claims 7-10 further includes: 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 during the release process, obtain monitoring information, and send the monitoring information to the server; The server is configured to generate instance change information corresponding to the target application based on the monitoring information and synchronize it to the data center node when 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.

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 during the release process, obtain monitoring information, and send the monitoring information to the server; The server 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 the to-be-released state; and continue to release the instance release set containing the changed instances based on the updated batch record information.

14. A computing device, comprising: A memory and a processor; The memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions. 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 storing computer-executable instructions, which, when executed by a processor, implement the steps of the application monitoring method according to any one of claims 1 to 11.

16. A computer program product, comprising a computer program / instructions, which, when executed by a processor, implement the steps of the application monitoring method according to any one of claims 1 to 11.

Images