CN113391979A - Processing method, equipment and system for monitoring data display and storage medium - Google Patents
Processing method, equipment and system for monitoring data display and storage medium Download PDFInfo
- Publication number
- CN113391979A CN113391979A CN202110688848.8A CN202110688848A CN113391979A CN 113391979 A CN113391979 A CN 113391979A CN 202110688848 A CN202110688848 A CN 202110688848A CN 113391979 A CN113391979 A CN 113391979A
- Authority
- CN
- China
- Prior art keywords
- server
- index data
- monitoring index
- monitoring
- subscription
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The application provides a processing method, equipment, a system and a storage medium for monitoring data display, wherein the method is applied to a server and comprises the following steps: receiving a first subscription request sent by a subscription end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, the monitoring index data is obtained by monitoring the service operation state of a service system, and the subscription end is in communication connection with a server end in a long connection mode; sending a second subscription request to the memory server, wherein the second subscription request comprises the identifier of the server and the type of the monitoring index data, and the server is in communication connection with the memory server; receiving monitoring index data pushed by a memory server; and pushing the monitoring index data to a subscription end. The method realizes the synchronization of the acquisition and the display of the monitoring index data and displays the effect of the monitoring index data in real time.
Description
Technical Field
The present application relates to computer technologies, and in particular, to a method, an apparatus, a system, and a storage medium for processing a monitoring data display.
Background
The business system is capable of providing business services. In order to ensure the normal operation of the service and to know the service operation status of the service system in real time, the service system needs to be monitored.
At present, monitoring data are regularly acquired from a service system through an acquisition end and stored in an application server or a database server, a client or a browser regularly inquires the application server or the database server and displays the data in a monitoring interface of the client or the browser, and each inquiry is a refresh of the current monitoring data. Therefore, the user can know the service operation state of the service system in real time.
However, the manner of regularly querying the monitoring data and refreshing the monitoring data in the monitoring interface may cause delay in displaying the monitoring data, and cannot ensure synchronization between monitoring data acquisition and monitoring data display.
Disclosure of Invention
The application provides a processing method, equipment and system for monitoring data display and a storage medium, which are used for solving the problems that the display of monitoring data is delayed and the synchronization between the monitoring data acquisition and the monitoring data display cannot be ensured.
In a first aspect, the present application provides a processing method for monitoring data display, which is applied to a server, and the method includes: receiving a first subscription request sent by a subscription end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, the monitoring index data is obtained by monitoring the service operation condition of a service system, and the subscription end is in communication connection with the service end in a long connection mode; sending a second subscription request to a memory server, wherein the second subscription request comprises the identifier of the server and the type of the monitoring index data, and the server is in communication connection with the memory server; receiving monitoring index data pushed by the memory server; and pushing the monitoring index data to a subscription end.
In one possible design, the method further includes: if receiving a query request of monitoring index data sent by the subscriber, forwarding the query request of the monitoring index data to a database server; receiving a query result, wherein the query result comprises the monitoring index data; and pushing the monitoring index data to the subscription terminal.
In one possible design, the method further includes: receiving a long connection request sent by the subscription terminal; determining a target working node in a plurality of working nodes, wherein the server comprises the plurality of working nodes; and sending the connection request to the target working node, wherein the target working node is used for establishing communication connection with the subscription terminal in a long connection mode according to the connection request, receiving the first subscription request and processing the first subscription request.
In a second aspect, the present application provides a processing method for monitoring data display, applied to an acquisition end, the method including: receiving monitoring index data pushed by a service system, wherein the service system is in communication connection with the acquisition end, and the monitoring index data is obtained by monitoring the service operation condition of the service system; and sending the monitoring index data to a database server and/or a memory server, wherein the acquisition end is in communication connection with the database server and/or the memory server.
In one possible design, the method further includes: determining a target working node in a plurality of working nodes, wherein the acquisition end comprises the plurality of working nodes; the target working node is used for receiving the monitoring index data pushed by the service system, preprocessing the monitoring index data and sending the preprocessed monitoring index data to a database server and/or a memory server.
In a third aspect, the present application provides a server, comprising: the receiving module is used for receiving a first subscription request sent by a subscription end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, the monitoring index data is obtained by monitoring the service operation state of a service system, and the subscription end is in communication connection with the server in a long connection mode; the sending module is used for sending a second subscription request to a memory server, wherein the second subscription request comprises the identifier of the server and the type of the monitoring index data, and the server is in communication connection with the memory server; the receiving module is further configured to receive monitoring index data pushed by the memory server; the sending module is further configured to push the monitoring index data to a subscriber.
In a fourth aspect, the present application provides an acquisition device comprising: the receiving module is used for receiving monitoring index data pushed by a service system, the service system is in communication connection with the acquisition equipment, and the monitoring index data is obtained by monitoring the service running state of the service system; and the transmitting module is used for transmitting the monitoring index data to a database server and/or a memory server, and the acquisition equipment is in communication connection with the database server and/or the memory server.
In a fifth aspect, the present application provides a processing system for monitoring data presentation, comprising: the acquisition equipment is respectively in communication connection with the service system and the memory server and is used for executing the method of the first aspect; the memory server is in communication connection with the server and is used for receiving the monitoring index data pushed by the service system and pushing the monitoring index data to the server; a server connected with at least one subscriber terminal for executing the method of the second aspect; and the at least one subscription end is in communication connection with the server in a long connection mode and is used for receiving the monitoring index data pushed by the server and updating the currently displayed monitoring index data according to the monitoring index data.
In a sixth aspect, the present application provides a computer-readable storage medium having stored thereon computer-executable instructions for implementing the method according to the first or second aspect when executed by a processor.
In a seventh aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the first or second aspect.
According to the processing method, the processing equipment, the processing system and the storage medium for displaying the monitoring data, the monitoring index data sent by the acquisition end is pushed to the server end through the memory database, and the received monitoring index data is pushed to the subscription end through the server end, so that the synchronization of the acquisition and the display of the monitoring index data is realized, and the effect of displaying the monitoring index data in real time is achieved. In addition, the service system pushes the monitoring index data to the acquisition end, so that the problem that the acquisition end actively acquires the monitoring index data to the service system and certain pressure is caused to the service system in the prior art is solved. In addition, the subscription end is in long connection with the server end, so that the server end can be ensured to push the monitoring index data to the subscription end in real time.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a prior art architecture diagram of a processing system for monitoring data presentation;
FIG. 2 is an architecture diagram of a processing system for monitoring data presentations provided by an embodiment of the present application;
fig. 3 is a first interaction diagram of a processing method for monitoring data presentation according to an embodiment of the present application;
fig. 4 is an architecture diagram of a server according to an embodiment of the present application;
fig. 5 is an architecture diagram of an acquisition apparatus provided in an embodiment of the present application;
FIG. 6 is an architecture diagram of another processing system for monitoring data presentation provided by embodiments of the present application;
fig. 7 is an interaction diagram ii of a processing method for monitoring data presentation according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an acquisition device provided in an embodiment of the present application.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
FIG. 1 is a diagram of a prior art processing system for monitoring data presentation. As shown in fig. 1, the system includes a terminal device 11, a database 12, a collection end 13 and a service system 14; the terminal device 11 may be a smart phone, a desktop computer, a notebook, an Ipad, or the like, and a client or a browser may be installed on the terminal device, where a monitoring interface is displayed on the client or the browser for displaying monitoring index data. The collection end 13 may be a probe collection tool. The acquisition end 13 and the client, or the acquisition end 13 and the browser may be understood as a monitoring system.
The acquisition terminal 13 monitors the service operation status of the service system 14 to obtain monitoring index data, and persistently stores the monitoring index data in the database, and the client or the browser acquires the monitoring index data from the database in a timing query manner to refresh the monitoring index data. The timing query mode can cause the asynchronous acquisition and display of the monitoring index data, and the real-time display of the monitoring index data cannot be ensured. In addition, the collection end 13 actively collects monitoring index data for the service system 14, which may cause a certain pressure on the service system 14.
In order to solve the technical problems, the application provides the following technical concepts: the monitoring index data collected by the collection end is actively pushed to the Server end by adopting a publish/subscribe message communication mode of a Remote Dictionary service (Redis) database, and the monitoring index data can be further actively pushed to the subscriber end by adopting the publish/subscribe message communication mode between the Server end and the subscriber end.
Fig. 2 is an architecture diagram of a processing system for monitoring data presentation according to an embodiment of the present application. As shown in fig. 2, the system includes: the system comprises at least one subscription end 21, a server end 22, a memory server 23 and a collection end 24, wherein the at least one subscription end 21, the server end 22, the memory server 23 and the collection end 24 are sequentially in communication connection, and the collection end 24 is further connected with at least one service system 25.
At least one of the subscribers 21 may be a terminal device such as a smart phone, a desktop computer, a notebook, an Ipad, etc., a client or a browser may be installed on the subscriber 21, and a monitoring interface is displayed on the client or the browser for displaying monitoring index data.
The server 22 is also called a server, and may be a single server or a server cluster including a plurality of servers.
A Remote Dictionary service (Redis) database is provided in the memory Server 23.
The collection end 24, also referred to as a collection device, may be a single server or a server cluster including a plurality of servers, and each server may be a probe collection tool. The acquisition end 24, the server end 22 and the client, or the acquisition end 24, the server end 22 and the browser may be understood as a monitoring system.
The following describes the technical solution of the present application and how to solve the above technical problem in a specific embodiment with reference to the system architecture diagram shown in fig. 2. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 3 is a first interaction diagram of a processing method for monitoring data display according to an embodiment of the present application. As shown in fig. 3, the method includes:
s301, the subscriber sends a long connection request to the server.
The subscription terminal is a terminal device which is to subscribe the monitoring index data push service to the server terminal. Before subscribing monitoring index data push service to the server, a long connection request needs to be sent to the server to establish long connection with the server.
Alternatively, the long connection may be a WebSocket long connection. WebSocket is a protocol for full duplex communication over a single TCP connection. WebSocket enables data exchange between the client and the server to be simpler, and allows the server to actively push data to the client. In a WebSocket Application Programming Interface (API), a client and a server only need to complete a handshake, and a persistent connection can be directly established between the client and the server, and bidirectional data transmission is performed.
S302, the server receives the long connection request and establishes long connection with the subscriber.
Specifically, the server receives a long connection request sent by the subscriber, authenticates the subscriber, and establishes a long connection with the subscriber after the authentication is successful.
S303, the subscriber sends a first subscription request to the server.
After the long connection between the subscription end and the server end is successfully established, the subscription end sends a first subscription request to the server end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, and the monitoring index data are monitoring data of the service operation condition of the service system. The Identifier of the subscriber is information uniquely identifying the subscriber, and may be a Universal Unique Identifier (UUID), taking a smart phone as an example.
For the subscriber, a button for subscribing the monitoring data push service may be displayed in a monitoring interface of the subscriber, and the subscriber may implement the subscription of the monitoring data push service by clicking the button for subscribing the monitoring data push service. The monitoring data pushing service is used for enabling the server to push monitoring index data to the subscriber.
In some scenarios, the business system may be a customer service center, and the monitoring index data may be a total number of current customer services, a number of complaint telephones received during the current day, a number of complaint telephones processed during the current day, and the like.
S304, the server receives the first subscription request and sends a second subscription request to the memory server.
And the server receives the first subscription request, processes the first subscription request, and returns a message of successful subscription to the subscriber, so that the server is successfully subscribed to the monitoring index data push service. And then, the server sends a second subscription request to the memory server, wherein the second subscription request comprises the identifier of the server and the type of the monitoring index data. And the memory server receives the second subscription request, processes the second subscription request and returns a successful subscription message to the server, so that the server subscribes the monitoring index data push service to the memory server.
The first subscription request may be understood as a trigger condition for the server to send the second subscription request to the memory server.
S305, the service system pushes monitoring index data to the acquisition end.
And S306, the acquisition end receives the monitoring index data pushed by the service system.
In this embodiment, a timing pushing task may be set for the service system, and the service system pushes the monitoring index data to the acquisition end at a timing according to the timing pushing task.
And S307, the acquisition end sends the monitoring index data to a memory server.
S308, the memory server pushes the monitoring index data to the server side.
In this embodiment, the server and the memory server perform data transmission through a publish-subscribe mechanism.
A publish-subscribe mechanism is a messaging paradigm in a software architecture where a sender of a message (called a publisher) does not send the message directly to a particular recipient (called a subscriber). But rather, the published messages are classified into different categories without knowing which subscribers, if any, may be present. Likewise, a subscriber may express interest in one or more categories, receiving only interesting messages, without knowing which publishers (if any) are present.
Specifically, the memory server is provided with a plurality of channels, each channel is used for receiving different types of data, the second subscription request may be understood as a request from the server to the memory server for establishing a connection with a target channel of the memory server, and the target channel of the memory server is used for receiving the monitoring index data. And then, the server monitors a target channel of the memory server. And the memory server receives the monitoring index data, sends the monitoring index data to a target channel, and pushes the monitoring index data to the subscriber terminal if the server terminal monitors the monitoring index data.
S309, the server side pushes the monitoring index data to the subscriber side.
And S310, the subscriber receives the monitoring index data pushed by the server, and updates the currently displayed monitoring index data according to the monitoring index data.
In this embodiment, the server and the subscriber also perform data transmission through a publish-subscribe mechanism. Specifically, the server receives a first subscription request sent by the terminal device, and returns a message of successful subscription to the terminal device, and the terminal device receives the message of successful subscription, thereby implementing successful subscription of the monitoring index data push service to the memory server, and thus, the terminal device becomes a subscriber.
Specifically, the server is provided with a plurality of channels, each channel is used for receiving different types of data, the first subscription request may be understood as a request from the terminal device to the server to establish a connection with a target channel of the server, and the target channel of the server is used for receiving monitoring index data. And then, the subscription side monitors the target channel of the service side. And the server receives the monitoring index data and sends the monitoring index data to a target channel of the server, and if the subscriber monitors the monitoring index data, the currently displayed monitoring index data is updated according to the monitoring index data.
In the embodiment, the monitoring index data sent by the acquisition end is pushed to the server end by the memory database, and the received monitoring index data is pushed to the subscription end by the server end, so that the synchronization of the acquisition and display of the monitoring index data is realized, and the effect of displaying the monitoring index data in real time is achieved. In addition, the service system pushes the monitoring index data to the acquisition end, so that the problem that the acquisition end actively acquires the monitoring index data to the service system and causes certain pressure on the service system in the prior art is solved, and the stability and the reliability of the service system can be improved. In addition, the subscription end is in long connection with the server end, so that the server end can be ensured to push the monitoring index data to the subscription end in real time.
On the basis of the above embodiment, the server and the acquisition end may adopt a micro-service PaaS platform to perform cluster deployment, specifically may be a K8S cluster. The following will describe the implementation process of the method of the embodiment of the present application, taking the K8S cluster as an example:
fig. 4 is an architecture diagram of a server according to an embodiment of the present application.
As shown in fig. 4, the server includes a master node 41 and a plurality of worker nodes 42; wherein, the host node 41 comprises an API Server component, a Schedule component, a Controller-Manager component and an Etcd component; each of the plurality of worker nodes 42 includes a kubel component, a kube-proxy component, and a plurality of pods, each of the plurality of pods including one or more containers.
The API Server component is used for receiving a long connection request sent by a subscriber, determining information (for example, the number of the Pods needing to be created) of the Pods which are in long connection with the subscriber according to the long connection request, and sending the information to the Schedule component, wherein the long connection request comprises an IP address of the subscriber;
and the Schedule component is used for determining a target working node in the plurality of working nodes according to the number of the Pod required to be created, and sending the information of the Pod which is in long connection with the subscription end to the API Server component.
And the API Server component is also used for sending the long connection request and the information of the Pod which is in long connection with the subscriber end to the target working node so as to create the Pod and operate the Pod on the target working node.
Specifically, the functions of each component in the target work node are as follows:
the kubbelet assembly is used for monitoring the operation information of the API Server assembly on the Pod on the working node corresponding to the kubbelet assembly, and the operation information comprises operations such as adding, deleting and the like;
and the kube-proxy component is used for determining a target Pod according to the long connection request and recording the mapping relation between the IP address of the subscriber end and the port address of the target Pod, wherein the target Pod comprises one or more pods.
The target Pod is used for monitoring a target channel of the memory server and sending a port address of the target Pod and monitoring index data to the kube-proxy component under the condition that the monitoring index data is monitored;
and the kube-proxy component is further used for determining the IP address of the subscription end according to the port address of the target Pod and the address mapping table, and sending the monitoring index data to the subscription end corresponding to the IP address of the subscription end.
For the functions of the Controller-Manager component and the Etcd component, reference may be made to the related end descriptions, which are not described herein again.
In this embodiment, the server is deployed as a K8S cluster architecture, and a Pod can be created in the server according to the number of the subscribers or the resources required by the monitoring data push service to implement the monitoring data push service, so that the number of pods is flexibly configured. In addition, when some Pod of the server fails, the task on the Pod can be transferred to other pods, so that the high availability of the monitoring index push service is ensured.
Fig. 5 is an architecture diagram of an acquisition apparatus provided in an embodiment of the present application.
As shown in fig. 5, the acquisition device includes a master node 51 and a plurality of worker nodes 52; the main node 51 comprises an API Server component, a Schedule component, a Controller-Manager component and an Etcd component; each of the plurality of worker nodes 52 includes a kubel component, a kube-proxy component, and a plurality of pods, each of the plurality of pods including one or more containers.
The API Server component is used for receiving a connection request sent by the service system, determining information (such as the number of the Pods needing to be created) of the Pods connected with the service system according to the connection request, and sending the information to the scheduler component, wherein the connection request comprises an IP address of the service system;
and the Schedule component is used for determining a target working node in the plurality of working nodes according to the number of the Pod required to be created, and sending the information of the Pod connected with the service system to the API Server component.
And the API Server component is also used for sending the connection request and the information of the Pod connected with the service system to the target working node so as to create the Pod and operate the Pod on the target working node.
Specifically, the functions of each component in the target work node are as follows:
the kubbelet component is used for monitoring the operation information of the API Server component on the pod on the working node corresponding to the kubbelet component, and the operation information comprises operations such as adding, deleting and the like;
and the kube-proxy component is used for determining a target Pod according to the connection request and recording the mapping relation between the IP address of the service system and the port address of the target Pod, wherein the target Pod comprises one or more pods.
The target Pod is used for receiving the monitoring index data pushed by the service system and sending the port address of the target Pod and the monitoring index data to the kube-proxy component;
and the kube-proxy component is also used for determining the IP address of the memory server according to the port address of the target Pod and the address mapping table, and sending the monitoring index data to the memory server.
In this embodiment, the acquisition device is deployed as a K8S cluster architecture, and a Pod can be created in the acquisition device according to the number of the service systems to implement that the service systems push monitoring data to the acquisition device, so that the number of pods is configured flexibly. In addition, when some of the Pod of the collection device fails, the task on the Pod can be transferred to other pods, so that the high availability of the monitoring index push service is ensured.
Based on the above embodiments, fig. 6 is an architecture diagram of another processing system for monitoring data presentation according to an embodiment of the present application. As shown in fig. 6, the system includes: the system comprises a subscription end 61, a service end 62, a memory server 63, a collection end 64 and a database server 65, wherein the subscription end 61, the service end 62, the memory database 63 and the collection end 64 are sequentially in communication connection, the collection end 64 is further connected with a service system 66, and the database server 65 is respectively connected with the collection end 64 and the service end 62.
For the subscription end 61, the service end 62, the memory server 63, and the collection end 64, reference may be made to the description of the embodiment shown in fig. 2, and details are not described here.
The acquisition end 64 also sends the monitoring index data to the database server 65, and stores the monitoring index data in the database server 65 in a persistent manner for the subscriber end 61 to query.
Embodiments of the present application are described below in conjunction with the system architecture diagram shown in fig. 6.
Fig. 7 is an interaction diagram two of a processing method for monitoring data display according to an embodiment of the present application. As shown in fig. 7, the method includes:
s701, the subscriber side sends a long connection request to the server side.
The specific implementation of step S701 may refer to the description of step S301, and is not described herein again.
S702, the server receives the long connection request and establishes long connection with the subscriber.
The specific implementation of step S702 may refer to the description of step S302, and is not described herein again.
S703, the subscription end sends a first subscription request to the server end.
The specific implementation of step S703 may refer to the description of step S303, and is not described herein again.
S704, the server receives the first subscription request and returns a message of successful subscription to the subscriber.
The specific implementation of step S704 may refer to the description of step S304, and is not described herein again.
S705, the service system pushes the monitoring index data to the acquisition end.
The specific implementation of step S705 may refer to the description of step S305, and is not described herein again.
And S706, the acquisition end receives the monitoring index data pushed by the service system.
The specific implementation of step S706 may refer to the description of step S306, and is not described herein again.
And S707, the acquisition end sends the monitoring index data to a database server.
In this embodiment, the acquisition end sends the monitoring index data to the database server to be persistently stored in the database server for the subscription end to query.
S708, the subscription side sends a query request of monitoring index data to the server side.
In some scenarios, the subscriber needs to count the monitoring index data of the current day or in a period of time, and then may send a query request for the monitoring index data of the current day or in a period of time to the server.
And S709, the server receives the query request of the monitoring index data sent by the subscriber and forwards the query request of the monitoring index data to the database server.
And S710, the database server queries data according to the query request and sends the queried monitoring index data to the server.
And S711, the server receives the queried monitoring index data and pushes the queried monitoring index data to the subscriber.
And S712, the subscriber receives the monitoring index data pushed by the server, and updates the currently displayed monitoring index data according to the monitoring index data.
As shown in the content introduction of the embodiment shown in fig. 3, the subscriber subscribes the monitoring data push service to the server, so that the server can send the queried monitoring index data to the target channel of the server, and the subscriber monitors the target channel of the server and updates the monitoring index data in the current monitoring interface in real time according to the monitored monitoring index data.
In the embodiment, the monitoring index data is persistently stored in the database server, so that the data query is conveniently performed by the subscriber, and the defects that the monitoring index data is pushed and completed by the memory database, the monitoring index data is not stored, and the query requirement of a user on the monitoring index data cannot be met are overcome. In addition, the server only needs to query the database server once, and the queried result can be sent to all the subscribing terminals, so that the problem that each subscribing terminal needs to query the monitoring index data from the database regularly to cause access pressure to the database server is solved.
On the basis of the above method embodiment, fig. 8 is a schematic structural diagram of a server provided in the embodiment of the present application. As shown in fig. 8, the server includes: a receiving module 81 and a transmitting module 82;
the receiving module 81 is configured to receive a first subscription request sent by a subscriber, where the first subscription request includes an identifier of the subscriber and a type of monitoring index data, the monitoring index data is data obtained by monitoring a service operation status of a service system, and the subscriber is in communication connection with the server in a long connection manner; a sending module 82, configured to send a second subscription request to a memory server, where the second subscription request includes an identifier of the server and a type of the monitoring index data; the receiving module 81 is further configured to receive monitoring index data pushed by the memory server; the sending module 82 is further configured to push the monitoring index data to a subscriber.
In a possible design, the sending module 82 is further configured to, if the receiving module 81 receives a query request of monitoring index data sent by the subscriber, forward the query request of monitoring index data to a database server; the receiving module 81 is further configured to receive a query result, where the query result includes the monitoring index data; the sending module 82 is further configured to push the monitoring index data to the subscribing terminal.
In another possible design, the server further includes: a determination module 83; the receiving module 81 is further configured to receive a long connection request sent by the subscriber; a determining module 83, configured to determine a target working node among a plurality of working nodes, where the server includes the plurality of working nodes; the sending module 82 is further configured to send the connection request to the target working node, where the target working node is configured to establish a communication connection with the subscribing terminal in a long connection manner according to the connection request, receive the first subscription request, and process the first subscription request.
On the basis of the above method embodiment, fig. 9 is a schematic structural diagram of the acquisition device provided in the embodiment of the present application. As shown in fig. 9, the acquisition apparatus includes: a receiving module 91 and a transmitting module 92;
the receiving module 91 is configured to receive monitoring index data pushed by a service system, where the monitoring index data is data obtained by monitoring a service operation status of the service system; a sending module 82, configured to send the monitoring index data to a database server and/or a memory server.
In one possible design, the acquisition device further comprises: a determination module 93; the determining module 93 is further configured to determine a target working node among a plurality of working nodes, where the collecting end includes the plurality of working nodes; the target working node is used for receiving the monitoring index data pushed by the service system, preprocessing the monitoring index data and sending the preprocessed monitoring index data to a database server and/or a memory server.
An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the processing method for monitoring data presentation provided in any embodiment of the present application corresponding to fig. 3 and fig. 7.
The computer readable storage medium may be, among others, ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
An embodiment of the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the processing method for monitoring data presentation provided in any embodiment of fig. 3 and fig. 7 of the present application is implemented.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (12)
1. A processing method for monitoring data display is applied to a server side, and the method comprises the following steps:
receiving a first subscription request sent by a subscription end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, the monitoring index data is obtained by monitoring the service operation condition of a service system, and the subscription end is in communication connection with the service end in a long connection mode;
sending a second subscription request to a memory server, wherein the second subscription request comprises the identifier of the server and the type of the monitoring index data;
receiving monitoring index data pushed by the memory server;
and pushing the monitoring index data to a subscription end.
2. The method of claim 1, further comprising:
if receiving a query request of monitoring index data sent by the subscriber, forwarding the query request of the monitoring index data to a database server;
receiving a query result, wherein the query result comprises the monitoring index data;
and pushing the monitoring index data to the subscription terminal.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
receiving a long connection request sent by the subscription terminal;
determining a target working node in a plurality of working nodes, wherein the server comprises the plurality of working nodes;
and sending the connection request to the target working node, wherein the target working node is used for establishing communication connection with the subscription terminal in a long connection mode according to the connection request, receiving the first subscription request and processing the first subscription request.
4. A processing method for monitoring data display is applied to an acquisition end, and comprises the following steps:
receiving monitoring index data pushed by a service system, wherein the monitoring index data is obtained by monitoring the service running condition of the service system;
and sending the monitoring index data to a database server and/or a memory server.
5. The method of claim 4, further comprising:
determining a target working node in a plurality of working nodes, wherein the acquisition end comprises the plurality of working nodes;
the target working node is used for receiving the monitoring index data pushed by the service system, preprocessing the monitoring index data and sending the preprocessed monitoring index data to a database server and/or a memory server.
6. A server, comprising:
the receiving module is used for receiving a first subscription request sent by a subscription end, wherein the first subscription request comprises an identifier of the subscription end and the type of monitoring index data, the monitoring index data is obtained by monitoring the service operation state of a service system, and the subscription end is in communication connection with the server in a long connection mode;
a sending module, configured to send a second subscription request to a memory server, where the second subscription request includes an identifier of the server and a type of the monitoring index data;
the receiving module is further configured to receive monitoring index data pushed by the memory server;
the sending module is further configured to push the monitoring index data to a subscriber.
7. An acquisition device, comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving monitoring index data pushed by a service system, and the monitoring index data is obtained by monitoring the service running condition of the service system;
and the sending module is used for sending the monitoring index data to a database server and/or a memory server.
8. A processing system for monitoring data presentation, comprising:
the acquisition equipment is respectively in communication connection with the service system and the memory server and is used for executing the method of claim 4 or 5;
the memory server is in communication connection with the server and is used for receiving the monitoring index data pushed by the service system and pushing the monitoring index data to the server;
a server connected with at least one subscriber terminal for executing the method of any one of claims 1-3;
and the at least one subscription end is in communication connection with the server in a long connection mode and is used for receiving the monitoring index data pushed by the server and updating the currently displayed monitoring index data according to the monitoring index data.
9. The system of claim 8, wherein the servers are a K8S cluster and the collection devices are a K8S cluster.
10. The system according to claim 8 or 9, characterized in that the system further comprises:
the database server is respectively connected with the acquisition equipment and the server and is used for storing the monitoring index data sent by the acquisition equipment and returning the queried monitoring index data to the server under the condition of receiving a query request of the monitoring index data sent by the server, wherein the query request of the monitoring index data is sent to the server by at least one subscription terminal;
the server is further configured to push the queried monitoring index data to the at least one subscriber.
11. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, perform the method of any one of claims 1-5.
12. A computer program product, comprising a computer program which, when executed by a processor, implements the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110688848.8A CN113391979A (en) | 2021-06-21 | 2021-06-21 | Processing method, equipment and system for monitoring data display and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110688848.8A CN113391979A (en) | 2021-06-21 | 2021-06-21 | Processing method, equipment and system for monitoring data display and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113391979A true CN113391979A (en) | 2021-09-14 |
Family
ID=77623223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110688848.8A Pending CN113391979A (en) | 2021-06-21 | 2021-06-21 | Processing method, equipment and system for monitoring data display and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113391979A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114025016A (en) * | 2021-10-18 | 2022-02-08 | 中国联合网络通信集团有限公司 | Data forwarding method and device and storage medium |
| CN114679503A (en) * | 2022-03-24 | 2022-06-28 | 长桥有限公司 | Market data processing method, system and equipment |
| CN115051979A (en) * | 2022-04-28 | 2022-09-13 | 福思(杭州)智能科技有限公司 | Monitoring data debugging system, method, vehicle and computer readable storage medium |
| CN115277666A (en) * | 2022-06-29 | 2022-11-01 | 浪潮通信技术有限公司 | 5G-based equipment remote operation and maintenance method, device and storage medium |
| CN115514612A (en) * | 2022-09-22 | 2022-12-23 | 杭州职业技术学院 | Data acquisition method, system and storage medium based on Redis message mechanism |
-
2021
- 2021-06-21 CN CN202110688848.8A patent/CN113391979A/en active Pending
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114025016A (en) * | 2021-10-18 | 2022-02-08 | 中国联合网络通信集团有限公司 | Data forwarding method and device and storage medium |
| CN114025016B (en) * | 2021-10-18 | 2024-03-15 | 中国联合网络通信集团有限公司 | Data forwarding method, device and storage medium |
| CN114679503A (en) * | 2022-03-24 | 2022-06-28 | 长桥有限公司 | Market data processing method, system and equipment |
| CN115051979A (en) * | 2022-04-28 | 2022-09-13 | 福思(杭州)智能科技有限公司 | Monitoring data debugging system, method, vehicle and computer readable storage medium |
| CN115051979B (en) * | 2022-04-28 | 2023-09-19 | 福思(杭州)智能科技有限公司 | Monitoring data debugging system, method, vehicle and computer readable storage medium |
| CN115277666A (en) * | 2022-06-29 | 2022-11-01 | 浪潮通信技术有限公司 | 5G-based equipment remote operation and maintenance method, device and storage medium |
| CN115514612A (en) * | 2022-09-22 | 2022-12-23 | 杭州职业技术学院 | Data acquisition method, system and storage medium based on Redis message mechanism |
| CN115514612B (en) * | 2022-09-22 | 2023-08-11 | 杭州职业技术学院 | Data acquisition method, system and storage medium based on Redis message mechanism |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113391979A (en) | Processing method, equipment and system for monitoring data display and storage medium | |
| CN100407627C (en) | Method and system for realizing end-to-end data sharing | |
| EP2453615A1 (en) | Cluster server in instant messaging system and method for communicating between clusters | |
| US20030158892A1 (en) | Apparatus and method for exchanging data between two devices | |
| CN108377247B (en) | Message pushing method and device | |
| CN110417884B (en) | Message pushing method, device, equipment and storage medium | |
| CN115004673B (en) | Message pushing method, device, electronic equipment and computer readable medium | |
| WO2021088641A1 (en) | Data transmission method, data processing method, data reception method and device, and storage medium | |
| CN108390950A (en) | A kind of information push method, device and equipment | |
| CN108712457A (en) | Back-end server dynamic load method of adjustment and device based on Nginx reverse proxys | |
| CN112839067B (en) | Data synchronization method and device | |
| CN114500633B (en) | Data forwarding method, related device, program product and data transmission system | |
| CN110311855B (en) | User message processing method and device, electronic equipment and storage medium | |
| CN116319732A (en) | Message queue centralized configuration management system and method based on RabbitMQ | |
| CN111124717A (en) | Message delivery method, system and computer storage medium | |
| CN110798495A (en) | Method and server for end-to-end message push in cluster architecture mode | |
| CN109918210B (en) | Method and terminal for displaying offline message | |
| US7937433B1 (en) | Queuing connector to promote message servicing | |
| CN113220684A (en) | Data packet storage and query method, device, system and storage medium | |
| CN110166487B (en) | Local area network equipment information transmission method, main equipment, storage medium and intelligent equipment | |
| CN113783913A (en) | Message pushing management method and device | |
| CN114338584B (en) | Message withdraw method and message transmission system | |
| CN113114557B (en) | Message sending method and device, electronic equipment and storage medium | |
| CN115629909A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN112492019B (en) | Message pushing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |