CN111459773B - System and method for monitoring and alarming swagger service - Google Patents
System and method for monitoring and alarming swagger service Download PDFInfo
- Publication number
- CN111459773B CN111459773B CN202010363863.0A CN202010363863A CN111459773B CN 111459773 B CN111459773 B CN 111459773B CN 202010363863 A CN202010363863 A CN 202010363863A CN 111459773 B CN111459773 B CN 111459773B
- Authority
- CN
- China
- Prior art keywords
- swagger
- address
- monitoring
- service
- addresses
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Telephonic Communication Services (AREA)
- Alarm Systems (AREA)
Abstract
The invention discloses a system and a method for monitoring and alarming a swagger service. The swagger service monitoring and alarming system comprises a front-end module, a back-end module, a timing task and a database; the front-end module provides configuration of swagger monitoring information, configuration of alarm notifier information, configuration of timing task rules, configuration of service restarting times and closing of monitoring functions; the back-end module automatically analyzes the swagger address and transmits the processed information input by the front-end user to the database for storage; the database is used for storing information; the timing task can monitor a large amount of service in real time with minimum network flow, and can automatically restart and trigger the nail alarm notification when the service is hung up. The invention can realize real-time monitoring of mass service with minimum network flow, and can automatically restart and nail to inform a specific person when the service is hung off, thereby greatly saving the time for positioning problems of research personnel, reducing the labor cost and improving the efficiency.
Description
Technical Field
The invention belongs to the technical field of computer software, and relates to a system and a method for monitoring and alarming a swagger service.
Background
The number of services deployed at the back end in the application system is large (up to 300), and when one service is hung up, the developer cannot know the service state in time. When the tested system cannot be accessed correctly, a researcher needs to take a lot of time to grasp the package at the front end, then check the log file from the rear end to locate the problem, and when the problem is located because the service is hung up (abnormal occurrence), then restart the service manually.
Because a process is generated after the back-end service deployment is completed, in the prior art, whether the service normally operates or is abnormal is judged by monitoring whether the process exists or not. But doing so has several drawbacks: firstly, the state of the back-end service cannot be known in real time, and secondly, when the service is hung up, the service needs to be restarted manually. Furthermore, even if a process exists, it is often not possible to tell that a service is available. In actual operation we find that a scenario exists where a process exists but a service is not already accessible.
Disclosure of Invention
In order to solve the problems, the invention discloses a swagger service monitoring and alarming system and an implementation method thereof.
In order to achieve the above purpose, the present invention provides the following technical solutions:
the swagger service monitoring and alarming system comprises a front-end module, a back-end module, a timing task and a database; the front-end module provides a user interface, obtains a swagger address, a user notification number, a corresponding service line name and a wiki address based on the user interface, and transmits the swagger address, the user notification number, the corresponding service line name and the wiki address to the back-end module; the back-end module is used for reading and processing parameters transmitted by the front end; marking the swagger address input by the user and acquired by the front-end module as active monitoring; automatically analyzing the swagger information in the address library corresponding to the wiki address, filtering out the part which is configured as active monitoring, adding the part which is not configured yet into a monitoring list, and marking that the swagger addresses are passive monitoring; storing all obtained swagger addresses, corresponding business line names, active and passive monitoring marks and user notification numbers into a database; the timing task is used for periodically starting monitoring at fixed time, a connection database acquires all swagger address information during starting, firstly analyzes and processes the swagger address, judges whether the swagger address is the swagger address of the system, triggers an alarm by an invalid address, and adopts a HEAD request mode to obtain summary information of the swagger service corresponding to the swagger address, analyzes and judges whether the swagger is abnormal according to the summary information, and automatically restarts and triggers a notification if the swagger is abnormal; if the swagger service is normal, continuing to monitor the next swagger service is skipped.
Furthermore, the front-end module can also acquire the number of times of automatic restarting service and monitoring rules, and the timing task starts the swagger service monitoring according to the monitoring rules.
Further, the back-end module also judges whether a non-monitoring identifier exists before the swagger address after processing the parameters transmitted by the front-end, and skips the swagger address when the non-monitoring identifier exists.
Further, the back-end module processing procedure includes: removing the parameters of front and back blank spaces and front and back line-wrapping symbols, cutting by using the line-wrapping symbols, removing the blank spaces of the character strings of each line after cutting, putting a new array, and finally converting the array into the character strings.
Further, the swagger address marked as passively monitored does not distinguish between corresponding traffic lines.
Further, the notification triggered by the timing task includes an abnormal swagger address, an active and passive monitoring mode of the swagger, a restarting service name, restarting times and a jump link when the person needs to intervene.
The swagger service monitoring and alarming method comprises the following steps:
step 1, obtaining a swagger address, a user notification number and a wiki address of each service line input by a user;
step 2, processing the information obtained in the step 1;
step 3, judging whether the first character of the address contains a preset non-monitoring identifier, and skipping the swagger address when the non-monitoring identifier exists; when judging that the user inputs a non-swagger address, reminding the user of filling errors of the swagger address according to the user notification number; the swagger address input by the user which does not accord with the judgment is marked as active monitoring; obtaining a swagger address in an address library linked with a wiki address, filtering out the swagger address actively monitored therein, and marking the rest swagger addresses as passive monitoring; storing all the obtained swagger addresses, the corresponding business line names, the active and passive monitoring marks and the user notification numbers into a database;
step 4, the timing connection database acquires all the swagger address information, after acquiring the address, firstly analyzing the swagger address, judging whether the swagger address is the swagger address of the system, triggering an alarm by an invalid address, acquiring summary information of the swagger service corresponding to the swagger address by adopting a HEAD request mode by the effective address, analyzing and judging whether the swagger is abnormal according to the summary information, restarting for a plurality of times automatically if the swagger is abnormal, and triggering and notifying corresponding engineers; if the swagger service is normal, continuing to execute the next swagger service is skipped.
As an improvement, the number of automatic restart services and the monitoring rule are also acquired in step 1.
As an improvement, the triggering notification in step 4 includes an abnormal swagger address, an active and passive monitoring mode of the swagger, a restarting service name, restarting times and a jump link when a person needs to intervene.
Further, in the step 3, when the user inputs the non-swagger address, the user is reminded of filling errors in the swagger address according to the user notification number entered on the user interface.
Compared with the prior art, the invention has the following advantages and beneficial effects:
according to the invention, one swagger configuration is injected for each service, and then whether the service is available or not is judged by monitoring the swagger, so that the monitoring mode is more accurate and effective. The scheme of the invention can realize real-time monitoring of mass service with minimum network flow, and can automatically restart and spike to inform a specific person when the service is hung off, thereby greatly saving the time for positioning problems of research personnel, reducing the labor cost and improving the efficiency.
Drawings
Fig. 1 is a schematic diagram of a system for monitoring and alarming a swagger service according to the present invention.
Fig. 2 is a schematic diagram of a user interface provided by the front-end module.
Detailed Description
The technical scheme provided by the present invention will be described in detail with reference to the following specific examples, and it should be understood that the following specific examples are only for illustrating the present invention and are not intended to limit the scope of the present invention. Additionally, the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that herein.
The invention provides a swagger service monitoring and alarming system which comprises a front-end module, a back-end module, a timing task and a database. The front-end module is built based on the VUE framework, provides the functions of configuring the swagger monitoring information, configuring the alarm notifier information, configuring the timing task rule, configuring the service restarting times and closing the monitoring, and transmits the information acquired by the front-end to the back-end module; the back-end module is built based on a Django frame, automatically analyzes the swagger address, and transmits the processed information input by the front-end user to a database for storage; the database is realized by mysql and is used for storing information; the timing task can monitor a large amount of service in real time with minimum network flow, and can automatically restart and trigger the nail alarm notification when the service is hung up.
Specifically, the front-end module provides a user interface as shown in fig. 2, and provides a swagger configuration page of each service line on the interface, and each service line engineer manually configures the swagger address to be monitored and marks that the monitoring is active. Specifically, a plurality of text boxes which can be input and modified by a user are arranged in the page, the user can input and modify the swagger address and the nailing mobile phone number which need to be monitored, and the automatic restarting service times and the monitoring rules (such as the monitoring time period, the time period has a default value in fig. 2) can be configured. When the swagger is not monitored, the input swgger address is annotated with a "#" sign (alternatively, other non-monitoring identifiers) in front of the input swgger address. The front-end module acquires parameters such as a swagger address to be monitored, a corresponding service line name, a nailing mobile phone number, a monitoring time period and a wiki address from a user interface and then transmits the parameters to the back-end module. The system also provides a wiki address library for recording the swagger address, the wiki address on the user interface can be linked to the address library after being clicked, and the user can inquire the swagger address.
The back-end module reads the parameters transmitted by the front end, processes the parameters and stores the parameters in the database. The parameters input by the front end are in character string format, and the processing procedure in this example comprises: removing the parameters of front and back blank spaces and front and back line-wrapping symbols, cutting by using the line-wrapping symbols, removing the blank spaces of the character strings of each line after cutting, putting a new array, and finally converting the array into the character strings and storing the character strings into a database. When the back-end module reads the address, the back-end module firstly judges whether the first character of the address is the "#" sign, and if yes, the swagger is skipped. The swagger addresses of other user inputs acquired by the front end module are marked as active monitoring. When the user inputs the non-swagger address, the nail is triggered according to the mobile phone number input on the user interface to remind the user of filling errors in the swagger address. In addition to user input, the back-end module automatically acquires wiki addresses of recorded swagger information, automatically analyzes the internal swagger information, then judges whether the user of the swagger address inputs active configuration (namely, whether the user input addresses are contained in the addresses input by the user acquired by the front-end) through the interface, filters out the user input addresses if the user input addresses are already configured, adds the user input addresses into a monitoring list if the user input addresses are not already configured, and marks that the swagger address is passively monitored. And finally, the back-end module writes all the obtained swagger addresses into a database for persistence, wherein the obtained swagger addresses comprise service line names corresponding to the swagger addresses and corresponding mobile phone numbers, and mark information of whether the swaggers are actively monitored or passively monitored. The passively monitored swagger addresses are not separated from the service line, and a reminder (the mobile phone number of which is stored in advance) is designated by default.
The timing task is used for periodically starting monitoring at fixed time, the connection database acquires all the swagger address information at the starting time, after the addresses are acquired, the swagger address is firstly analyzed and processed, whether the swagger address is the swagger address of the system is judged, the invalid address triggers the nail alarm, the effective address adopts a HEAD request mode, the summary information of the swagger address corresponding to the swagger service is acquired with the minimum network flow, whether the swagger is hung up is judged according to the analysis of the summary information, if the swagger is hung up (when the state code is not 200 or 304), the connection database is restarted for N times automatically according to the configured restarting times, the corresponding engineer is triggered to be informed by the nail, and the nail information comprises the hung-up swagger address, whether the swgger is actively monitored or passively monitored, which service is restarted, and the jump link is restarted for a plurality of times when the man needs to be in a medium. If the swagger service is normal, continuing to monitor the next swagger service is skipped. The timing task should start the swagger service monitoring according to the monitoring period configured in the front-end module.
Based on the system, the invention also provides a swagger service monitoring and alarming method, which comprises the following steps:
step 1, obtaining a swagger address, a user notification number and a wiki address of each service line input by a user; in this example, the user notification number is a nailed cell phone number. As an improvement, the number of automatic restart services and a monitoring rule are also acquired in this step, and the monitoring rule is a monitoring time period.
Step 2, processing the information obtained in the step 1 and then storing the processed information in a database, wherein the method specifically comprises the following steps: removing the parameters of front and back blank spaces and front and back line-wrapping symbols, cutting by using the line-wrapping symbols, removing the blank spaces of the character strings of each line after cutting, putting a new array, and finally converting the array into the character strings and storing the character strings into a database.
Step 3, judging whether the first character of the address contains a preset non-monitoring mark, wherein the non-monitoring mark is a "#" sign in the example, and skipping the swagger when the first character of the address is the "#"; when judging that the user inputs a non-swagger address, triggering a nail to remind the user of filling errors of the swagger address according to the user notification number; the user input swagger address which does not accord with the judgment is the correct swagger address which needs to be monitored normally, and is marked as active monitoring. And acquiring the swagger addresses in the address library linked with the wiki addresses, filtering out the swagger addresses actively monitored in the swagger addresses, and marking the rest swagger addresses as passive monitoring. All the obtained swagger addresses and the marks thereof are stored in a database.
And 4, the timing connection database acquires all the swagger address information, after acquiring the address, firstly analyzing the swagger address, judging whether the swagger address is the swagger address of the system, triggering a nail alarm by an invalid address, acquiring summary information of the swagger service corresponding to the swagger address by adopting a HEAD request mode by the effective address, judging whether the swagger is hung up according to the summary information analysis, and if the swagger is hung up (when the state code is not 200 or 304), restarting N times automatically according to the configured restarting times and triggering a nail to inform a corresponding engineer, wherein the nail information comprises the hung-up swagger address, whether the swagger is actively monitored or passively monitored, restarting a plurality of times and a jump link when a person needs to be in a medium. If the swagger service is normal, continuing to monitor the next swagger service is skipped.
The technical means disclosed by the scheme of the invention is not limited to the technical means disclosed by the embodiment, and also comprises the technical scheme formed by any combination of the technical features. It should be noted that modifications and adaptations to the invention may occur to one skilled in the art without departing from the principles of the present invention and are intended to be within the scope of the present invention.
Claims (10)
- A swagger service monitoring and alerting system, characterized by: the system comprises a front-end module, a back-end module, a timing task and a database; the front-end module provides a user interface, obtains a swagger address, a user notification number, a corresponding service line name and a wiki address based on the user interface, and transmits the swagger address, the user notification number, the corresponding service line name and the wiki address to the back-end module; the back-end module is used for reading and processing parameters transmitted by the front end; marking the swagger address input by the user and acquired by the front-end module as active monitoring; automatically resolving the swagger addresses in the address library corresponding to the wiki addresses, filtering out the part which is configured as active monitoring, adding the swagger addresses which are not configured yet into a monitoring list, and marking the swagger addresses as passive monitoring; storing all obtained swagger addresses, corresponding business line names, active and passive monitoring marks and user notification numbers into a database; the timing task is used for periodically starting monitoring at fixed time, a connection database acquires all the swagger addresses during starting, firstly analyzes the swagger addresses, judges whether the swagger addresses are the swagger addresses of the system, triggers an alarm by an invalid address, and adopts a HEAD request mode to obtain summary information of the swagger services corresponding to the swagger addresses, analyzes and judges whether the swagger services are abnormal according to the summary information, and automatically restarts and triggers a notification if the swagger services are abnormal; if the swagger service is normal, continuing to monitor the next swagger service is skipped.
- 2. The swagger service monitoring and alert system according to claim 1, wherein: the front-end module can also acquire the number of times of automatic restarting service and monitoring rules, and the timing task starts the swagger service monitoring according to the monitoring rules.
- 3. The swagger service monitoring and alert system according to claim 1, wherein: the back-end module also judges whether a non-monitoring mark exists before the swagger address after processing the parameters transmitted by the front end, and skips the swagger address when the non-monitoring mark exists.
- 4. The swagger service monitoring and alert system according to claim 1, wherein: the back-end module processing process comprises the following steps: removing the parameters of front and back blank spaces and front and back line-wrapping symbols, cutting by using the line-wrapping symbols, removing the blank spaces of the character strings of each line after cutting, putting a new array, and finally converting the array into the character strings.
- 5. The swagger service monitoring and alert system according to claim 1, wherein: the swagger address marked as passively monitored does not distinguish between corresponding traffic lines.
- 6. The swagger service monitoring and alert system according to claim 1, wherein: the notification triggered by the timing task comprises an abnormal swagger address, an active and passive monitoring mode of the swagger, a restarting service name, restarting times and a jump link when the person needs to intervene.
- The method for monitoring and alarming the swagger service is characterized by comprising the following steps:step 1, obtaining a swagger address, a user notification number and a wiki address of each service line input by a user;step 2, processing the information obtained in the step 1;step 3, judging whether the first character of the address contains a preset non-monitoring identifier, and skipping the swagger address when the non-monitoring identifier exists; when judging that the user inputs a non-swagger address, reminding the user of filling errors of the swagger address according to the user notification number; the swagger address input by the user which does not accord with the judgment is marked as active monitoring; obtaining a swagger address in an address library linked with a wiki address, filtering out the swagger address actively monitored therein, and marking the rest swagger addresses as passive monitoring; storing all the obtained swagger addresses, the corresponding business line names, the active and passive monitoring marks and the user notification numbers into a database;step 4, the timing connection database acquires all the swagger addresses, after acquiring the addresses, firstly analyzing the swagger addresses, judging whether the addresses are the swagger addresses of the system, triggering an alarm by an invalid address, acquiring summary information of the swagger services corresponding to the swagger addresses by adopting a HEAD request mode by the effective address, analyzing and judging whether the swagger services are abnormal according to the summary information, restarting for a plurality of times automatically if the swagger services are abnormal, and triggering and notifying corresponding engineers; if the swagger service is normal, continuing to execute the next swagger service is skipped.
- 8. The method for monitoring and alarming a swagger service according to claim 7, wherein the number of times of automatic restart service and the monitoring rule are also obtained in step 1.
- 9. The method for monitoring and alarming the swagger according to claim 7, wherein the triggering notification in step 4 includes an abnormal swagger address, an active and passive monitoring mode of the swagger, a restarting service name, restarting times, and a jump link when a person needs to intervene.
- 10. The method for monitoring and alarming the swagger according to claim 7, wherein in the step 3, when the user inputs the non-swagger address, the user is reminded of filling errors in the swagger address according to the user notification number entered on the user interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010363863.0A CN111459773B (en) | 2020-04-30 | 2020-04-30 | System and method for monitoring and alarming swagger service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010363863.0A CN111459773B (en) | 2020-04-30 | 2020-04-30 | System and method for monitoring and alarming swagger service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111459773A CN111459773A (en) | 2020-07-28 |
| CN111459773B true CN111459773B (en) | 2023-09-05 |
Family
ID=71686049
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010363863.0A Active CN111459773B (en) | 2020-04-30 | 2020-04-30 | System and method for monitoring and alarming swagger service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111459773B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160246592A1 (en) * | 2015-02-20 | 2016-08-25 | International Business Machines Corporation | Dynamic extensibility of application programming interfaces |
| CN106708676A (en) * | 2016-12-01 | 2017-05-24 | 广州酷狗计算机科技有限公司 | Interface test method and apparatus |
| US20190196948A1 (en) * | 2017-12-27 | 2019-06-27 | Accenture Global Solutions Limited | Touchless testing platform |
| CN110825619A (en) * | 2019-10-12 | 2020-02-21 | 深圳壹账通智能科技有限公司 | Automatic generation method and device of interface test case and storage medium |
-
2020
- 2020-04-30 CN CN202010363863.0A patent/CN111459773B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160246592A1 (en) * | 2015-02-20 | 2016-08-25 | International Business Machines Corporation | Dynamic extensibility of application programming interfaces |
| CN106708676A (en) * | 2016-12-01 | 2017-05-24 | 广州酷狗计算机科技有限公司 | Interface test method and apparatus |
| US20190196948A1 (en) * | 2017-12-27 | 2019-06-27 | Accenture Global Solutions Limited | Touchless testing platform |
| CN110825619A (en) * | 2019-10-12 | 2020-02-21 | 深圳壹账通智能科技有限公司 | Automatic generation method and device of interface test case and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111459773A (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3355197A1 (en) | Fault processing method, related apparatus, and computer | |
| CN104966172A (en) | Large data visualization analysis and processing system for enterprise operation data analysis | |
| CN106681913A (en) | Application not responding positioning system and method | |
| CN108259268B (en) | Network monitoring data processing method and device, computer equipment and storage medium | |
| WO2020237877A1 (en) | Log monitoring method and apparatus, terminal, and storage medium | |
| US11310140B2 (en) | Mitigating failure in request handling | |
| CN110007857B (en) | Method and device for predicting service life of flash memory chip | |
| CN111291384A (en) | Vulnerability scanning method and device and electronic equipment | |
| CN114356499A (en) | Kubernetes cluster alarm root cause analysis method and device | |
| JP2007241872A (en) | Program for monitoring change in computer resource on network | |
| CN108874618B (en) | Cognos process monitoring method and device, computer equipment and storage medium | |
| EP3646182A1 (en) | Recovery of application from error | |
| CN111813590A (en) | Method and device for diagnosing abnormal reset of main control module and main control module | |
| CN111459773B (en) | System and method for monitoring and alarming swagger service | |
| CN114756406A (en) | Processing method and device for application program crash and electronic equipment | |
| CN106055703B (en) | Log real-time analysis method and system | |
| CN110888790B (en) | Log management method and device, electronic equipment and storage medium | |
| CN112328602A (en) | Method, device and equipment for writing data into Kafka | |
| CN112306871A (en) | Data processing method, device, equipment and storage medium | |
| CN116566810A (en) | System exception handling method, device and equipment based on Spring MVC framework | |
| CN112543127A (en) | Monitoring method and device of micro-service architecture | |
| CN113568811A (en) | Distributed safety monitoring data processing method | |
| CN115168137A (en) | Monitoring method and system for timing task, computer equipment and storage medium | |
| CN114265669A (en) | Destroyed container instance identification method and device | |
| CN110502404B (en) | Early warning processing method based on data management platform and related equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |