CN109525466A - Back end monitor method and device - Google Patents
Back end monitor method and device Download PDFInfo
- Publication number
- CN109525466A CN109525466A CN201910004437.5A CN201910004437A CN109525466A CN 109525466 A CN109525466 A CN 109525466A CN 201910004437 A CN201910004437 A CN 201910004437A CN 109525466 A CN109525466 A CN 109525466A
- Authority
- CN
- China
- Prior art keywords
- monitor
- target data
- monitoring
- data node
- server
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
Abstract
The application provides a kind of back end monitor method and device, and wherein method monitors target data node including the use of monitor；If the monitor listens to the target data node and changes, notice request is sent to the client for registering the monitor；Retain the monitor to continue to monitor the target data node.The application monitor after a snoop-operations can remain, it will not be deleted, so can repeat to monitor target data node, the case where deleting the variation of target data node is omitted between newly-built monitor is avoided, to omit the variation issue of target data node after solving deletion monitor between newly-built monitor.Client only needs to send a registration request to server-side, it is not necessary to repeatedly send registration request to server-side, it is possible to client and server-side network interaction number is reduced, to save Internet resources and simplify monitoring mechanism operation.
Description
Technical field
This application involves network communication technology field more particularly to back end monitor methods and device.
Background technique
Zookeeper can provide the distribution of open source as distributed coordination service system for large-scale distributed calculating
The services such as configuration, synchronous service and name registration.ZooKeeper system includes server-side and multiple client, and server-side includes
Multiple back end.
In the monitoring mechanism that ZooKeeper is supported, client can register monitor (Watcher) to server-side, with
Just server-side monitors client target data node of interest.It listens to if target data node changes and touches if server-side
The monitor is sent out, to notify to register the client of the monitor.
But since ZooKeeper default monitor is using will be deleted the monitor after primary, so in ZooKeeper
Monitor is only capable of executing a trigger action, i.e., after target data node changes, client can only receive primary logical
Know.Hereafter, target data node changes again, and the client that the monitor is arranged before will not receive notice again.
If client still desires in the case where monitoring target data node, need to register monitor to server-side again,
This will increase the network interaction number of client and server-side；If also, constructed after deleting former monitor new monitor it
Before, target data node changes, then server-side can not listen to the variation, i.e., can omit target data section during this
The variation of point.
That is existing monitoring mechanism in ZooKeeper, operating process is cumbersome, occupies more Internet resources and has centainly
Missing rate.
Summary of the invention
In consideration of it, the application provides back end monitor method and device, it can simplify the operating process of monitoring mechanism, keep away
Exempt to occupy more Internet resources, avoids the variation of missing data node.
To achieve the goals above, this application provides following technical characteristics:
A kind of back end monitor method, comprising:
Target data node is monitored using monitor；
If the monitor listens to the target data node and changes, notice request is sent to registering the prison
Listen the client of device；
Retain the monitor to continue to monitor the target data node.
Optionally, before the monitoring target data node using monitor, further includes:
Receive the registration request that the client is sent；Wherein, the registration request include target data node identification and
Interception type；
Construct monitor corresponding with the registration request；
Store the monitoring information of the monitor；Wherein, the monitoring information includes the client identification, the target
Back end mark and the interception type.
Optionally, if the monitor listens to the target data node and changes, notice request is sent
To the client for registering the monitor, comprising:
If the monitor listens to the variation that the interception type instruction occurs for the target data node, generate logical
Know request；
The notice request is sent to client；Wherein, notice request may include the client identification, target data
Node identification and interception type.
Optionally, the registration request further includes monitoring termination condition, the monitorings termination condition include monitoring parameter with
Monitor threshold value；
It further include updating the monitoring ginseng then after transmission notice request to the client for registering the monitor
Number；
Before the reservation monitor continues to monitor the target data node, further includes:
Judge whether updated monitoring parameter reaches the monitoring threshold value；
If updated monitoring parameter reaches the monitoring threshold value, then it represents that reach the monitoring termination condition, delete institute
State monitor；
If updated monitoring parameter is not up to the monitoring threshold value, then it represents that not up to monitoring termination condition executes institute
It states the reservation monitor and continues the step of monitoring the target data node.
Optionally, in the case where the monitoring parameter includes monitoring number, the monitoring threshold value includes preset times.
In the case where the monitoring parameter includes monitoring duration, the monitoring threshold value includes preset duration.
Optionally, further includes:
Receive the removal request that the client is sent；Wherein, the removal request includes client identification, number of targets
According to node identification and interception type；
Search monitor corresponding with the removal request；
Delete monitor corresponding with the removal request.
A kind of back end monitor method, comprising:
Registration request is sent to server-side, so that the server-side constructs monitor corresponding with the registration request, and
Target data node is monitored using the monitor；
Receive the notice request that the server-side is sent；
Wherein, the notice request listens to the target data node for the monitor of the server-side and becomes
Client is sent to after change, also, server-side can retain the monitor and continue to monitor the target data node.
Optionally, after receiving the notice request that the server-side is sent, further includes:
Data acquisition request corresponding with the notice request is sent to the server-side；
Receive the data content for the target data node that server-side is sent；
If the data content of the target data node reaches setting condition, touching corresponding with the registration request is executed
Hair operation；
Removal request is sent to server-side, so that the server-side deletes the monitor.
A kind of back end monitoring device, comprising:
Node unit is monitored, for monitoring target data node using monitor；
Notification unit is sent, is changed if listening to the target data node for the monitor, is sent logical
Know request to the client for registering the monitor；
Stick unit continues to monitor the target data node for retaining the monitor.
A kind of back end monitoring device, comprising:
Request unit is sent, for sending registration request to server-side, so that server-side building is asked with the registration
Corresponding monitor is sought, and monitors target data node using the monitor；
Notification unit is received, the notice request sent for receiving the server-side；
Wherein, the notice request listens to the target data node for the monitor of the server-side and becomes
Client is sent to after change, also, server-side can retain the monitor and continue to monitor the target data node.
A kind of electronic equipment, comprising:
Processor；And
Memory, for storing the executable instruction of the processor；
Wherein, the processor is configured to execute the back end monitoring side via the executable instruction is executed
Method.
A kind of storage medium, for storing software program, which can be used for realizing described the storage medium
Back end monitor method.
By the above technological means, may be implemented it is following the utility model has the advantages that
The application monitor after a snoop-operations can remain, and will not be deleted, it is possible to repeat to monitor
Target data node avoids deleting the case where variation of target data node is omitted between newly-built monitor, to solve to delete
The variation issue of target data node is omitted after monitor between newly-built monitor.
Client only needs to send a registration request to server-side, it is not necessary to registration request repeatedly is sent to server-side,
So client and server-side network interaction number can be reduced, to save Internet resources and simplify monitoring mechanism operation.
Detailed description of the invention
In order to illustrate the technical solutions in the embodiments of the present application or in the prior art more clearly, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of application for those of ordinary skill in the art without creative efforts, can be with
It obtains other drawings based on these drawings.
Fig. 1 is a kind of structural schematic diagram of back end monitoring system disclosed in the embodiment of the present application；
Fig. 2 is a kind of flow chart of back end monitor method disclosed in the embodiment of the present application；
Fig. 3 is the flow chart of another back end monitor method disclosed in the embodiment of the present application；
Fig. 4 is a kind of structural schematic diagram of back end monitoring device disclosed in the embodiment of the present application；
Fig. 5 is the structural schematic diagram of another back end monitoring device disclosed in the embodiment of the present application.
Specific embodiment
Below in conjunction with the attached drawing in the embodiment of the present application, technical solutions in the embodiments of the present application carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of embodiments of the present application, instead of all the embodiments.It is based on
Embodiment in the application, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall in the protection scope of this application.
The application is mainly used in Zookeeper, thus this application involves server-side be Zookeeper service
Device cluster, client are the machine serviced using Zookeeper.It is subsequent no longer to illustrate one by one.
According to a kind of embodiment of the application, a kind of back end monitoring system is provided.Referring to Fig. 1, back end is monitored
System includes:
Server-side 100；Wherein, server-side 100 can store multiple back end.
The multiple client 200 being connected with server-side 100.
Before introducing back end monitor method provided by the present application, the pre- of server-side 100 and client 200 is first introduced
Execute operation.Referring to fig. 2, pre-execution operation the following steps are included:
Step S201: client generates registration request, and sends registration request to server-side.
Server-side has multiple back end, if some back end in client concern server-side, i.e. client need
Learn whether some back end changes, then registration request can be generated in client, registers to send to server-side
Request, to construct monitor, in server-side whether to change for monitored data node.
By taking target data node as an example, if client needs to learn whether target data node changes, structure is needed
Build registration request corresponding with target data node.Wherein, registration request includes target data node identification, interception type.Note
Volume request can also include monitoring termination condition, also possible not comprising termination condition is monitored in certain registration request.
Introduce each content in registration request one by one below:
Target data node identification: since server-side includes multiple back end, so using target data node identification,
To indicate that registration request is for target data node.
Interception type: target data node changes including many types, for example, creation child node, data value change,
Delete child node etc..
Client can select a type as interception type according to demand, such as data value is selected to change as monitoring
Type, then the monitor of subsequent builds can then be used to monitor whether target data node occurs data value change.Usual situation
Under, if desired the corresponding interception type of a monitor is monitored the multiple types variation of target data node, then can be constructed
For monitoring multiple monitors of different type variation.
It monitors termination condition: increasing monitor termination condition in the registration request, can contribute to persistently monitor in server-side
During target data node, a termination condition is provided for snoop procedure, avoids monitoring the progress lasting without limitation.
It monitors termination condition to include monitoring parameter and monitor threshold value, the present embodiment provides two kinds of realizations for monitoring termination condition
Mode:
The first implementation: in the case where the monitoring parameter includes monitoring number, the monitoring threshold value includes pre-
If number, when monitoring number reaches preset times, reach monitoring termination condition.
Second of implementation: in the case where the monitoring parameter includes monitoring duration, the monitoring threshold value includes pre-
If duration, when monitoring duration reaches preset duration, reach monitoring termination condition.
Step S202: client stores setting condition corresponding with registration request and trigger action.
Setting condition corresponding with registration request can be set in client, and, reach and is needed to be implemented after imposing a condition
Trigger action.Then, setting condition corresponding with registration request and trigger action are stored.About setting condition and trigger action meeting
It describes in step S310~S312, wouldn't repeat herein.
Step S203: server-side receives the registration request that the client is sent, and constructs corresponding with the registration request
Monitor.
Server-side receives the registration request that client is sent, and server-side constructs monitor corresponding with registration request.
In the case where registration request includes client identification, target data node identification and interception type, server-side structure
Monitor is built for monitoring the variation whether target data node occurs the interception type, and after determining change, notice
Client corresponding with client identification.
Registration request can also include monitoring termination condition, which is the survival of above-mentioned building monitor
In the period, reaching just needs to delete monitor after monitoring termination condition, can continue to use monitoring if not up to monitoring termination condition
Device.
Step S204: server-side saves monitoring information.
Server-side would generally safeguard monitoring information table, and monitoring information table can uniformly save each monitoring information, with housecoat
Uniformly manage the monitor of each client in business end.
Referring to table 1, for a kind of signal (be not shown and monitor termination condition) of the monitoring information table of server-side.
Table 1
The corresponding monitor in the column by taking color in table aggravates a column as an example, the monitor are used to be client 1 and visitor
Whether 2 monitored data node 1 of family end occurs the variation of " creation child node ".It is the corresponding client mark of client 1 in field
Know 1 and the corresponding client identification 2 of client 2.
It is above-mentioned to be operated for server-side and client pre-execution, the online implementation procedure of server-side and client is described below.
According to a kind of embodiment of the application, a kind of back end monitor method is provided, is applied to back end shown in FIG. 1
Monitoring system.Monitor corresponding with registration request is provided with monitoring termination condition in the present embodiment.It is understood that if note
Step S304~306 can not then be executed by not including monitoring termination condition in volume request.
Referring to Fig. 3, back end monitor method be may comprise steps of:
Step S301: server-side monitors target data node using monitor.
Under normal conditions, server-side can uniformly monitor whether each back end changes according to monitoring information table.
It is exemplified by Table 1, server-side can monitor each back end in table 1 and identify corresponding back end, interception type whether occurs refer to
The variation shown.
For constructing monitor corresponding with registration request in step 203, server-side can monitor target data node mark
Know corresponding target data node, if the variation of specified interception type instruction occurs.
Step S302: monitor monitors whether target data node changes, if then entering step S303, if not
Then enter step S304.
Under normal conditions, a monitor listens to the change that a certain interception type instruction occurs for a back end in server-side
Change, is then notified that the corresponding all clients of the interception type in the back end.Still by taking color in table 1 aggravates a column as an example,
The variation of creation child node occurs in the corresponding back end 1 of back end mark 1, then server-side is notified that client identification 1
Corresponding client 1 and the corresponding client 2 of client identification 2.
For constructing monitor corresponding with registration request in step 203, whether monitor monitors target data node
The variation that interception type instruction in registration request occurs, if then entering step S303, if otherwise entering step S304.
Step S303: if the monitor listens to the target data node and changes, notice request is sent extremely
The client.
If the monitor listens to the variation that interception type instruction in registration request occurs for the target data node,
Notice request is generated, and sends the notice request to client.Wherein notice request may include the client identification, mesh
Mark back end mark and interception type.
Step S304: server-side updates the monitoring parameter monitored in termination condition.
When the monitoring parameter includes monitoring number, then monitoring number can be updated.For example, at the beginning of monitoring number
In the case where beginning cancellation, monitoring number can be incremented by；Or in the case where monitoring number is initialized as monitoring number,
It can successively decrease and monitor number.
When the monitoring parameter includes monitoring duration, then it can continue record and monitor duration.For example, when monitoring
In the case that length is initialized as zero, record can be continued and monitor duration.Or when monitoring duration is initialized as default monitor
In the case where length, countdown operation can be executed to duration is monitored.
Step S305: server-side judges whether to reach monitoring termination condition；If then entering step S306, if otherwise entering
Step S307.
Server-side may determine that whether monitoring parameter reaches monitoring threshold value；If the monitoring parameter reaches the monitoring threshold
Value, then it represents that reach monitoring termination condition, otherwise indicate not up to monitor termination condition.
When the monitoring parameter includes monitoring number, the monitoring threshold value includes preset times；Monitoring number
In the case of reaching preset times, expression reaches monitoring termination condition, otherwise indicates not up to monitor termination condition.
It include preset duration monitoring threshold value when the monitoring parameter includes monitoring duration.It is up to when monitoring
To in the case of preset duration, expression reaches monitoring termination condition, otherwise indicates not up to monitor termination condition.
Step S306: the monitor is deleted.
If the monitoring parameter reaches the monitoring threshold value, then it represents that reach monitoring termination condition, delete the monitor.
Deleting monitor can specifically include: server-side delete target back end in the monitoring information table of table 1 identifies corresponding prison
The client identification in type is listened, to reach the variation that identical interception type occurs again for target data node, then will not be led to again
Know the client.It should be pointed out that the variation of identical interception type occurs again for target data node, it is still that can notify it
Its client.
Step S307: retain the monitor, enter step S301.
If the monitoring parameter is not up to the monitoring threshold value, then it represents that not up to monitoring termination condition retains the prison
Device is listened, continues to monitor the target data node.This step can repeat to register monitor to server-side to avoid client.
Step S308: client receives the notice request that server-side is sent, and Xiang Suoshu server-side is sent and notice request pair
The data acquisition request answered.
Client receives the notice request that server-side is sent, and notice request may include the client identification, number of targets
According to node identification and interception type.
Client, in order to learn the data of variation, can be generated data and obtain after learning that target data node changes
Take request.
Step S309: client receives the data content for the target data node that server-side is sent.
In the case where data acquisition request includes target data node identification, client receives the target that server-side is sent
The total data content of back end.
Step S310: client judges whether the data content of the target data node reaches setting condition.If then
S311 is entered step, does not execute operation if not.
Client is previously stored with setting condition corresponding with registration request and trigger action, in the target data section
In the case that the data content of point reaches setting condition, indicate that the variation of target data node in server-side has reached client
Demand, trigger action can be executed at this time, and, no longer need to monitor target data node.
In the case where the data content of the target data node not up to imposes a condition, number of targets in server-side is indicated
It is not up to the demand of client according to the variation of node, does not execute trigger action at this time, need to continue to monitor target data node.
Step S311: client executing trigger action corresponding with the registration request.
If data value corresponding with interception type reaches setting condition in the data content, client executing with it is described
The corresponding trigger action of registration request.
For example, target data node is to complain number, imposing a condition is 3 times, and trigger action is to connect artificial customer service, then objective
Family end setting monitor corresponding with number is complained, complains changing for number listening to, and, it gets and complains number
Data value is 3 times, meets 3 times of setting condition, the operation for connecting artificial customer service can be triggered in the case of this.
Step S312: client sends removal request to server-side, so that server-side deletes the monitor.
Target data node is monitored due to client and has reached setting condition, namely meets monitoring demand, so subsequent
It no longer needs to monitor target data node, client sends removal request to server-side.Removal request may include that the deletion is asked
It asks including client identification, target data node identification and interception type.
Step S313: server-side deletes monitor corresponding with removal request.
Even if monitor not up to monitors termination condition in server-side, server-side is in the deletion for receiving client transmission
After request, monitor corresponding with removal request also will be deleted.
Deleting monitor can specifically include: server-side delete target back end in the monitoring information table of table 1 identifies
Client identification in corresponding interception type, to reach the variation that identical interception type occurs again for target data node, then
The client will not be reinformed.
It can learn that the application has the advantages that by above-mentioned technical characteristic
First, the present embodiment monitor after a snoop-operations can remain, and will not be deleted, it is possible to repeat
Target data node is monitored, avoids deleting the case where omitting the variation of target data node between newly-built monitor, to solve
The variation issue of target data node is omitted after deletion monitor between newly-built monitor.
Second, the application provides various ways and continues monitoring mechanism: being to continue when not having and monitoring termination condition
Repeat listening mode；When there is monitoring termination condition and monitoring termination condition is predetermined number of times, repeated for predetermined number of times
Mode；It is specified time repetitive mode in the case where there is monitoring termination condition and monitoring termination condition is specified time.It can
To set repetition advice method according to actual conditions.
Third, client only need to send a registration request to server-side, it is not necessary to repeatedly send and register to server-side
Request, it is possible to client and server-side network interaction number are reduced, to save Internet resources and simplify monitoring mechanism behaviour
Make.
Referring to fig. 4, this application provides a kind of back end monitoring devices, comprising:
Node unit 41 is monitored, for monitoring target data node using monitor；
Notification unit 42 is sent, changes, sends if listening to the target data node for the monitor
Notice is requested to the client for registering the monitor；
Stick unit 43 continues to monitor the target data node for retaining the monitor.
Wherein, back end monitoring device is before monitoring node unit 41 further include:
Receiving unit 44, the registration request sent for receiving the client；Wherein, the registration request includes target
Back end mark and interception type；
Construction unit 45, for constructing monitor corresponding with the registration request；
Storage unit 46, for storing the monitoring information of the monitor；Wherein, the monitoring information includes the client
End mark, the target data node identification and the interception type.
Wherein, sending notification unit 42 includes:
Notice request generation unit 421, if listening to the target data node for the monitor occurs the prison
The variation for listening type to indicate then generates notice request；
Transmission unit 422, for sending the notice request to client；Wherein, notice request may include the visitor
Family end mark, target data node identification and interception type.
Wherein, the registration request further includes monitoring termination condition, and the monitoring termination condition includes monitoring parameter and prison
Listen threshold value；
Then after sending notification unit 42, further includes:
Updating unit 47, for updating the monitoring parameter；
Before the reservation monitor continues to monitor the target data node, further includes:
Whether judging unit 48 reaches the monitoring threshold value for updated monitoring parameter；
Unit 49 is deleted, if reaching the monitoring threshold value for updated monitoring parameter, then it represents that reach the monitoring
Termination condition deletes the monitor；
If updated monitoring parameter is not up to the monitoring threshold value, then it represents that not up to monitoring termination condition, into guarantor
It stays unit 43 to execute the reservation monitor and continues the step of monitoring the target data node.
Wherein, in the case where the monitoring parameter includes monitoring number, the monitoring threshold value includes preset times；Institute
Stating monitoring parameter includes in the case where monitoring duration, and the monitoring threshold value includes preset duration.
Wherein, back end monitoring device further include:
Receiving unit 410, the removal request sent for receiving the client；Wherein, the removal request includes
Client identification, target data node identification and interception type；
Searching unit 411, for searching monitor corresponding with the removal request；
Unit 49 is deleted, for deleting monitor corresponding with the removal request.
Specific implementation about back end monitoring device may refer to Fig. 2 and embodiment shown in Fig. 3, no longer superfluous herein
It states.
Referring to Fig. 5, the application provides a kind of back end monitoring device again, comprising:
Request unit 51 is sent, for sending registration request to server-side, for server-side building and the registration
Corresponding monitor is requested, and monitors target data node using the monitor；
Notification unit 52 is received, the notice request sent for receiving the server-side；
Wherein, the notice request listens to the target data node for the monitor of the server-side and becomes
Client is sent to after change, also, server-side can retain the monitor and continue to monitor the target data node.
Wherein, back end monitoring device is after receiving notification unit 52, further includes:
Acquisition request unit 53 is sent, is asked for sending data acquisition corresponding with the notice request to the server-side
It asks；
Data content unit 54 is received, the data content of the target data node for receiving server-side transmission；
Execution unit 55, if the data content for the target data node reaches setting condition, execute with it is described
The corresponding trigger action of registration request；
Removal request unit 56 is sent, for sending removal request to server-side, so that the server-side deletes the prison
Listen device.
Specific implementation about back end monitoring device may refer to Fig. 2 and embodiment shown in Fig. 3, no longer superfluous herein
It states.
The application also provides a kind of electronic equipment, comprising:
Processor；And
Memory, for storing the executable instruction of the processor；
Wherein, the processor is configured to execute the number as shown in Fig. 2 and Fig. 3 via the executable instruction is executed
According to node monitor method.
This application provides a kind of storage medium, for the storage medium for storing software program, the software program is available
In realization back end monitor method as shown in Figures 2 and 3.
If function described in the present embodiment method is realized in the form of SFU software functional unit and as independent product pin
It sells or in use, can store in a storage medium readable by a compute device.Based on this understanding, the embodiment of the present application
The part of the part that contributes to existing technology or the technical solution can be embodied in the form of software products, this is soft
Part product is stored in a storage medium, including some instructions are used so that calculating equipment (it can be personal computer,
Server, mobile computing device or network equipment etc.) execute all or part of step of each embodiment the method for the application
Suddenly.And storage medium above-mentioned includes: USB flash disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), deposits at random
The various media that can store program code such as access to memory (RAM, Random Access Memory), magnetic or disk.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with it is other
The difference of embodiment, same or similar part may refer to each other between each embodiment.
The foregoing description of the disclosed embodiments makes professional and technical personnel in the field can be realized or use the application.
Various modifications to these embodiments will be readily apparent to those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the application.Therefore, the application
It is not intended to be limited to the embodiments shown herein, and is to fit to and the principles and novel features disclosed herein phase one
The widest scope of cause.
Claims (12)
1. a kind of back end monitor method characterized by comprising
Target data node is monitored using monitor；
If the monitor listens to the target data node and changes, notice request is sent to registering the monitor
Client；
Retain the monitor to continue to monitor the target data node.
2. the method as described in claim 1, which is characterized in that before the monitoring target data node using monitor,
Further include:
Receive the registration request that the client is sent；Wherein, the registration request includes target data node identification and monitoring
Type；
Construct monitor corresponding with the registration request；
Store the monitoring information of the monitor；Wherein, the monitoring information includes the client identification, the target data
Node identification and the interception type.
3. method according to claim 2, which is characterized in that if the monitor listens to the target data node
It changes, then sends notice request to the client for registering the monitor, comprising:
If the monitor listens to the variation that the interception type instruction occurs for the target data node, generates notice and ask
It asks；
The notice request is sent to client；Wherein, notice request may include the client identification, target data node
Mark and interception type.
4. method according to claim 2, which is characterized in that the registration request further includes monitoring termination condition, the prison
Listening termination condition includes monitoring parameter and monitoring threshold value；
It further include updating the monitoring parameter then after transmission notice request to the client for registering the monitor；
Before the reservation monitor continues to monitor the target data node, further includes:
Judge whether updated monitoring parameter reaches the monitoring threshold value；
If updated monitoring parameter reaches the monitoring threshold value, then it represents that reach the monitoring termination condition, delete the prison
Listen device；
If updated monitoring parameter is not up to the monitoring threshold value, then it represents that not up to monitoring termination condition executes the guarantor
The monitor is stayed to continue the step of monitoring the target data node.
5. method as claimed in claim 4, which is characterized in that
In the case where the monitoring parameter includes monitoring number, the monitoring threshold value includes preset times.
In the case where the monitoring parameter includes monitoring duration, the monitoring threshold value includes preset duration.
6. the method as described in claim 1, which is characterized in that further include:
Receive the removal request that the client is sent；Wherein, the removal request includes client identification, target data section
Point identification and interception type；
Search monitor corresponding with the removal request；
Delete monitor corresponding with the removal request.
7. a kind of back end monitor method characterized by comprising
Registration request is sent to server-side, so that the server-side constructs monitor corresponding with the registration request, and is utilized
The monitor monitors target data node；
Receive the notice request that the server-side is sent；
Wherein, the notice request is that the monitor of the server-side listens to after the target data node changes
It is sent to client, also, server-side can retain the monitor and continue to monitor the target data node.
8. the method for claim 7, which is characterized in that
After receiving the notice request that the server-side is sent, further includes:
Data acquisition request corresponding with the notice request is sent to the server-side；
Receive the data content for the target data node that server-side is sent；
If the data content of the target data node reaches setting condition, triggering behaviour corresponding with the registration request is executed
Make；
Removal request is sent to server-side, so that the server-side deletes the monitor.
9. a kind of back end monitoring device characterized by comprising
Node unit is monitored, for monitoring target data node using monitor；
Notification unit is sent, is changed if listening to the target data node for the monitor, is sent notice and ask
It asks to the client for registering the monitor；
Stick unit continues to monitor the target data node for retaining the monitor.
10. a kind of back end monitoring device characterized by comprising
Request unit is sent, for sending registration request to server-side, for server-side building and the registration request pair
The monitor answered, and target data node is monitored using the monitor；
Notification unit is received, the notice request sent for receiving the server-side；
Wherein, the notice request is that the monitor of the server-side listens to after the target data node changes
It is sent to client, also, server-side can retain the monitor and continue to monitor the target data node.
11. a kind of electronic equipment characterized by comprising
Processor；And
Memory, for storing the executable instruction of the processor；
Wherein, the processor is configured to execute as described in any one of claim 1~6 via the executable instruction is executed
Back end monitor method.
12. a kind of storage medium, which is characterized in that for storing software program, which can be used for the storage medium
Realize back end monitor method as described in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910004437.5A CN109525466B (en) | 2019-01-03 | 2019-01-03 | Data node monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910004437.5A CN109525466B (en) | 2019-01-03 | 2019-01-03 | Data node monitoring method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109525466A true CN109525466A (en) | 2019-03-26 |
| CN109525466B CN109525466B (en) | 2020-09-29 |
Family
ID=65798146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910004437.5A Active CN109525466B (en) | 2019-01-03 | 2019-01-03 | Data node monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109525466B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110166528A (en) * | 2019-04-16 | 2019-08-23 | 平安科技（深圳）有限公司 | The method, apparatus and computer equipment for preventing node Notification of Changes from losing |
| CN110321140A (en) * | 2019-05-23 | 2019-10-11 | 天津五八到家科技有限公司 | Data-updating method, device and mobile terminal |
| CN111294382A (en) * | 2019-12-30 | 2020-06-16 | 欧普照明股份有限公司 | Real-time data pushing method and device |
| CN113553126A (en) * | 2021-07-06 | 2021-10-26 | 网易（杭州）网络有限公司 | Data processing method and device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070112856A1 (en) * | 2005-11-17 | 2007-05-17 | Aaron Schram | System and method for providing analytics for a communities framework |
| US20070233710A1 (en) * | 2006-03-31 | 2007-10-04 | Passey Aaron J | Systems and methods for notifying listeners of events |
| CN101977124A (en) * | 2010-11-05 | 2011-02-16 | 山东中创软件工程股份有限公司 | Service clustering method and system based on ZooKeeper technology |
| CN104969222A (en) * | 2013-01-23 | 2015-10-07 | 脸谱公司 | Method and system for using a recursive event listener on a node in hierarchical data structure |
| CN105682115A (en) * | 2014-11-21 | 2016-06-15 | 联想(北京)有限公司 | Information processing method and electronic device |
| CN105791354A (en) * | 2014-12-23 | 2016-07-20 | 中兴通讯股份有限公司 | Job scheduling method and cloud scheduling server |
| CN106155662A (en) * | 2015-04-15 | 2016-11-23 | 高德软件有限公司 | A kind of Web page event-handling method, system and page controller |
| CN106375342A (en) * | 2016-10-21 | 2017-02-01 | 用友网络科技股份有限公司 | Zookeeper-technology-based system cluster method and system |
| CN108347718A (en) * | 2018-02-02 | 2018-07-31 | 北京小米移动软件有限公司 | Monitor the method, apparatus and storage medium of communication bag |
-
2019
- 2019-01-03 CN CN201910004437.5A patent/CN109525466B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070112856A1 (en) * | 2005-11-17 | 2007-05-17 | Aaron Schram | System and method for providing analytics for a communities framework |
| US20070233710A1 (en) * | 2006-03-31 | 2007-10-04 | Passey Aaron J | Systems and methods for notifying listeners of events |
| CN101977124A (en) * | 2010-11-05 | 2011-02-16 | 山东中创软件工程股份有限公司 | Service clustering method and system based on ZooKeeper technology |
| CN104969222A (en) * | 2013-01-23 | 2015-10-07 | 脸谱公司 | Method and system for using a recursive event listener on a node in hierarchical data structure |
| CN105682115A (en) * | 2014-11-21 | 2016-06-15 | 联想(北京)有限公司 | Information processing method and electronic device |
| CN105791354A (en) * | 2014-12-23 | 2016-07-20 | 中兴通讯股份有限公司 | Job scheduling method and cloud scheduling server |
| CN106155662A (en) * | 2015-04-15 | 2016-11-23 | 高德软件有限公司 | A kind of Web page event-handling method, system and page controller |
| CN106375342A (en) * | 2016-10-21 | 2017-02-01 | 用友网络科技股份有限公司 | Zookeeper-technology-based system cluster method and system |
| CN108347718A (en) * | 2018-02-02 | 2018-07-31 | 北京小米移动软件有限公司 | Monitor the method, apparatus and storage medium of communication bag |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110166528A (en) * | 2019-04-16 | 2019-08-23 | 平安科技（深圳）有限公司 | The method, apparatus and computer equipment for preventing node Notification of Changes from losing |
| WO2020211361A1 (en) * | 2019-04-16 | 2020-10-22 | 平安科技（深圳）有限公司 | Method for preventing loss of node change notification, device and computer apparatus |
| CN110166528B (en) * | 2019-04-16 | 2022-03-18 | 平安科技（深圳）有限公司 | Method and device for preventing node change notification from being lost and computer equipment |
| CN110321140A (en) * | 2019-05-23 | 2019-10-11 | 天津五八到家科技有限公司 | Data-updating method, device and mobile terminal |
| CN111294382A (en) * | 2019-12-30 | 2020-06-16 | 欧普照明股份有限公司 | Real-time data pushing method and device |
| CN113553126A (en) * | 2021-07-06 | 2021-10-26 | 网易（杭州）网络有限公司 | Data processing method and device |
| CN113553126B (en) * | 2021-07-06 | 2024-03-22 | 网易（杭州）网络有限公司 | Data processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109525466B (en) | 2020-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109525466A (en) | Back end monitor method and device | |
| US10817324B2 (en) | System and method of cross-silo discovery and mapping of storage, hypervisors and other network objects | |
| CN108234168B (en) | Data display method and system based on service topology | |
| US6687750B1 (en) | Network traffic visualization | |
| WO2020119540A1 (en) | Group profile picture generation method and device | |
| CN109660400A (en) | Flow control configuration method and system | |
| CN107241380B (en) | Method and apparatus for time-based adjusted load balancing | |
| US11843674B2 (en) | Virtual workspace experience visualization and optimization | |
| TW201814609A (en) | Information pushing | |
| CN110334074B (en) | Data processing method, device, server and storage medium | |
| CN105337841A (en) | Information processing method and system, client, and server | |
| CN109842524A (en) | Automatically updating method, device, electronic equipment and computer readable storage medium | |
| CN111311014B (en) | Service data processing method, device, computer equipment and storage medium | |
| CN109992325B (en) | Information display method, information display apparatus, storage medium, and electronic apparatus | |
| CN111158979A (en) | Service dial testing method, system, device and storage medium | |
| CN112764837B (en) | Data reporting method, device, storage medium and terminal | |
| CN114866617A (en) | Micro-service request processing method, device, equipment and medium | |
| CN111669290B (en) | Network element management method, management server and storage medium | |
| CN114390015A (en) | Data pushing system, method and equipment based on object model and storage medium | |
| CN112087327A (en) | Information state acquisition method and apparatus, storage medium, and electronic apparatus | |
| CN111552715A (en) | User query method and device | |
| CN113542103B (en) | Method and device for monitoring invitations of accounts in social communication group and mobile terminal | |
| CN110321276A (en) | The generation method and device of test case | |
| CN109947892A (en) | Analysis path determines method and system, interface, log tree constructing method | |
| CN114205320B (en) | Message display 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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200731 Address after: 310000 2 6th Floor, No. 3588 Jiangnan Avenue, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Hangzhou Yunyi Network Technology Co.,Ltd. Address before: 11, building 310053, Hang Seng tower, 3588 Jiangnan Avenue, Hangzhou, Zhejiang, Binjiang District Applicant before: HANGZHOU YUN-IN NETWORK TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |