Data processing method and device, medium, equipment and product

Abstract

The invention relates to a data processing method and device, a medium, equipment and a product, the data processing method and device are applied to a container arrangement system, the container arrangement system comprises one or more container groups, and the method comprises the steps that the current running state of each container group in the one or more container groups is acquired; determining at least one target container group with faults in the one or more container groups according to the current running state of each container group; obtaining fault information of each target container group; and for each target container group, determining fault processing prompt data corresponding to the fault information through preset relation data according to the fault information. Therefore, the target container group with the fault can be quickly and accurately positioned, and the fault processing prompt data corresponding to the fault information of the target container group can also be quickly and accurately determined, so that the reliability and efficiency of operation and maintenance can be effectively improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular, to a data processing method, apparatus, medium, equipment, and product. Background Art

[0002] Container orchestration systems encompass multiple layers of dependencies, and problems can arise at any of these layers. During system operation, a large number of event logs are generated, scattered across various parts of the container orchestration system.

[0003] In existing technologies, when problems arise with container groups in container orchestration systems, operations and maintenance personnel typically need to manually screen and analyze them. However, this approach is not only time-consuming and labor-intensive, but also prone to missing critical information. Furthermore, effective problem diagnosis requires operators to possess advanced technical skills and extensive practical experience. Even if the cause of the error can be manually pinpointed, quickly resolving the issue still requires a deep operations and maintenance background and specialized technical knowledge. Consequently, existing operations and maintenance methods suffer from low reliability and efficiency. Summary of the Invention

[0004] To overcome the problems existing in the related art, the present disclosure provides a data processing method, apparatus, medium, equipment and product.

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a data processing method, which is applied to a container orchestration system, wherein the container orchestration system includes one or more container groups. The method includes: Obtaining a current running status of each of the one or more container groups; Determine at least one target container group having a fault among the one or more container groups according to the current running status of each container group; Obtaining fault information of each target container group; For each target container group, fault processing prompt data corresponding to the fault information is determined according to the fault information through preset relationship data, where the preset relationship data includes preset processing prompt information of different container group identifiers under multiple fault types.

[0006] Optionally, the container group includes one or more containers, and the current running state includes a waiting-to-be-scheduled state, a normal running state, and a non-running state. Determining at least one target container group having a fault among the one or more container groups according to the current running state of each container group includes: For each container group, if it is determined that the current operating state is a non-operating state, the container group is used as the target container group; and if it is determined that the current operating state is a waiting-to-be-scheduled state or a normal operating state, the container group is used as a standby container group; Obtaining the container status of each container in the standby container group; Determine whether the standby container group belongs to the target container group according to the container status of each container in the standby container group.

[0007] Optionally, the container status includes a creation process status, an error status, and an unready status, and determining whether the standby container group belongs to the target container group according to the container status of each container in the standby container group includes: When it is determined that the container status of at least one container in the standby container group is the creation process state or the unready state, obtaining an event record of the standby container group within a preset time; When it is determined that the event record includes a first error identifier and a first error cause, using the standby container group as the target container group; When it is determined that the container status of at least one container in the standby container group is the error status, the standby container group is used as the target container group.

[0008] Optionally, the container group includes one or more containers, and the container status includes a creation process status, an error status, and an unready status. The acquiring fault information of each target container group includes: If at least one container in the target container group is in the error state, error information of the standby container group is obtained, the error information including a second error identifier and a second error cause, and the target identifier of the target container group, the second error identifier, and the second error cause in the error information are used as fault information of the target container group; If no container in the target container group has a container status in the error state, and if it is determined that the event record of the target container group contains a first error identifier and a first error cause, the target identifier of the target container group, the first error identifier, and the first error cause in the event record are used as fault information of the target container group.

[0009] Optionally, the fault information includes a target identifier, a target error identifier, and a target error cause of the target container group; the fault type includes an error identifier field and an error cause field; and determining fault handling prompt data corresponding to the fault information using preset relationship data based on the fault information includes: When it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, determining a target fault type of the target container group according to the target error identifier and the target error cause; Target processing prompt information corresponding to the target fault type is determined from the preset relationship data, and the target processing prompt information is used as the fault processing prompt data of the target container group.

[0010] Optionally, the preset processing prompt information includes multiple operation and maintenance information segments, and obtaining the preset relationship data includes: Acquire multiple operation and maintenance document data of the container orchestration system, where the operation and maintenance document data is used to describe a fault type and processing prompt information corresponding to the fault type; Inputting the plurality of operation and maintenance document data into a preset text embedding model to obtain a plurality of operation and maintenance information segments corresponding to each fault type output by the text embedding model; The multiple operation and maintenance information segments corresponding to each fault type are used as the preset relationship data.

[0011] Optionally, the fault handling prompt data includes one or more target operation and maintenance information segments, and the method further includes: The one or more target operation and maintenance information segments, the container group identifier, the fault type and preset language processing requirement information are input into a preset language processing model to obtain target operation and maintenance prompt data output by the language processing model.

[0012] According to a second aspect of an embodiment of the present disclosure, there is provided a data processing apparatus, applied to a container orchestration system, the container orchestration system including one or more container groups, the apparatus including: A first acquisition module is configured to acquire a current running status of each of the one or more container groups; A first determining module is configured to determine at least one target container group having a fault among the one or more container groups based on a current operating status of each container group; A second acquisition module is configured to acquire fault information of each target container group; A second determining module is configured to determine, for each target container group, fault handling prompt data corresponding to the fault information using preset relationship data based on the fault information, wherein the preset relationship data includes preset handling prompt information for different container group identifiers under multiple fault types.

[0013] Optionally, the container group includes one or more containers, the current running state includes a waiting-to-be-scheduled state, a normal running state, and a non-running state, and the first determining module is configured to: For each container group, if it is determined that the current operating state is a non-operating state, the container group is used as the target container group; and if it is determined that the current operating state is a waiting-to-be-scheduled state or a normal operating state, the container group is used as a standby container group; Obtaining the container status of each container in the standby container group; Determine whether the standby container group belongs to the target container group according to the container status of each container in the standby container group.

[0014] Optionally, the container status includes a creation process status, an error status, and an unready status, and the first determining module is further configured to: When it is determined that the container status of at least one container in the standby container group is the creation process state or the unready state, obtaining an event record of the standby container group within a preset time; When it is determined that the event record includes a first error identifier and a first error cause, using the standby container group as the target container group; When it is determined that the container status of at least one container in the standby container group is the error status, the standby container group is used as the target container group.

[0015] Optionally, the container group includes one or more containers, and the container status includes a creation process status, an error status, and an unready status. The second acquisition module is configured to: If at least one container in the target container group is in the error state, error information of the standby container group is obtained, the error information including a second error identifier and a second error cause, and the target identifier of the target container group, the second error identifier, and the second error cause in the error information are used as fault information of the target container group; If no container in the target container group has a container status in the error state, and if it is determined that the event record of the target container group contains a first error identifier and a first error cause, the target identifier of the target container group, the first error identifier, and the first error cause in the event record are used as fault information of the target container group.

[0016] Optionally, the fault information includes a target identifier, a target error identifier, and a target error cause of the target container group; the fault type includes an error identifier field and an error cause field; and the second determining module is configured to: When it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, determining a target fault type of the target container group according to the target error identifier and the target error cause; Target processing prompt information corresponding to the target fault type is determined from the preset relationship data, and the target processing prompt information is used as the fault processing prompt data of the target container group.

[0017] Optionally, the fault handling prompt data includes one or more target operation and maintenance information segments, and the device further includes: The third acquisition module is used to input the one or more target operation and maintenance information fragments, the container group identifier, the fault type and the preset language processing requirement information into a preset language processing model to obtain the target operation and maintenance prompt data output by the language processing model.

[0018] According to a third aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the method provided in the first aspect of the present disclosure are implemented.

[0019] According to a fourth aspect of an embodiment of the present disclosure, there is provided an electronic device, including: a memory having a computer program stored thereon; A processor is used to execute the computer program in the memory to implement the steps of the method described in the first aspect of the embodiment of the present disclosure.

[0020] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program, which implements the steps of the method described in the first aspect of an embodiment of the present disclosure when executed by a processor.

[0021] The above technical solution obtains the current operating status of each of the one or more container groups; determines at least one target container group in the one or more container groups that has a fault based on the current operating status of each container group; obtains fault information for each target container group; and, for each target container group, determines fault handling prompt data corresponding to the fault information based on the fault information using preset relationship data, wherein the preset relationship data includes preset handling prompt information for different container group identifiers under multiple fault types. In this way, by determining at least one target container group in the one or more container groups that has a fault based on the current operating status of each container group, and determining the fault handling prompt data corresponding to the fault information based on the fault information using preset relationship data, the target container group with a fault can be quickly and accurately located, and the fault handling prompt data corresponding to the fault information of the target container group can be quickly and accurately determined, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0022] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following detailed description, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings: Figure 1 is a flow chart showing a data processing method according to an exemplary embodiment; Figure 2 is based on Figure 1 A flow chart of a data processing method shown in the illustrated embodiment; Figure 3 is based on Figure 2 A flow chart of a data processing method shown in the illustrated embodiment; Figure 4 is based on Figure 2 A flow chart of another data processing method shown in the illustrated embodiment; Figure 5 is based on Figure 1 A flow chart of another data processing method shown in the illustrated embodiment; Figure 6 is based on Figure 1 A flow chart of yet another data processing method shown in the illustrated embodiment; Figure 7 is a flow chart showing a data processing method according to an exemplary embodiment; Figure 8 is a block diagram of a data processing device according to an exemplary embodiment; Figure 9 is a block diagram of an electronic device according to an exemplary embodiment; Figure 10 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0024] The following describes the specific embodiments of the present disclosure in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to illustrate and explain the present disclosure and are not intended to limit the present disclosure.

[0025] Before detailing the specific implementations of the present disclosure, we first describe its application scenarios. This disclosure can be applied to the operation and maintenance of Kubernetes (a container orchestration system). A pod (a container group) is the smallest deployable and manageable computing unit in a Kubernetes cluster. A pod can contain one or more closely related containers that share the same network namespace, storage volumes, and other resources. Diagnosing and resolving pod issues is a common problem in Kubernetes cluster operations. Existing techniques typically use command queries and log queries to locate issues. Kubernetes clusters have a complex architecture, involving dependencies at multiple levels, and faulty container groups can occur at any level. Kubernetes clusters generate a large volume of event logs distributed across multiple locations, requiring manual sifting and analysis by operations personnel. However, manually reviewing logs and events at each level is time-consuming and labor-intensive, and can easily miss important information. Furthermore, problem diagnosis requires a high level of technical expertise and experience from the operations personnel. Furthermore, even if the cause of the error can be manually identified, quickly resolving the issue still requires a deep operations background and specialized technical knowledge. Therefore, the operation and maintenance methods in the existing technology have problems with reliability and low efficiency.

[0026] To address the above-mentioned issues, the solution of the present application obtains the current operating status of each of the one or more container groups; determines at least one target container group in the one or more container groups that has a fault based on the current operating status of each container group; obtains fault information for each target container group; and, for each target container group, determines fault handling prompt data corresponding to the fault information based on the fault information using preset relationship data, wherein the preset relationship data includes preset handling prompt information for different container group identifiers under various fault types. In this way, by determining at least one target container group in the one or more container groups that has a fault based on the current operating status of each container group, and determining the fault handling prompt data corresponding to the fault information based on the fault information using preset relationship data, the fault handling prompt data can be quickly and accurately located, and the fault handling prompt data corresponding to the fault information of the target container group can be quickly and accurately determined, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0027] Figure 1 is a flow chart of a data processing method according to an exemplary embodiment, which is applied to a container orchestration system, wherein the container orchestration system includes one or more container groups, such as Figure 1 As shown, the data processing method may include the following steps: Step 101: Obtain the current running status of each of the one or more container groups.

[0028] The current operating state includes a waiting-for-scheduling state, a normal operating state, and a non-operating state.

[0029] In this step, the K8s cluster includes multiple namespaces. The container groups in the K8s cluster can be filtered by the label selector to obtain the current running status of each container group in the specified namespace.

[0030] Step 102: Determine at least one target container group with a fault among the one or more container groups according to the current running status of each container group.

[0031] The current operating state includes a waiting-for-scheduling state, a normal operating state, and a non-operating state.

[0032] In one embodiment, determining at least one target container group with a fault among the one or more container groups based on the current operating status of each container group may include: for each container group, if it is determined that the current operating status is a waiting-to-be-scheduled state or a normal operating state, setting the container group as a standby container group; obtaining the container status of each container in the standby container group; and determining whether the standby container group belongs to the target container group based on the container status of each container in the standby container group.

[0033] In another embodiment, determining at least one target container group having a fault among the one or more container groups based on the current operating state of each container group may include: for each container group, if the current operating state is determined to be a non-operating state, selecting the container group as the target container group.

[0034] Step 103: Obtain fault information of each target container group.

[0035] The fault information includes the target identifier of the target container group, the target error identifier and the target error cause.

[0036] Step 104 : For each target container group, determine fault handling prompt data corresponding to the fault information using preset relationship data according to the fault information.

[0037] The preset relationship data may include preset processing prompt information for different container group identifiers under multiple fault types. The preset processing prompt information may include multiple operation and maintenance information segments. The fault processing prompt data may include one or more target operation and maintenance information segments.

[0038] In this step, if it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, the target fault type of the target container group is determined based on the target error identifier and the target error cause; target processing prompt information corresponding to the target fault type is determined from the preset relationship data, and the target processing prompt information is used as the fault processing prompt data for the target container group.

[0039] The above technical solution determines at least one target container group with a fault among the one or more container groups based on the current operating status of each container group, and determines fault handling prompt data corresponding to the fault information based on the fault information using preset relationship data. This allows for rapid and accurate location of the target container group with a fault, and rapid and accurate determination of the fault handling prompt data corresponding to the fault information of the target container group, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0040] Figure 2 is based on Figure 1 The embodiment shown is a flowchart of a data processing method, wherein the container group includes one or more containers, and the current running state includes a waiting state, a normal running state, and a non-running state. Figure 2 As shown, Figure 1 Determining at least one target container group with a fault among the one or more container groups based on the current running status of each container group in step 102 may include: Step 1021 : For each container group, if it is determined that the current running state is a waiting-to-be-scheduled state or a normal running state, the container group is set as a standby container group.

[0041] Step 1022: Obtain the container status of each container in the standby container group.

[0042] The container status includes a creation process status and a non-creation process status, and the non-creation process status includes an error state and a non-error state.

[0043] Step 1023: Determine whether the standby container group belongs to the target container group according to the container status of each container in the standby container group.

[0044] In one embodiment, determining whether the standby container group belongs to the target container group based on the container status of each container in the standby container group may include: if it is determined that the container status of at least one container in the standby container group is the creation process status, obtaining a first event record of the standby container group within a preset time; and if it is determined that the first event record includes a first error identifier and a first error cause, setting the standby container group as the target container group.

[0045] In another embodiment, determining whether the standby container group belongs to the target container group based on the container status of each container in the standby container group may include: if it is determined that the container status of at least one container in the standby container group is the error state, using the standby container group as the target container group.

[0046] The above technical solution determines at least one target container group with a fault among the one or more container groups based on the current operating status of each container group. This can quickly and accurately locate the target container group with a fault, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0047] Figure 3 is based on Figure 2 The embodiment shown is a flowchart of a data processing method, wherein the container state includes a creation process state and a non-creation process state, such as Figure 3 As shown, Figure 2 Determining whether the standby container group belongs to the target container group according to the container status of each container in the standby container group in step 1023 may include: S11: When it is determined that the container status of at least one container in the standby container group is the creation process status, obtain a first event record of the standby container group within a preset time.

[0048] The first event record is an event log of the standby container group.

[0049] In this step, when it is determined that the container status of at least one container in the standby container group is the creation process status, the latest event log of the standby container group is obtained.

[0050] S12: When it is determined that the first event record includes a first error identifier and a first error cause, use the standby container group as the target container group.

[0051] For example, a Kubernetes cluster includes a first container group, a second container group, and a third container group. If the current running state of the third container group is determined to be Pending, the third container group is set as the standby container group. The container states of the containers in the standby container group are obtained. If the container state of at least one container in the standby container group is ContainerCreating, the latest event log for the standby container group is obtained. If the event log contains a first error identifier and a first error cause, the standby container group is set as the target container group.

[0052] The above technical solution determines whether the standby container group belongs to the target container group based on the container status of each container in the standby container group. This can quickly and accurately locate the target container group with a fault, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0053] Alternatively, as Figure 1 Obtaining the fault information of each target container group in step 103 may include: When it is determined that the container status of at least one container in the standby container group is the creation process status, the target identifier of the target container group, and the first error identifier and the first error cause in the first event record are used as fault information of the target container group.

[0054] For example, a K8s cluster includes a first container group, a second container group, and a third container group. If it is determined that the current running state of the third container group is Pending, the third container group is used as a standby container group. The container state of the containers in the standby container group is obtained. If it is determined that the container state of at least one container in the standby container group is ContainerCreating or Unschedulable, the latest event log of the standby container group is obtained. If it is determined that a first error identifier and a first error cause are present in the event log, the target identifier corresponding to the standby container group, as well as the first error identifier and the first error cause in the event log, are used as fault information for the target container group.

[0055] The above technical solution determines the fault information of the target container group, which can provide a basis for subsequently quickly and accurately determining the fault handling prompt data corresponding to the fault information of the target container group.

[0056] Optionally, the non-creation process state includes an error state and a non-error state, such as Figure 2Determining whether the standby container group belongs to the target container group according to the container status of each container in the standby container group in step 1023 may include: When it is determined that the container status of at least one container in the standby container group is the error status, the standby container group is used as the target container group.

[0057] By way of example, the error status may include CrashLoopBackOff status (crash loop back-off status), ImagePullBackOff status (image pull back-off status), CreateContainerConfigError status (create container configuration error status), PreCreateHookError status (pre-create hook error status), CreateContainerError status (create container error status), PreStartHookError status (pre-start hook error status), RunContainerError status (run container error status), ImageInspectError status (image check error status), ErrImagePull status (pull image error status), ErrImageNeverPull status (never pull image error status) and InvalidImageName status (invalid image name error status).

[0058] Alternatively, as Figure 1 The acquisition of the fault information of each target container group in step 103 may further include: If it is determined that the container status of at least one container in the standby container group is the error state, error information of the standby container group is obtained, the error information including a second error identifier and a second error cause; and the target identifier of the target container group, the second error identifier, and the second error cause in the error information are used as fault information of the target container group.

[0059] It should be noted that the first error identifier and the second error identifier may be the same or different, and the first error cause and the second error cause may be the same or different.

[0060] For example, when a container is in the CrashLoopBackOff state, you can directly obtain the container's error flag, CrashLoopBackOff, which indicates that the container is repeatedly crashing and restarting. In addition, the Kubernetes cluster's event log contains event types, such as FailedScheduling events, which can also serve as error flags. The event log contains a more specific description of the error cause. For example, "Failed to pull image "nginx:latest": rpc error: code = Unknown desc = Error response from daemon: manifest unknown" indicates that the image pull failed because the image manifest could not be found.

[0061] The above technical solution determines the fault information of the target container group, which can provide a basis for subsequently quickly and accurately determining the fault handling prompt data corresponding to the fault information of the target container group.

[0062] Figure 4 is based on Figure 2 The embodiment shown is a flowchart of another data processing method, wherein the container state includes an unready state and a ready state, such as Figure 4 As shown, Figure 2 Determining whether the standby container group belongs to the target container group according to the container status of each container in the standby container group in step 1023 may include: S21, when it is determined that the container status of at least one container in the standby container group is the unready state, obtaining a second event record of the standby container group within a preset time; S22: When it is determined that the second event record includes a first error identifier and a first error cause, use the standby container group as the target container group.

[0063] For example, a Kubernetes cluster includes a first container group, a second container group, and a third container group. If the current running state of the third container group is determined to be "running," the third container group is designated as the standby container group. The container status of the containers in the standby container group is obtained. A readiness probe can be used to check the readiness of a container. If the probe fails, the container is considered to be in an unready state. If it is determined that at least one container in the standby container group is in an unready state, the latest event log for the standby container group is obtained. If an unhealthy event is detected in the event log, the specific cause and detailed message description are typically included. For example, the readiness probe may have failed multiple times because the application within the container is unable to respond to requests, or the liveness probe may have failed, indicating that the process within the container has crashed. The standby container group is designated as the target container group.

[0064] The above technical solution determines whether the standby container group belongs to the target container group based on the container status of each container in the standby container group. This can quickly and accurately locate the target container group with a fault, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0065] Alternatively, as Figure 1 The acquisition of the fault information of each target container group in step 103 may further include: If it is determined that the container status of at least one container in the standby container group is the unready state, the target identifier of the target container group, and the first error identifier and the first error cause in the second event record are used as fault information of the target container group.

[0066] In this step, if it is determined that at least one container in the standby container group is in an unready state, the latest event log for the standby container group is obtained. If it is determined that an unhealthy record appears in the event log, it will typically include a specific cause and a detailed message description. For example, the readiness probe may have failed multiple times because the application within the container cannot respond to requests, or the liveness probe may have failed, indicating that the process within the container may have crashed. The standby container group is used as the target container group. The target container group's target identifier, as well as the unhealthy cause and the first error identifier, are used as the target container group's failure information.

[0067] The above technical solution determines the fault information of the target container group, which can provide a basis for subsequently quickly and accurately determining the fault handling prompt data corresponding to the fault information of the target container group.

[0068] Alternatively, as Figure 1 Determining at least one target container group with a fault among the one or more container groups according to the current running status of each container group in step 102 may include: For each container group, when it is determined that the current running state is a non-running state, the container group is used as the target container group.

[0069] The above technical solution determines whether the standby container group belongs to the target container group based on the container status of each container in the standby container group. This can quickly and accurately locate the target container group with a fault, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0070] Alternatively, as Figure 1 Obtaining fault information for each target container group in step 103 may further include: when it is determined that the current operating state is a non-operating state, obtaining a first error identifier and a first error cause from a third event record of the target container group; and using the target identifier of the target container group, the first error identifier, and the first error cause in the third event record as the fault information for the target container group.

[0071] The above technical solution determines the fault information of the target container group, which can provide a basis for subsequently quickly and accurately determining the fault handling prompt data corresponding to the fault information of the target container group.

[0072] Figure 5 is based on Figure 1 The embodiment shown is a flowchart of another data processing method, wherein the fault information includes the target identifier of the target container group, the target error identifier and the target error cause, and the fault type includes an error identifier field and an error cause field, such as Figure 5 As shown, Figure 1 Determining the fault handling prompt data corresponding to the fault information by using preset relationship data according to the fault information in step 104 may include: Step 1041 : When it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, determine the target fault type of the target container group according to the target error identifier and the target error cause.

[0073] The target error identifier may include the first error identifier or the second error identifier, and the target error cause may include the first error cause or the second error cause.

[0074] Step 1042: Determine target processing prompt information corresponding to the target fault type from the preset relationship data, and use the target processing prompt information as the fault processing prompt data of the target container group.

[0075] The above technical solution determines the fault handling prompt data corresponding to the fault information through preset relationship data based on the fault information, and can quickly and accurately determine the fault handling prompt data corresponding to the fault information of the target container group, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0076] Figure 6 is based on Figure 1 The embodiment shown is a flowchart of another data processing method, wherein the preset processing prompt information includes multiple operation and maintenance information fragments, and obtaining the preset relationship data includes: S31, obtaining multiple operation and maintenance document data of the container orchestration system.

[0077] The operation and maintenance document data is used to describe the fault type and the processing prompt information corresponding to the fault type.

[0078] For example, the operation and maintenance document data may include self-created documents, official documents, screened technical documents, etc. These documents contain detailed descriptions and solutions to various container group failures.

[0079] S32: Input the plurality of operation and maintenance document data into a preset text embedding model to obtain a plurality of operation and maintenance information segments corresponding to each fault type output by the text embedding model.

[0080] The text embedding model may be a sentence embedding model.

[0081] S33: Use the multiple operation and maintenance information segments corresponding to each fault type as the preset relationship data.

[0082] In this step, each operation and maintenance document data can be converted into a high-dimensional vector using a sentence embedding model, and the high-dimensional vector is stored in a preset vector search engine to establish a corresponding relationship between each fault type and the multiple operation and maintenance information segments. The high-dimensional vector includes the semantic features of the multiple operation and maintenance information segments, as well as the implicit associations and similarities between the multiple operation and maintenance information segments corresponding to each fault type.

[0083] Optionally, the fault handling prompt data includes one or more target operation and maintenance information segments, and the method further includes: The one or more target operation and maintenance information segments, the container group identifier, the fault type and preset language processing requirement information are input into a preset language processing model to obtain target operation and maintenance prompt data output by the language processing model.

[0084] Among them, the language processing model can be a large language model, such as the Transformer architecture (Transformer Architecture), BERT (Bidirectional Encoder Representations from Transformers), and GPT (Generative Pre-trained Transformer).

[0085] For example, the target operation and maintenance information fragment can be {answer_docs}, the container group identifier can be {name}, the fault type can be {error}, and the preset language processing requirement information can be "You are a professional K8S cluster operation and maintenance expert, please aggregate and integrate the target operation and maintenance information fragments provided by the preset relationship data, and answer the operation and maintenance prompt data corresponding to the container group fault type. Note that the answer is first based on the preset relationship data. If the preset relationship data is not involved, the answer is generated based on the own knowledge."

[0086] The above technical solution determines the fault handling prompt data corresponding to the fault information through preset relationship data based on the fault information, and can quickly and accurately determine the fault handling prompt data corresponding to the fault information of the target container group, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0087] Figure 7 FIG. 1 is a flow chart showing a data processing method according to an exemplary embodiment. The method may include the following steps: Step 701: Initialize the analyzer.

[0088] In this step, you can initialize the analyzer in the K8s cluster and clear the problem indicators related to the current analyzer to avoid contamination of the current round of pod problem diagnosis data due to historical residual information.

[0089] For example, a pod was previously marked as CrashLoopBackOff due to insufficient memory, but the resource issue was subsequently resolved. If the analyzer is not initialized, it may still use the old status as the basis for the current issue.

[0090] Step 702: Traverse the container group list.

[0091] In this step, the K8s cluster includes multiple namespaces. You can filter the container groups in the K8s cluster through the label selector, and perform a traversal check on all pods or specified pods to obtain the current running status of each container group in the specified namespace.

[0092] Step 703: Check the container group status.

[0093] In this step, the current operating status of each container group is determined.

[0094] Step 704: Detect container status.

[0095] In this step, the container status of the containers in the container group is determined.

[0096] Step 705: Build a failed object list.

[0097] In this step, one or more target container groups with faults are determined according to the current running status of each container group and the container status of the containers in the container group, and the one or more target container groups are used as a failed object list.

[0098] Step 706: Vector knowledge base search.

[0099] In this step, the list of failed objects is input into the preset vector knowledge base, and document fragments related to the failed objects are retrieved.

[0100] The vector knowledge base can be obtained through the following methods: Obtain a large amount of Kubernetes cluster operation and maintenance documentation, including self-built documents, official documents, and selected technical documents. These documents contain detailed descriptions of various Pod issues and solutions. Preprocess the collected documents, including removing irrelevant information, standardizing the text format, and performing word segmentation. Convert each document fragment into structured text, ensuring that each fragment independently describes a problem and its solution. Use a sentence embedding model to convert each document fragment into a high-dimensional vector. Store these vectors in an efficient vector search engine to build a vector knowledge base.

[0101] Step 707: Recall the document.

[0102] In this step, a document segment corresponding to the failure type of the failed object list is retrieved from the vector knowledge base. If it is determined that a document segment corresponding to the failure type of the failed object list exists in the vector knowledge base, the document segment is recalled.

[0103] Step 708: Not found.

[0104] The document fragment corresponding to the fault type of the failed object list is retrieved in the vector knowledge base, and when it is determined that the document fragment corresponding to the fault type of the failed object list does not exist in the vector knowledge base, it is displayed that it is not found.

[0105] Step 709: Set prompt words.

[0106] The prompt word can include a list of failed objects, a container group identifier, and preset language processing requirements. For example, the list of failed objects can be {answer_docs}, the container group identifier can be {name}, the failure type can be {error}, and the preset language processing requirements can be "As a professional K8S cluster operation and maintenance expert, please aggregate and integrate the document fragments provided by the vector knowledge base and answer the solution corresponding to the list of failed objects."

[0107] Step 7010: Input model.

[0108] In this step, the prompt word is input into the large language model.

[0109] Step 7011: Output the diagnosis conclusion and solution.

[0110] In this step, if the recalled document is displayed in step 707, a diagnosis conclusion and solution are provided based on the document fragment in the vector knowledge base. If the not found document is displayed in step 707, a diagnosis conclusion and solution are provided based on the self-generated knowledge.

[0111] The above technical solution can quickly and accurately locate the target container group with a fault, and can also quickly and accurately determine the fault handling prompt data corresponding to the fault information of the target container group, thereby effectively improving the reliability and efficiency of operation and maintenance.

[0112] Figure 8 is a block diagram of a data processing device according to an exemplary embodiment, which is applied to a container orchestration system. The container orchestration system includes one or more container groups, such as Figure 8 As shown, the apparatus 800 includes: A first acquisition module 801 is configured to acquire the current running status of each of the one or more container groups; A first determining module 802 is configured to determine at least one target container group having a fault among the one or more container groups based on the current running status of each container group; A second acquisition module 803 is configured to acquire fault information of each target container group; The second determining module 804 is configured to determine, for each target container group, fault handling prompt data corresponding to the fault information using preset relationship data based on the fault information, where the preset relationship data includes preset handling prompt information for different container group identifiers under multiple fault types.

[0113] Optionally, the container group includes one or more containers, the current running state includes a waiting-to-be-scheduled state, a normal running state, and a non-running state, and the first determining module 802 is configured to: For each container group, if it is determined that the current operating state is a non-operating state, the container group is used as the target container group; and if it is determined that the current operating state is a waiting-to-be-scheduled state or a normal operating state, the container group is used as a standby container group; Obtaining the container status of each container in the standby container group; Determine whether the standby container group belongs to the target container group according to the container status of each container in the standby container group.

[0114] Optionally, the container status includes a creation process status, an error status, and an unready status. The first determining module 802 is further configured to: When it is determined that the container status of at least one container in the standby container group is the creation process state or the unready state, obtaining an event record of the standby container group within a preset time; When it is determined that the event record includes a first error identifier and a first error cause, using the standby container group as the target container group; When it is determined that the container status of at least one container in the standby container group is the error status, the standby container group is used as the target container group.

[0115] Optionally, the container group includes one or more containers, and the container status includes a creation process status, an error status, and an unready status. The second acquisition module 803 is configured to: If at least one container in the target container group is in the error state, error information of the standby container group is obtained, the error information including a second error identifier and a second error cause, and the target identifier of the target container group, the second error identifier, and the second error cause in the error information are used as fault information of the target container group; If no container in the target container group has a container status in the error state, and if it is determined that the event record of the target container group contains a first error identifier and a first error cause, the target identifier of the target container group, the first error identifier, and the first error cause in the event record are used as fault information of the target container group.

[0116] Optionally, the fault information includes a target identifier, a target error identifier, and a target error cause of the target container group; the fault type includes an error identifier field and an error cause field; and the second determining module 804 is configured to: When it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, determining a target fault type of the target container group according to the target error identifier and the target error cause; Target processing prompt information corresponding to the target fault type is determined from the preset relationship data, and the target processing prompt information is used as the fault processing prompt data of the target container group.

[0117] Optionally, the fault handling prompt data includes one or more target operation and maintenance information segments, and the device further includes: The third acquisition module 805 is used to input the one or more target operation and maintenance information fragments, the container group identifier, the fault type and the preset language processing requirement information into a preset language processing model to obtain the target operation and maintenance prompt data output by the language processing model.

[0118] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0119] Figure 9 FIG. 1 is a block diagram of an electronic device 900 according to an exemplary embodiment. Figure 9 As shown, the electronic device 900 may include: a first processor 901 , a first memory 902 , and one or more of a multimedia component 903 , a first input / output interface 904 , and a first communication component 905 .

[0120] The first processor 901 is used to control the overall operation of the electronic device 900 to complete all or part of the steps in the above-mentioned data processing method. The first memory 902 is used to store various types of data to support the operation of the electronic device 900. This data may include, for example, instructions for any application or method operating on the electronic device 900, as well as application-related data such as contact information, sent and received messages, images, audio, video, etc. The first memory 902 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The multimedia component 903 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the first memory 902 or sent through the first communication component 905. The audio component also includes at least one speaker for outputting audio signals. The first input / output interface 904 provides an interface between the first processor 901 and other interface modules. The above-mentioned other interface modules may be a keyboard, a mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The first communication component 905 is used for wired or wireless communication between the electronic device 900 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more thereof, so the corresponding first communication component 905 may include: a Wi-Fi module, a Bluetooth module, an NFC module.

[0121] In an exemplary embodiment, the electronic device 900 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-mentioned data processing method.

[0122] In another exemplary embodiment, a computer-readable storage medium including program instructions is further provided. When the program instructions are executed by a processor, the steps of the above-described data processing method are implemented. For example, the computer-readable storage medium may be the above-described first memory 902 including the program instructions. The above-described program instructions may be executed by the first processor 901 of the electronic device 900 to implement the above-described data processing method.

[0123] In another exemplary embodiment, a computer program product is further provided. The computer program product includes a computer program that can be executed by a processor. When the computer program is executed by the processor, the steps of the above data processing method are implemented.

[0124] Figure 10 1 is a block diagram of an electronic device 1000 according to an exemplary embodiment. For example, the electronic device 1000 can be provided as a server. Figure 10 The electronic device 1000 includes a second processor 1022, which may be one or more, and a second memory 1032 for storing a computer program executable by the second processor 1022. The computer program stored in the second memory 1032 may include one or more modules, each corresponding to a set of instructions. In addition, the second processor 1022 may be configured to execute the computer program to perform the above-mentioned data processing method.

[0125] In addition, the electronic device 1000 may further include a power supply component 1026 and a second communication component 1050. The power supply component 1026 may be configured to perform power management of the electronic device 1000, and the second communication component 1050 may be configured to implement communication of the electronic device 1000, for example, wired or wireless communication. In addition, the electronic device 1000 may further include a second input / output interface 1058. The electronic device 1000 may operate based on an operating system stored in the second memory 1032, such as Windows Server 2003. TM , Mac OS X TM , Unix TM , Linux TM etc.

[0126] In another exemplary embodiment, a computer-readable storage medium including program instructions is further provided. When the program instructions are executed by a processor, the steps of the above-described data processing method are implemented. For example, the computer-readable storage medium may be the second memory 1032 including the program instructions. The program instructions may be executed by the second processor 1022 of the electronic device 1000 to implement the above-described data processing method.

[0127] In another exemplary embodiment, a computer program product is further provided. The computer program product includes a computer program that can be executed by a processor. When the computer program is executed by the processor, the steps of the above data processing method are implemented.

[0128] The preferred embodiments of the present disclosure are described in detail above in conjunction with the accompanying drawings. However, the present disclosure is not limited to the specific details of the above embodiments. Within the technical concept of the present disclosure, various simple modifications can be made to the technical solutions of the present disclosure, and these simple modifications all fall within the scope of protection of the present disclosure.

[0129] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, the present disclosure will not further describe various possible combinations.

[0130] In addition, the various embodiments of the present disclosure may be arbitrarily combined, and as long as they do not violate the concept of the present disclosure, they should also be regarded as the contents disclosed by the present disclosure.

Claims

1. A data processing method, characterized in that: Applied to a container orchestration system, the container orchestration system includes one or more container groups, and the method includes: Obtaining a current running status of each of the one or more container groups; Determine at least one target container group having a fault among the one or more container groups according to the current running status of each container group; Obtaining fault information of each target container group; For each target container group, fault processing prompt data corresponding to the fault information is determined according to the fault information through preset relationship data, where the preset relationship data includes preset processing prompt information of different container group identifiers under multiple fault types.

2. The data processing method according to claim 1, wherein: The container group includes one or more containers, the current running state includes a waiting-to-be-scheduled state, a normal running state, and a non-running state. Determining at least one target container group having a fault among the one or more container groups according to the current running state of each container group includes: For each container group, if it is determined that the current operating state is a non-operating state, the container group is used as the target container group; and if it is determined that the current operating state is a waiting-to-be-scheduled state or a normal operating state, the container group is used as a standby container group; Obtaining the container status of each container in the standby container group; Determine whether the standby container group belongs to the target container group according to the container status of each container in the standby container group.

3. The data processing method according to claim 2, characterized in that: The container status includes a creation process status, an error status, and an unready status. Determining whether the standby container group belongs to the target container group according to the container status of each container in the standby container group includes: If it is determined that at least one container in the standby container group is in the creation process state or the not ready state, obtaining an event record of the standby container group within a preset time; if it is determined that the event record includes a first error identifier and a first error cause, using the standby container group as the target container group; When it is determined that the container status of at least one container in the standby container group is the error status, the standby container group is used as the target container group.

4. The data processing method according to claim 1, wherein: The container group includes one or more containers, and the container status includes a creation process status, an error status, and an unready status. The acquiring fault information of each target container group includes: If at least one container in the target container group is in the error state, error information of the standby container group is obtained, the error information including a second error identifier and a second error cause, and the target identifier of the target container group, the second error identifier, and the second error cause in the error information are used as fault information of the target container group; If no container in the target container group has a container status in the error state, and if it is determined that the event record of the target container group contains a first error identifier and a first error cause, the target identifier of the target container group, the first error identifier, and the first error cause in the event record are used as fault information of the target container group.

5. The data processing method according to claim 1, wherein: The fault information includes a target identifier, a target error identifier, and a target error cause of the target container group; the fault type includes an error identifier field and an error cause field; and determining fault handling prompt data corresponding to the fault information through preset relationship data based on the fault information includes: When it is determined that the target identifier in the fault information is consistent with the target container group identifier in the preset relationship data, determining a target fault type of the target container group according to the target error identifier and the target error cause; Target processing prompt information corresponding to the target fault type is determined from the preset relationship data, and the target processing prompt information is used as the fault processing prompt data of the target container group.

6. The data processing method according to claim 1, wherein: The preset processing prompt information includes multiple operation and maintenance information segments, and obtaining the preset relationship data includes: Acquire multiple operation and maintenance document data of the container orchestration system, where the operation and maintenance document data is used to describe a fault type and processing prompt information corresponding to the fault type; Inputting the plurality of operation and maintenance document data into a preset text embedding model to obtain a plurality of operation and maintenance information segments corresponding to each fault type output by the text embedding model; The multiple operation and maintenance information segments corresponding to each fault type are used as the preset relationship data.

7. The data processing method according to claim 1, wherein: The fault handling prompt data includes one or more target operation and maintenance information segments, and the method further includes: The one or more target operation and maintenance information segments, the container group identifier, the fault type and preset language processing requirement information are input into a preset language processing model to obtain target operation and maintenance prompt data output by the language processing model.

8. A data processing device, characterized in that: Applied to a container orchestration system, the container orchestration system includes one or more container groups, and the apparatus includes: A first acquisition module is configured to acquire a current running status of each of the one or more container groups; A first determining module is configured to determine at least one target container group having a fault among the one or more container groups based on a current operating status of each container group; A second acquisition module is configured to acquire fault information of each target container group; A second determining module is configured to determine, for each target container group, fault handling prompt data corresponding to the fault information using preset relationship data based on the fault information, wherein the preset relationship data includes preset handling prompt information for different container group identifiers under multiple fault types.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

10. An electronic device, characterized in that: include: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1 to 8.

Images