CN111343222A - Method and device for monitoring subsystem to limit flow, storage medium and server - Google Patents
Method and device for monitoring subsystem to limit flow, storage medium and server Download PDFInfo
- Publication number
- CN111343222A CN111343222A CN201811554346.0A CN201811554346A CN111343222A CN 111343222 A CN111343222 A CN 111343222A CN 201811554346 A CN201811554346 A CN 201811554346A CN 111343222 A CN111343222 A CN 111343222A
- Authority
- CN
- China
- Prior art keywords
- subsystem
- user
- state
- monitoring
- running state
- 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
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
Abstract
The invention discloses a method, a device, a storage medium and a server for monitoring the flow limited by a subsystem, wherein the method comprises the steps of monitoring the running state of the subsystem and generating a flow limiting rule for logging in the subsystem according to the running state; and processing the login request of the subsystem according to the current limiting rule. By limiting the amount of users logging in the subsystem, the poor experience of the users when accessing the subsystem is avoided, and the subsystem breakdown caused by a large amount of users logging in the subsystem can be avoided.
Description
Technical Field
The invention belongs to the technical field of cloud platforms, and particularly relates to a method and a device for monitoring a subsystem to limit flow, a storage medium and a server.
Background
In the prior art, a cloud platform includes a plurality of subsystems, and a user logs in the corresponding subsystem through each entry provided by the cloud platform. Taking a code scanning cloud platform as an example, the code scanning cloud platform is used as a uniform entrance for scanning codes by equipment, and bears millions of browsing login amounts every day. The framework of the cloud platform system is designed according to high availability and high performance, a large number of users can access the first page of the code scanning cloud platform without problems, but the framework of each sub-service system in the cloud platform can not realize the high availability and high performance design, when the large number of users flow to the sub-service system through the code scanning cloud platform inlet, a large number of risks of accessing and crushing the service system exist, and user experience is poor. If the original sub-service systems are required to change the existing architecture to support the high available performance, a lot of manpower, time and money are required, and the method is limited in many aspects.
Disclosure of Invention
The present invention is directed to overcome the above drawbacks of the prior art, and provides a method, an apparatus, a storage medium, and a server for monitoring a subsystem to limit traffic, so as to solve the problem in the prior art that a large number of users have poor user experience when accessing the subsystem.
One aspect of the present invention provides a method for monitoring a subsystem to limit a flow, including: monitoring the running state of a subsystem, and generating a current limiting rule for logging in the subsystem according to the running state, wherein the current limiting rule is used for limiting the amount of users logging in the subsystem; and processing the login request of the subsystem according to the current limiting rule.
Optionally, monitoring an operating state of a subsystem, and generating a current limiting rule for logging in the subsystem according to the operating state includes: and sending a health check request to the subsystem, judging the running state of the subsystem according to a returned check result, and prohibiting a user from logging in the subsystem when the subsystem is judged to be in a breakdown state.
Optionally, when the returned check result includes at least one of the following, it is determined that the subsystem is in a crash state:
the subsystem receives the health detection request and then does not respond or overtime responds;
the http state code in the returned check result is an abnormal http state code;
checking that the returned checking result does not meet a preset interface standard;
the returned check result indicates that the operation is not normal.
Optionally, processing the login request of the subsystem according to the current limiting rule includes: and after receiving the login request, forbidding the user to login the subsystem, and feeding back first prompt information to the user, wherein the first prompt information is used for reminding the user that the subsystem is in a collapse state.
Optionally, the method further includes: and when the subsystem is in the breakdown state, feeding back second prompt information to an administrator, wherein the second prompt information is used for reminding the administrator that the subsystem is in the abnormal state.
Optionally, monitoring an operating state of a subsystem, and generating a current limiting rule for logging in the subsystem according to the operating state includes: and sending a health check request to the subsystem, judging the running state of the subsystem according to a returned check result, and allowing a user to log in the subsystem when the subsystem is judged to be in a normal running state.
Optionally, the returned check result includes whether the running state is a normal running state or not and a running state score; when the subsystem is judged to be in a normal operation state, allowing a user to log in the subsystem, wherein the steps comprise: and setting the waiting time for the user to log in the subsystem according to the running state score, wherein the waiting time is inversely proportional to the running state score.
Optionally, the returned inspection result includes a response time after the subsystem receives the health inspection request; when the subsystem is judged to be in a normal operation state, allowing a user to log in the subsystem, wherein the steps comprise: and setting up the waiting time for the user to log in the subsystem according to the response time, wherein the waiting time is in direct proportion to the response time.
Optionally, monitoring the operating state of the subsystem includes: and monitoring the running state of the subsystem in real time and updating.
In another aspect, the present invention provides an apparatus for monitoring a flow restriction of a subsystem, comprising: the monitoring module is used for monitoring the running state of the subsystem and generating a current limiting rule for logging in the subsystem according to the running state; and the processing module is used for processing the login request of the subsystem according to the current limiting rule.
Optionally, the processing module further includes a first feedback module, where the first feedback module is configured to feed back first prompt information to the user, and the first prompt information is used to remind the user that the subsystem is in a crash state.
Optionally, the processing module further includes a second feedback module, where the second feedback module is configured to feed back second prompt information to the administrator, and the second prompt information is used to remind the administrator that the subsystem is in an abnormal state.
A further aspect of the invention provides a storage medium having a computer program stored thereon which, when executed by a processor, implements any of the methods described above.
A further aspect of the present invention provides a server comprising a processor, a memory, and a computer program stored in the memory and operable on the processor, wherein the processor executes the computer program to implement the method of any one of the preceding claims.
According to the scheme provided by the invention, when a user requests to log in the subsystem through the cloud platform entrance, the running state of the subsystem is monitored at first, the current limiting rule of the logging subsystem is generated according to the running state, and the cloud platform can process the login request of the user according to the current limiting rule. By limiting the amount of users logging in the subsystem, the poor experience of the users when accessing the subsystem is avoided, and the subsystem breakdown caused by a large amount of users logging in the subsystem can be avoided.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
FIG. 1 is a schematic flow chart diagram illustrating an embodiment of a method for monitoring subsystem traffic limits provided by the present invention;
FIG. 2 is a schematic flow chart illustrating another embodiment of a method for monitoring subsystem traffic limits provided by the present invention;
FIG. 3 is a schematic flow chart diagram illustrating a method for monitoring subsystem traffic limits according to another embodiment of the present invention;
FIG. 4 is a schematic flow chart diagram illustrating a method for monitoring subsystem traffic limits according to another embodiment of the present invention;
FIG. 5 is a schematic flow chart diagram illustrating a method for monitoring subsystem traffic limits according to yet another embodiment of the present invention;
FIG. 6 is a schematic diagram of an embodiment of an apparatus for monitoring a subsystem limit flow provided by the present invention;
fig. 7 is a schematic workflow diagram of another embodiment of the apparatus for monitoring a subsystem to restrict flow provided by the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the specific embodiments of the present invention and the accompanying drawings. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a method for monitoring the flow limitation of a subsystem, which can be applied to a cloud platform system, and when a user requests to log in a certain subsystem through an entrance of a cloud platform, the method provided by the invention can be adopted to ensure that the user can log in and access the corresponding subsystem according to the current flow limitation rule corresponding to the running state of the subsystem, so as to improve the user experience.
Fig. 1 is a schematic flow chart of a method for monitoring a subsystem to limit a flow according to an embodiment of the present invention. As shown in fig. 1, the method for monitoring the flow limitation of the subsystem according to the present invention at least includes step S101 and step S102. Wherein the content of the first and second substances,
step S101: monitoring the running state of the subsystem, and generating a current limiting rule of the login subsystem according to the running state, wherein the current limiting rule is used for limiting the user amount of the login subsystem;
the cloud platform comprises a plurality of subsystems, the running states of the subsystems can be respectively monitored, and then the current limiting rules corresponding to the subsystems are respectively generated according to the running states of the subsystems. Optionally, the operating states of the subsystems can be monitored in real time, and when a user requests to log in the subsystems, the user's login request is processed according to the existing current limiting rule, that is, whether the user can log in the subsystems is determined.
In a specific embodiment, the invention judges the running state of the subsystem according to the returned checking result by sending a health checking request to the subsystem. By setting the health check interface standard, each subsystem develops a corresponding interface according to the interface standard, and judges the running state of the subsystem according to the return result of the health check interface. The running state of the subsystem comprises a normal running state and a breakdown state, and the subsystem can provide normal service for a user in the normal running state; in a crash state, the subsystem cannot provide normal service for the user due to the fact that the number of users is too large, or the hardware of the subsystem per se fails, and the like.
Step S102: and processing the login request of the subsystem according to the current limiting rule. For example, taking a code scanning cloud platform as an example, a user enters a homepage of the cloud platform through code scanning, and then requests to log in a subsystem under the cloud platform through an entry in the homepage, at this time, the system processes the login request of the user according to the generated current limiting rule.
In one embodiment, when the subsystem is determined to be in a crash state, the current limiting rule includes: the user is prohibited from logging into the subsystem. At this time, when the user requests to log in the system, the platform can ignore the login request of the user, that is, the user is not allowed to log in the crashed subsystem page. In the related art, when a user logs in a subsystem, the user can find that the subsystem is broken down after entering a page of the subsystem under the condition that the subsystem cannot provide services for the user at all, and the user experience is poor. According to the generated current limiting rule, when the system is in a breakdown state, the user is prohibited from logging in the subsystem, the user is prevented from entering a broken subsystem page, and therefore user experience is improved.
In some optional embodiments, when the health check request is sent to the subsystem, the returned check result may include: the subsystem receives no response or overtime response after the health check request interface, namely, the request health check interface has no response or overtime response; the http state code in the returned check result is an abnormal http state code; in the returned checking result, the checking interface does not meet the preset interface standard; the returned check result shows that the subsystem is not in normal operation, namely, a field which shows whether the subsystem is in normal operation state exists in the returned check result, and when the subsystem is in a crash state, the returned check result also shows that the returned check result is in the following field: and is not operating normally. And when the return result comprises at least one of the above, judging that the subsystem is in a breakdown state.
In one embodiment, fig. 2 is a schematic flow chart of another embodiment of a method for monitoring a subsystem to limit a flow provided by the present invention. As shown in fig. 2, the method for monitoring the flow limitation of the subsystem according to the present invention at least includes steps S201 to S203, wherein,
step S201: sending a health check request to the subsystem, and judging the running state of the subsystem according to the returned check result;
step S202: when the subsystem is judged to be in a breakdown state, the current limiting rule is to prohibit a user from logging in the subsystem;
step S203: after receiving the login request, forbidding the user to login the subsystem, and feeding back first prompt information to the user, wherein the first prompt information is used for reminding the user that the subsystem is in a collapse state.
In this embodiment, when it is monitored that the subsystem is in a crash state, the login request of the user is ignored, the user is prohibited from logging in the subsystem, and the first prompt information is fed back to the user at the same time, for example, when the user requests to enter the subsystem through the code scanning cloud platform, the first prompt information may be displayed on the terminal device used by the user: the current system has crashed, please log in later. After the user receives similar reminding information, the current state of the subsystem can be mastered, the user can not continue to wait for a long time to enter the subsystem under the condition, the user is prevented from having a fussy and anxious emotion in the login waiting process, the time of the user can be saved, and the user experience is improved.
In an embodiment, fig. 3 is a schematic flow chart of a method for monitoring a subsystem to limit a flow according to another embodiment of the present invention. As shown in fig. 3, the method for monitoring the flow restriction of the subsystem according to the present invention at least includes step S101 and step S302, wherein,
step S301: sending a health check request to the subsystem, and judging the running state of the subsystem according to the returned check result;
step S302: and when the subsystem is in the breakdown state, feeding back second prompt information to an administrator, wherein the second prompt information is used for reminding the administrator that the subsystem is in the abnormal state.
In this embodiment, when it is monitored that the subsystem is in a crash state, the second prompt information is fed back to the administrator, and the administrator may be, for example, a person in charge of the subsystem, and may notify the person in charge of the subsystem that the running state of the subsystem is abnormal by sending a short message to the person in charge of the subsystem, and the like, so that the user service cannot be provided, the service of the subsystem is recovered as early as possible, and the influence on the user experience is avoided. The implementation mode ensures that the self-maintenance check can be carried out on the running state of the subsystem instead of repairing the system when the user feeds back the system breakdown, and the service quality of the system can be improved.
In one embodiment, the current limiting rule is to allow a user to log in the subsystem when the subsystem is determined to be in a normal operation state. At this time, when the user requests to log in the system, the platform can log in the subsystem page which normally runs through the login request of the user.
In some cases, although a user can log in to the subsystem, the user browsing amount of the subsystem is already large, and a large number of users accessing the subsystem results in a large data processing amount of the subsystem, and the response time of the subsystem becomes slow, which may seriously affect the user experience. The invention further proposes a solution to this problem.
In an embodiment, fig. 4 is a schematic flow chart of a method for monitoring a subsystem to limit a flow according to another embodiment of the present invention. As shown in fig. 4, the method for monitoring the flow limitation of the subsystem according to the present invention at least includes steps S401 to S402, wherein,
step S401: sending a health check request to the subsystem, and judging the running state of the subsystem according to a returned check result, wherein the returned check result comprises whether the running state is a normal running state or not and a running state score;
step S402: and setting the waiting time of the user for logging in the subsystem according to the running state score, wherein the waiting time is inversely proportional to the running state score.
The returned inspection results consist of two parts: the first part represents the current running state of the subsystem, namely whether the subsystem is in normal running or not and whether the subsystem can continue to provide services or not; the second part represents the current operating state score of the subsystem, with higher scores representing a healthier system. Alternatively, the scoring may be self-determined by the subsystem. Optionally, the scoring index may include a CPU usage rate, a memory usage rate, a server response time, a service abnormality rate, or the like. It should be noted that, when determining the subsystem operating state, the present invention does not determine whether the system has crashed according to the subsystem operating state score in the returned result.
In this embodiment, when the state of the subsystem is normal and the score is the highest, the user access to the subsystem is not limited, and the subsystem can be accessed directly and normally, optionally, the user waiting time is 0; when the status of the subsystem is functioning properly and the score is not high, user access to the subsystem is restricted. The embodiment ensures the quantity of users accessing the subsystem within a certain time by waiting for queuing, thereby ensuring the normal operation of the subsystem and ensuring that users logging in the subsystem can be smoothly used.
In an embodiment, fig. 5 is a flowchart illustrating a method for monitoring a subsystem to limit a flow according to another embodiment of the present invention. As shown in fig. 5, the method for monitoring the flow restriction of the subsystem according to the present invention at least includes steps S501 to S502, wherein,
step S501: sending a health check request to the subsystem, and judging the running state of the subsystem according to a returned check result, wherein the returned check result comprises the response time of the subsystem after receiving the health check request;
step S502: and setting up the waiting time for the user to log in the subsystem according to the response time, wherein the waiting time is in direct proportion to the response time.
In this embodiment, the response time after the subsystem receives the health check request interface, that is, the response time of the health check request interface, may be used as a basis for limiting the user access, and the shorter the response time, the healthier the subsystem is, that is, the shorter the response time, the shorter the user waiting time is.
In one embodiment, the latency of the user logging into the subsystem may be formulated by simultaneously referencing the running status score in the returned results and the response time of the request health check interface.
In some alternative embodiments, the present invention provides methods in which the operational status of the subsystems is monitored and updated in real time. And then, re-formulating the current limiting rule of the corresponding login subsystem according to the updated running state of the subsystem. The operation state of the subsystem is monitored in real time in the operation process of the system, so that once a user requests to log in the subsystem, the login request of the user can be processed according to the latest current limiting rule, and the user experience is improved.
Fig. 6 is a schematic diagram of an embodiment of the apparatus for monitoring a subsystem to limit flow provided by the present invention. As shown in fig. 6, the apparatus 100 provided by the present invention at least comprises: the monitoring module 10 is used for monitoring the running state of the subsystem and generating a current limiting rule for logging in the subsystem according to the running state; and the processing module 20 is used for processing the login request of the subsystem according to the current limiting rule.
In some optional embodiments, the monitoring module 10 is configured to send a health check request to the subsystem, and determine an operating state of the subsystem according to a returned result; when the subsystem is judged to be in a breakdown state, the current limiting rule is to prohibit a user from logging in the subsystem; and when the subsystem is judged to be in a normal running state, allowing a user to log in the subsystem according to the current limiting rule.
In some optional embodiments, when the returned check result includes whether the returned check result is a normal operation state and an operation state score, the monitoring module 10 is further configured to set a waiting time for the user to log in the subsystem according to the operation state score, wherein the waiting time is inversely proportional to the operation state score.
In some optional embodiments, when the returned check result includes a response time after the subsystem receives the health check request, the monitoring module 10 is further configured to set a waiting time for the user to log in the subsystem according to the response time, where the waiting time is proportional to the response time.
In an embodiment, in the apparatus provided in the present invention, the processing module further includes a first feedback module, where the first feedback module is configured to feed back first prompt information to the user, and the first prompt information is used to remind the user that the subsystem is in a crash state. Fig. 7 is a schematic workflow diagram of another embodiment of the apparatus for monitoring a subsystem to restrict flow provided by the present invention. As shown in fig. 7, the device monitoring provided by the present invention processes a user login request for one time. When a user requests to log in the subsystem through an entrance of the platform, a monitoring module in the device for monitoring the subsystem to limit the flow starts to call the running state of the subsystem according to the login request, when the subsystem is in a normal running state, a processing module responds to the login request of the user and controls the user to log in the subsystem according to the current flow limiting rule, for example, the flow limiting rule is corresponding waiting time determined according to the return time of the check result of the health check request, and the user quantity of accessing the subsystem in a certain time is ensured in a waiting queue mode, so that the normal running of the subsystem is ensured, and meanwhile, the user logging in the subsystem can be smoothly used. When the subsystem is in a collapse state, the processing module sends an instruction to prohibit a user from logging in the subsystem, meanwhile, the first feedback module in the control module can send friendly prompt (first prompt information) to a front end (a terminal device used by the user) to prompt the current state of the subsystem, the user can adjust the own time arrangement according to the prompt, the user can not continue to wait for entering the subsystem for a long time under the condition, the time of the user can be saved, and the user experience is improved.
In an embodiment, in the apparatus provided by the present invention, the processing module further includes a second feedback module, where the second feedback module is configured to feed back second prompt information to the administrator, and the second prompt information is used to remind the administrator that the subsystem is in an abnormal state. In this embodiment, when it is monitored that the subsystem is in a crash state, the second prompt information is fed back to the administrator, and the administrator may be, for example, a person in charge of the subsystem, and may notify the person in charge of the subsystem that the running state of the subsystem is abnormal by sending a short message to the person in charge of the subsystem, and the like, so that the user service cannot be provided, the service of the subsystem is recovered as early as possible, and the influence on the user experience is avoided.
The invention also provides a storage medium having a computer program stored therein, which when executed by a processor implements any of the methods described above.
The invention also provides a server comprising a processor, a memory and a computer program stored on the memory and operable on the processor, the processor implementing any of the methods described above when executing the program.
The invention also provides a server comprising any one of the devices.
In summary, it is readily understood by those skilled in the art that the advantageous modes described above can be freely combined and superimposed without conflict.
Therefore, according to the scheme provided by the invention, when a user requests to log in the subsystem through the cloud platform entrance, the running state of the subsystem is monitored at first, the current limiting rule of the logging subsystem is generated according to the running state, and the cloud platform can process the login request of the user according to the current limiting rule. By limiting the amount of users logging in the subsystem, the poor experience of the users when accessing the subsystem is avoided, and the subsystem breakdown caused by a large amount of users logging in the subsystem can be avoided.
The above description is only an example of the present invention, and is not intended to limit the present invention, and it is obvious to those skilled in the art that various modifications and variations can be made in the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (15)
1. A method of monitoring a subsystem restriction flow, comprising:
monitoring the running state of a subsystem, and generating a current limiting rule for logging in the subsystem according to the running state, wherein the current limiting rule is used for limiting the amount of users logging in the subsystem;
and processing the login request of the subsystem according to the current limiting rule.
2. The method of claim 1, wherein monitoring an operational state of a subsystem and generating a current limit rule for logging into the subsystem based on the operational state comprises:
and sending a health check request to the subsystem, judging the running state of the subsystem according to a returned check result, and prohibiting a user from logging in the subsystem when the subsystem is judged to be in a breakdown state.
3. The method of claim 2,
when the returned check result comprises at least one of the following conditions, judging that the subsystem is in a breakdown state:
the subsystem receives the health check request and then does not respond or overtime responds;
the http state code in the returned check result is an abnormal http state code;
the returned checking result shows that the checking interface does not meet the preset interface standard;
the returned check result indicates that the operation is not normal.
4. The method of claim 2, wherein processing the login request of the subsystem according to the current limiting rule comprises:
and after receiving the login request, forbidding the user to login the subsystem, and feeding back first prompt information to the user, wherein the first prompt information is used for reminding the user that the subsystem is in a collapse state.
5. The method of claim 2, further comprising:
and when the subsystem is in the breakdown state, feeding back second prompt information to an administrator, wherein the second prompt information is used for reminding the administrator that the subsystem is in the abnormal state.
6. The method according to any one of claims 1 to 5, wherein monitoring an operational state of a subsystem and generating a current limiting rule for logging into the subsystem based on the operational state comprises:
and sending a health check request to the subsystem, judging the running state of the subsystem according to a returned check result, and allowing a user to log in the subsystem when the subsystem is judged to be in a normal running state.
7. The method of claim 6,
the returned checking result comprises whether the returned checking result is in a normal operation state or not and an operation state score;
when the subsystem is judged to be in a normal operation state, allowing a user to log in the subsystem, wherein the steps comprise:
and setting the waiting time for the user to log in the subsystem according to the running state score, wherein the waiting time is inversely proportional to the running state score.
8. The method of claim 6,
the returned check result comprises the response time of the subsystem after receiving the health check request;
when the subsystem is judged to be in a normal operation state, allowing a user to log in the subsystem, wherein the steps comprise:
and setting up the waiting time for the user to log in the subsystem according to the response time, wherein the waiting time is in direct proportion to the response time.
9. The method of any one of claims 1-8, wherein monitoring the operational status of the subsystem comprises:
and monitoring the running state of the subsystem in real time and updating.
10. An apparatus for monitoring a subsystem flow restriction, comprising:
the monitoring module is used for monitoring the running state of the subsystem and generating a current limiting rule for logging in the subsystem according to the running state;
and the processing module is used for processing the login request of the subsystem according to the current limiting rule.
11. The apparatus of claim 10, wherein the processing module further comprises a first feedback module, and wherein the first feedback module is configured to feed back first prompt information to a user, and wherein the first prompt information is configured to remind the user that the subsystem is in a crash state.
12. The apparatus according to claim 10 or 11, wherein the processing module further comprises a second feedback module, and the second feedback module is configured to feed back a second prompt message to the administrator, and the second prompt message is configured to remind the administrator that the subsystem is in an abnormal state.
13. A storage medium, characterized in that a computer program is stored in the storage medium, which program, when being executed by a processor, carries out the method of any one of claims 1 to 9.
14. A server comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 9 when executing the program.
15. A server, characterized in that it comprises the apparatus of any one of claims 10 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811554346.0A CN111343222A (en) | 2018-12-18 | 2018-12-18 | Method and device for monitoring subsystem to limit flow, storage medium and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811554346.0A CN111343222A (en) | 2018-12-18 | 2018-12-18 | Method and device for monitoring subsystem to limit flow, storage medium and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111343222A true CN111343222A (en) | 2020-06-26 |
Family
ID=71186817
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811554346.0A Pending CN111343222A (en) | 2018-12-18 | 2018-12-18 | Method and device for monitoring subsystem to limit flow, storage medium and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111343222A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112083659A (en) * | 2020-09-27 | 2020-12-15 | 珠海格力电器股份有限公司 | Intelligent household system safety monitoring method, intelligent household system and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101902697A (en) * | 2009-05-26 | 2010-12-01 | 北大方正集团有限公司 | System and method for monitoring and operating service through mobile equipment |
| CN103324539A (en) * | 2013-06-24 | 2013-09-25 | 浪潮电子信息产业股份有限公司 | Job scheduling management system and method |
| US20160099930A1 (en) * | 2014-10-07 | 2016-04-07 | Nicholas James Minovski | Restriction of ip access based on personal performance |
| CN106161443A (en) * | 2016-06-29 | 2016-11-23 | 网易（杭州）网络有限公司 | A kind of monitoring method and device of game service |
| CN106254331A (en) * | 2016-07-28 | 2016-12-21 | 努比亚技术有限公司 | A kind of terminal applies request managing device and method, communication system |
| CN108566317A (en) * | 2018-04-27 | 2018-09-21 | 深信服科技股份有限公司 | Business monitoring method, Cloud Server, storage medium and device |
-
2018
- 2018-12-18 CN CN201811554346.0A patent/CN111343222A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101902697A (en) * | 2009-05-26 | 2010-12-01 | 北大方正集团有限公司 | System and method for monitoring and operating service through mobile equipment |
| CN103324539A (en) * | 2013-06-24 | 2013-09-25 | 浪潮电子信息产业股份有限公司 | Job scheduling management system and method |
| US20160099930A1 (en) * | 2014-10-07 | 2016-04-07 | Nicholas James Minovski | Restriction of ip access based on personal performance |
| CN106161443A (en) * | 2016-06-29 | 2016-11-23 | 网易（杭州）网络有限公司 | A kind of monitoring method and device of game service |
| CN106254331A (en) * | 2016-07-28 | 2016-12-21 | 努比亚技术有限公司 | A kind of terminal applies request managing device and method, communication system |
| CN108566317A (en) * | 2018-04-27 | 2018-09-21 | 深信服科技股份有限公司 | Business monitoring method, Cloud Server, storage medium and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112083659A (en) * | 2020-09-27 | 2020-12-15 | 珠海格力电器股份有限公司 | Intelligent household system safety monitoring method, intelligent household system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109586952B (en) | Server capacity expansion method and device | |
| US20210004628A1 (en) | Method and system for website detection | |
| EP2763069A1 (en) | Method and device for multiple engine virus killing | |
| JP2009519541A (en) | Automated device blog creation | |
| CN108200132B (en) | Resource acquisition method, device, equipment and computer readable storage medium | |
| US20170293614A1 (en) | Method and device for information processing | |
| CN104869052A (en) | Implementation method of social platform with monitoring function, client, server, and social platform system with monitoring function | |
| CN110222107B (en) | Data transmission method and related equipment | |
| CN105786636B (en) | A kind of system repair and device | |
| CN110737548B (en) | Data request method and server | |
| CN114257550B (en) | Automatic control method and device for interface access flow, storage medium and server | |
| CN111343222A (en) | Method and device for monitoring subsystem to limit flow, storage medium and server | |
| CN109948332A (en) | A kind of physical machine login password remapping method and device | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN112286559A (en) | Upgrading method and device for vehicle-mounted intelligent terminal | |
| CN111052072B (en) | Installation-free application program downloading method and device | |
| TW201412069A (en) | Method and system for providing digital content in a network environment | |
| CN115080381A (en) | Mimicry escape quick identification module and method and mimicry request response model framework | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN110457632B (en) | Webpage loading processing method and device | |
| CN113039751B (en) | Fault notification method, device and equipment | |
| CN113457142A (en) | Method and device for determining cloud equipment server in cloud game and business server | |
| US10365870B2 (en) | Information processing system for detecting overload of a management server and processing a priority request having priority, and information processing method for detecting overload of a management server and processing a priority request having a high priority | |
| CN113779562A (en) | Zero trust based computer virus protection method, device, equipment and medium | |
| CN109634721B (en) | Method and related device for starting communication between virtual machine and host |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200626 |
|
| RJ01 | Rejection of invention patent application after publication |