Agent-based user side container log acquisition method and system in public cloud scene

Abstract

The invention relates to the technical field of cloud native, and discloses an agent-based user side container log acquisition and system in a public cloud scene, a user sends a log query request to an apiserver component, and the apiserver component converts the log query request into a to-be-processed log task. According to the method, the agent component reports healthy heartbeat to the apiserver component regularly, the apiserver component writes a log task to be processed into response information of the heartbeat and sends the response information to the agent component, after receiving the log task, the agent component actively establishes connection with the apiserver component, checks container log information and returns the container log information to the apiserver component, and the apiserver component returns a result to a user after receiving the result. Two-way communication between the PaaS control plane and the user network is established in an agent mode, and the problems of resource waste and safety of a traditional double-network-card mode are solved.

Description

Technical Field

[0001] The present invention relates to the field of cloud native technology, and in particular to an agent-based user-side container log acquisition method and system in a public cloud scenario. Background Art

[0002] In traditional public cloud scenarios, obtaining user-side container logs usually uses dual network cards, such as Figure 1 As shown in the figure, since the control plane network and the user private network are naturally isolated, they cannot communicate. If the management side and the user side need to be able to communicate, the network card of the management side needs to be configured on the cloud server on the user side to achieve access between the management side and the user side. However, this method will consume a large amount of network card resources, resulting in resource waste. At the same time, if the container on the user side escapes, it will log in to the control plane, causing security issues. Summary of the invention

[0003] In view of this, the present invention provides an agent-based user-side container log acquisition method and system in a public cloud scenario to solve the resource waste and security problems of the traditional dual network card mode.

[0004] In a first aspect, the present invention provides an agent-based user-side container log acquisition method in a public cloud scenario, the method being applied to a PaaS control plane, the method comprising:

[0005] Receive a query log request sent by a user, and convert the query log request into a log task to be processed;

[0006] Regularly receive the health heartbeat reported by the agent component, where the agent component is deployed in the user's cloud server;

[0007] Write the log task to be processed into the response information of the health heartbeat, and send the response information to the agent component;

[0008] Establish a websocket connection with the agent component and receive the container log information returned by the agent component. The agent component obtains the container log information by viewing the log file of the container, and the container is deployed in the user's cloud server;

[0009] The container log information is returned to the user end.

[0010] In an optional embodiment, the method further includes:

[0011] Determine whether the user terminal initiates a request to access the preset apiserver component based on the log tasks to be processed;

[0012] When a request is not made to the preset apiserver component, the preset apiserver component is used as a reverse proxy component.

[0013] In an optional implementation, the preset apiserver component is a component that receives a health heartbeat reported by an agent component.

[0014] In an optional implementation, the apiserver component is deployed in multiple copies.

[0015] In an optional implementation, the log task to be processed carries a unique request identifier.

[0016] In a second aspect, the present invention provides an agent-based user-side container log acquisition method in a public cloud scenario, the method being applied to a user cloud server, the method comprising:

[0017] Regularly report health heartbeats to the apiserver component, which is deployed in a containerized manner on the PaaS control plane;

[0018] After receiving the pending log task, it actively establishes a websocket connection with the apiserver component. The pending log task is included in the response information sent by the apiserver component.

[0019] View the container's log files and obtain container log information;

[0020] Return the container log information to the apiserver component.

[0021] In a third aspect, the present invention provides an agent-based user-side container log acquisition method in a public cloud scenario, the method being applied to a user side, and the method comprising:

[0022] Send a query log request to the apiserver component;

[0023] Receives container log information returned by the apiserver component.

[0024] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario. Based on the existing vpce network mode, an agent is used to establish two-way communication between the PaaS control plane and the user network, so that users can obtain container logs in real time on the control plane, which solves the resource waste and security problems of the traditional dual-network card mode, breaks through the bottleneck of one-way communication in the vpce network mode, and realizes two-way communication and container log acquisition.

[0025] In a fourth aspect, the present invention provides an agent-based user-side container log acquisition system in a public cloud scenario, the system comprising: a PaaS control plane, a user cloud server and a user terminal, wherein:

[0026] The PaaS control plane receives a query log request sent by a user terminal, and converts the query log request into a log task to be processed;

[0027] The PaaS control plane periodically receives the health heartbeat reported by the agent component, and the agent component is deployed in the user cloud server;

[0028] The PaaS control plane writes the log task to be processed into the response information of the health heartbeat, and sends the response information to the agent component;

[0029] The PaaS control plane establishes a websocket connection with the agent component and receives the container log information returned by the agent component. The agent component obtains the container log information by viewing the log file of the container. The container is deployed in the user's cloud server.

[0030] The PaaS control plane returns the container log information to the user end;

[0031] The user cloud server periodically reports health heartbeats to the apiserver component, and the apiserver component is deployed on the PaaS control plane in a containerized manner;

[0032] After receiving the log task to be processed, the user cloud server actively establishes a websocket connection with the apiserver component. The log task to be processed is included in the response information sent by the apiserver component.

[0033] The user cloud server checks the log file of the container and obtains the container log information;

[0034] The user cloud server returns the container log information to the apiserver component;

[0035] The user terminal sends a query log request to the apiserver component;

[0036] The user end receives the container log information returned by the apiserver component.

[0037] The present invention provides an agent-based user-side container log acquisition system in a public cloud scenario. Based on the existing vpce network mode, an agent is used to establish two-way communication between the PaaS control plane and the user network, so that users can obtain container logs in real time on the control plane, which solves the resource waste and security problems of the traditional dual-network card mode, breaks through the bottleneck of one-way communication in the vpce network mode, and realizes two-way communication and container log acquisition.

[0038] In a fifth aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the agent-based user-side container log acquisition method in the public cloud scenario of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0039] In a sixth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the agent-based user-side container log acquisition method in a public cloud scenario of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0041] Figure 1 is a schematic diagram of a communication method between a user private network and a control plane network according to an embodiment of the present invention;

[0042] Figure 2 is a schematic diagram of another communication method between a user private network and a control plane network according to an embodiment of the present invention;

[0043] Figure 3 It is a flowchart of an agent-based user-side container log acquisition method in a public cloud scenario according to an embodiment of the present invention;

[0044] Figure 4 is another flow chart of a method for obtaining container logs on the user side based on an agent in a public cloud scenario according to an embodiment of the present invention;

[0045] Figure 5 is another flow chart of a method for obtaining container logs on the user side based on an agent in a public cloud scenario according to an embodiment of the present invention;

[0046] Figure 6 is another flow chart of a method for obtaining container logs on the user side based on an agent in a public cloud scenario according to an embodiment of the present invention;

[0047] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0049] like Figure 2 As shown, based on the existing vpce technology, one-way communication between the user's private network and the control plane network can be achieved, but this one-way communication can only perform some simple operations and cannot meet the use requirements of public cloud products. How to enable users to access business containers on the control plane and obtain relevant information such as container logs based on the existing solution is very important. To this end, an embodiment of the present invention provides an agent-based user-side container log acquisition method in a public cloud scenario, which uses an agent to establish two-way communication between the PaaS control plane and the user network, solves the resource waste and security problems of the traditional dual network card mode, breaks through the bottleneck of one-way communication in the vpce network mode, and realizes two-way communication and obtains container logs.

[0050] like Figure 3 The figure shows an application scenario diagram of an embodiment of the present invention. The user at the user end sends a request to the apiserver component deployed on the PaaS control plane. The apiserver component receives the user request and converts it into a log task to be processed. The agent component deployed on the user's cloud server will periodically report a healthy heartbeat to the apiserver component. The apiserver component writes the log task to be processed into the heartbeat response information and sends it to the agent component. After receiving the log task, the agent component actively establishes a websocket connection with the apiserver component, and continuously checks the container log information and returns it to the apiserver component. After receiving the result, the apiserver component returns it to the user. Among them, the apiserver component is a component of the PaaS control plane, which processes user requests and interacts with the agent component. The agent component is a component on the user side, responsible for managing the life cycle of the container.

[0051] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario, which is applied to the PaaS control plane. Figure 3 and Figure 4 As shown, the agent-based user-side container log acquisition method in the public cloud scenario includes the following steps:

[0052] Step S11, receiving a log query request sent by a user terminal, and converting the log query request into a log task to be processed.

[0053] Specifically, the user on the user side sends a query log request to the apiserver component deployed on the PaaS control plane. After receiving the user request, the apiserver component converts the query log request into a log task to be processed. The apiserver component is deployed on the PaaS control plane in a containerized manner, using a multi-copy deployment method to handle external user traffic. The apiserver component creates a request identifier as a unique identifier for each query log request, that is, each log task to be processed has a unique request identifier.

[0054] Step S12: regularly receiving the health heartbeat reported by the agent component, where the agent component is deployed in the user's cloud server.

[0055] Specifically, the agent component deployed on the user's cloud server will periodically report the container health heartbeat to the apiserver component. The agent component is deployed on the user's cloud server as a bridge for the user's business container to interact with the apiserver. The agent component is responsible for managing the container lifecycle and reporting the container health status.

[0056] Step S13, write the log task to be processed into the response information of the healthy heartbeat, and send the response information to the agent component.

[0057] Specifically, the apiserver component writes the pending log task into the heartbeat response information and sends the response information to the agent component.

[0058] Step S14, establish a websocket connection with the agent component, receive the container log information returned by the agent component, the agent component obtains the container log information by viewing the log file of the container, and the container is deployed in the user's cloud server.

[0059] Specifically, the agent component obtains the pending log tasks sent by the apiserver through the heartbeat response information. After receiving the pending log tasks, the agent component actively establishes a websocket connection with the apiserver component. The agent component continuously checks the container's log files and obtains the container log information.

[0060] Step S15: Return the container log information to the user end.

[0061] Specifically, after the agent component obtains the container log information, it returns the container log information to the apiserver component. The apiserver component then returns the container log information to the user on the user side.

[0062] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario. The self-developed agent component establishes two-way communication between the control plane and the user's private network by regularly reporting heartbeats, solving the problem of only one-way communication in the vpce mode. In the scenario of dual network cards, users can quickly access remote business containers on the control plane. The self-developed apiserver component ensures effective communication while being safer and more reliable. Users purchase public cloud container instances and can obtain container log information on the control plane on demand and dynamically without additional configuration, which is convenient and fast. Public cloud vendors can meet users' needs for accessing remote containers on the control plane without dual network cards, saving costs and improving product value and sales capabilities.

[0063] In an optional embodiment, the method further comprises the following steps:

[0064] Step S16, judging whether the user terminal initiates an access request to the preset apiserver component according to the log task to be processed.

[0065] Step S17, when the access request is not made to the preset apiserver component, the preset apiserver component is used as a reverse proxy component.

[0066] Specifically, the preset apiserver component is the component that receives the healthy heartbeat reported by the agent component. When a user requests to access apiserver component-1, and the agent component heartbeat is connected to apiserver component-2, apiserver component-2 will identify whether the pending request is in itself through the pending log task. If not, it will proxy to the corresponding apiserver component, that is, apiserver component-1.

[0067] In an optional implementation, the log task to be processed carries a unique request identifier.

[0068] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario. The method is applied to a user cloud server, such as Figure 3 and Figure 5 As shown, the agent-based user-side container log acquisition method in the public cloud scenario includes the following steps:

[0069] Step S21, regularly report the health heartbeat to the apiserver component, and the apiserver component is deployed in a containerized manner on the PaaS control plane.

[0070] Specifically, the agent component is responsible for managing the container lifecycle and reporting the container health status. The agent component will periodically report the container health heartbeat to the apiserver component.

[0071] Step S22, after receiving the log task to be processed, actively establish a websocket connection with the apiserver component, and the log task to be processed is included in the response information sent by the apiserver component.

[0072] Specifically, the agent component obtains the pending log tasks sent by the apiserver through the heartbeat response information. After receiving the pending log tasks, the agent component actively establishes a websocket connection with the apiserver component.

[0073] Step S23, check the log file of the container and obtain the container log information.

[0074] Specifically, the agent component obtains container log information by viewing the container's log file.

[0075] Step S24, returning the container log information to the apiserver component.

[0076] Specifically, after the agent component obtains the container log information, it returns the container log information to the apiserver component.

[0077] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario. The method is applied to the user side, such as Figure 3 and Figure 6 As shown, the agent-based user-side container log acquisition method in the public cloud scenario includes the following steps:

[0078] Step S31, sending a query log request to the apiserver component.

[0079] Specifically, when a user wants to obtain remote container logs, the user first sends a log query request to the apiserver component.

[0080] Step S32, receiving the container log information returned by the apiserver component.

[0081] Specifically, the self-developed agent component establishes two-way communication between the control plane and the user's private network by reporting heartbeats at regular intervals. After the agent component obtains the container log information, it returns the container log information to the apiserver component. The apiserver component then returns the container log information to the user on the user side.

[0082] The present invention provides an agent-based user-side container log acquisition method in a public cloud scenario. Based on the existing vpce network mode, an agent is used to establish two-way communication between the PaaS control plane and the user network, so that users can obtain container logs in real time on the control plane, which solves the resource waste and security problems of the traditional dual-network card mode, breaks through the bottleneck of one-way communication in the vpce network mode, and realizes two-way communication and container log acquisition.

[0083] like Figure 3 As shown, the present invention provides an agent-based user-side container log acquisition system in a public cloud scenario, and the system includes: a PaaS control plane, a user cloud server and a user terminal.

[0084] Among them, the PaaS control plane receives the query log request sent by the user end and converts the query log request into a log task to be processed. The PaaS control plane periodically receives the health heartbeat reported by the agent component, and the agent component is deployed in the user cloud server. The PaaS control plane writes the log task to be processed into the response information of the health heartbeat and sends the response information to the agent component. The PaaS control plane establishes a websocket connection with the agent component and receives the container log information returned by the agent component. The agent component obtains the container log information by viewing the log file of the container. The container is deployed in the user cloud server. The PaaS control plane returns the container log information to the user end. The user cloud server periodically reports the health heartbeat to the apiserver component, and the apiserver component is deployed in a containerized manner on the PaaS control plane. After receiving the log task to be processed, the user cloud server actively establishes a websocket connection with the apiserver component, and the log task to be processed is included in the response information sent by the apiserver component. The user cloud server views the log file of the container and obtains the container log information. The user cloud server returns the container log information to the apiserver component. The user end sends a query log request to the apiserver component. The client receives the container log information returned by the apiserver component.

[0085] Specifically, the user sends a query log request to the apiserver component, which receives the query log request and converts it into a log task to be processed. The agent component periodically reports a healthy heartbeat to the apiserver component, and the apiserver component writes the log task to be processed into the heartbeat response information and sends it to the agent component. After receiving the log task, the agent component actively establishes a websocket connection with the apiserver component, and continuously checks the container log information and returns it to the apiserver component. After receiving the result, the apiserver component returns it to the user.

[0086] The present invention provides an agent-based user-side container log acquisition system in a public cloud scenario. Based on the existing vpce network mode, an agent is used to establish two-way communication between the PaaS control plane and the user network, so that users can obtain container logs in real time on the control plane, which solves the resource waste and security problems of the traditional dual-network card mode, breaks through the bottleneck of one-way communication in the vpce network mode, and realizes two-way communication and container log acquisition.

[0087] The embodiment of the present invention also provides a computer device having the above Figure 3 The agent-based user-side container log acquisition system in the public cloud scenario is shown.

[0088] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0089] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0090] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0091] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0092] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0093] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 7 The example of connecting through bus is taken in the following.

[0094] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0095] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0096] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for obtaining user-side container logs based on an agent in a public cloud scenario, characterized in that: The method is applied to the PaaS control plane, and the method includes: Receive a query log request sent by a user, and convert the query log request into a log task to be processed; Regularly receive the health heartbeat reported by the agent component, where the agent component is deployed in the user's cloud server; Write the log task to be processed into the response information of the health heartbeat, and send the response information to the agent component; Establish a websocket connection with the agent component and receive the container log information returned by the agent component. The agent component obtains the container log information by viewing the log file of the container, and the container is deployed in the user's cloud server; The container log information is returned to the user end.

2. According to the agent-based user-side container log acquisition method in the public cloud scenario of claim 1, it is characterized in that: The method further comprises: Determine whether the user terminal initiates a request to access the preset apiserver component based on the log tasks to be processed; When a request is not made to the preset apiserver component, the preset apiserver component is used as a reverse proxy component.

3. The agent-based user-side container log acquisition method in a public cloud scenario according to claim 2 is characterized in that: The preset apiserver component is a component that receives the health heartbeat reported by the agent component.

4. The agent-based user-side container log acquisition method in a public cloud scenario according to claim 2 is characterized in that: The apiserver component is deployed in multiple copies.

5. According to the agent-based user-side container log acquisition method in the public cloud scenario of claim 1, it is characterized in that: Pending log tasks carry a unique request ID.

6. A method for obtaining user-side container logs based on an agent in a public cloud scenario, characterized in that: The method is applied to a user cloud server, and the method comprises: Regularly report health heartbeats to the apiserver component, which is deployed in a containerized manner on the PaaS control plane; After receiving the pending log task, it actively establishes a websocket connection with the apiserver component. The pending log task is included in the response information sent by the apiserver component. View the container's log files and obtain container log information; Return the container log information to the apiserver component.

7. A method for obtaining user-side container logs based on an agent in a public cloud scenario, characterized in that: The method is applied to a user terminal, and the method comprises: Send a query log request to the apiserver component; Receives container log information returned by the apiserver component.

8. An agent-based user-side container log acquisition system in a public cloud scenario, characterized in that: The system includes: a PaaS control plane, a user cloud server and a user terminal, wherein: The PaaS control plane receives a query log request sent by a user terminal, and converts the query log request into a log task to be processed; The PaaS control plane periodically receives the health heartbeat reported by the agent component, and the agent component is deployed in the user cloud server; The PaaS control plane writes the log task to be processed into the response information of the health heartbeat, and sends the response information to the agent component; The PaaS control plane establishes a websocket connection with the agent component and receives the container log information returned by the agent component. The agent component obtains the container log information by viewing the log file of the container. The container is deployed in the user's cloud server. The PaaS control plane returns the container log information to the user end; The user cloud server periodically reports health heartbeats to the apiserver component, and the apiserver component is deployed on the PaaS control plane in a containerized manner; After receiving the log task to be processed, the user cloud server actively establishes a websocket connection with the apiserver component. The log task to be processed is included in the response information sent by the apiserver component. The user cloud server checks the log file of the container and obtains the container log information; The user cloud server returns the container log information to the apiserver component; The user terminal sends a query log request to the apiserver component; The user end receives the container log information returned by the apiserver component.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the agent-based user-side container log acquisition method in the public cloud scenario according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the agent-based user-side container log acquisition method in a public cloud scenario according to any one of claims 1 to 7.

Images