CN111506455B - Checking method and device for service release result - Google Patents
Checking method and device for service release result Download PDFInfo
- Publication number
- CN111506455B CN111506455B CN202010240543.6A CN202010240543A CN111506455B CN 111506455 B CN111506455 B CN 111506455B CN 202010240543 A CN202010240543 A CN 202010240543A CN 111506455 B CN111506455 B CN 111506455B
- Authority
- CN
- China
- Prior art keywords
- target service
- service
- release
- result
- monitoring index
- 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
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000012544 monitoring process Methods 0.000 claims abstract description 190
- 230000008859 change Effects 0.000 claims abstract description 157
- 230000005856 abnormality Effects 0.000 claims abstract description 20
- 238000007689 inspection Methods 0.000 claims description 39
- 238000009826 distribution Methods 0.000 claims description 30
- 238000004458 analytical method Methods 0.000 claims description 20
- 238000003860 storage Methods 0.000 claims description 14
- 238000012795 verification Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 abstract description 20
- 230000002159 abnormal effect Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000012827 research and development Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008439 repair process Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000003631 expected effect Effects 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000011112 process operation Methods 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000007670 refining Methods 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- 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/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a checking method and a checking device for service release results, which relate to the technical field of mobile internet, wherein the method comprises the following steps: identifying a service change type and a release monitoring index of the target service according to the release change information of the target service; obtaining a publishing result of the target service according to the monitored flow data after the target service is published; according to the service change type and the release monitoring index of the target service, which are obtained through identification, the release result is checked to obtain a check result; the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service. Through the technical scheme of the application, the manual intervention and judgment in the existing service issuing process can be effectively simplified, the checking result is intelligently obtained, whether the corresponding rollback operation is executed or not is intelligently obtained, and the corresponding loss caused by the online abnormality of the service is reduced.
Description
Technical Field
The application relates to the technical field of mobile internet, in particular to a method and a device for checking a service release result.
Background
With the rapid development of the internet technology, the rapid iteration becomes the characteristic of the internet product, and under the high-speed iteration, the risk brought by the product change is increased, so that the risk that the whole product is unavailable due to service release exists. Therefore, in the prior art, for service distribution of online services, research and development or operation and maintenance personnel generally manually operate online and perform observation and verification, and for problems occurring during or after the distribution, the research and development or operation and maintenance personnel usually perform manual abnormal repair or rollback change after troubleshooting.
However, the prior art has the disadvantages that the efficiency of manually repairing the abnormality or performing rollback change is low, i.e. developers need to be contacted to confirm whether rollback is possible, and corresponding online operation records need to be searched, so that the operation is complicated, the timeliness of repairing the abnormality or rollback change is poor, and the online abnormality of service is easy to cause corresponding loss; meanwhile, the expected effect of the change is manually identified and whether the rollback can be carried out or not is confirmed, so that the checking and verification intelligence of the service issuing process is poor.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for checking a service delivery result, a storage medium, and a terminal, and mainly aims to solve the problem that the efficiency and the intelligence of repairing an abnormal service delivery process or performing a rollback change are low.
According to an aspect of the present application, there is provided a method for checking a service distribution result, including:
identifying a service change type and a release monitoring index of the target service according to the release change information of the target service;
obtaining a publishing result of the target service according to the monitored flow data after the target service is published;
according to the service change type and the release monitoring index of the target service, which are obtained through identification, the release result is checked to obtain a check result;
the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service.
Preferably, before the step of identifying the service change type and the release monitoring index of the target service according to the release change information of the target service, the method further includes:
the system comprises a service change type unit for creating service and a release monitoring index unit related to the service change type unit.
Preferably, the obtaining a publishing result of the target service according to the monitored flow data after the target service is published specifically includes:
determining the checking time for checking the target service according to the identified release monitoring index of the target service;
and monitoring the flow data after the target service is issued, acquiring the flow data of the target service in the checking time, and taking the flow data as an issuing result of the target service.
Preferably, the checking the distribution result according to the service change type and the distribution monitoring index of the target service obtained by identification to obtain a checking result specifically includes:
according to the issuing monitoring index of the target service, obtaining an inspection result of whether the analysis result of the flow data in the issuing result is within the required range of the issuing monitoring index of the target service;
if the analysis result of the flow data in the release result is within the required range of the release monitoring index of the target service, obtaining an inspection result for continuously inspecting whether the flow data of the associated service of the target service is within the required range of the release monitoring index of the target service;
and if the flow data of the associated service of the target service is not in the required range of the target service for issuing the monitoring index, obtaining an inspection result whether the global anomaly belongs to the target service or not according to the monitored time information of the global anomaly.
Preferably, the method further comprises:
according to the checking result, executing corresponding rollback operation according to the service change type of the target service, which specifically comprises the following steps:
if the analysis result of the flow data in the issuing result is not in the requirement range of the issuing monitoring index of the target service, determining whether to execute rollback operation according to the service change type of the target service;
if the flow data of the associated service of the target service is in the requirement range of the release monitoring index of the target service, determining whether to execute rollback operation according to the service change type of the target service;
and if the global exception belongs to the target service, determining whether to execute rollback operation according to the service change type of the target service.
Preferably, if the traffic data of the service related to the target service is not within the range of the requirement for issuing the monitoring index of the target service, obtaining, according to the monitored time information of the global anomaly, an inspection result of whether the global anomaly belongs to the target service, specifically including:
if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service, identifying whether the target service release has global abnormality or not according to the release monitoring index of the target service;
if the target service is issued with global abnormity, whether the global abnormity belongs to the inspection result of the target service is judged according to the monitored time information of the global abnormity.
Preferably, also includes;
if the global influence identifier in the target service release monitoring index is negative, the target service release has no global exception, the target service is allowed to continue releasing, and a checking result of the release completion is obtained.
According to another aspect of the present application, there is provided a verification apparatus for issuing a result, including:
the identification module is used for identifying the service change type and the release monitoring index of the target service according to the release change information of the target service;
the monitoring module is used for obtaining a publishing result of the target service according to the monitored flow data after the target service is published;
the checking module is used for checking the issuing result according to the service change type and the issuing monitoring index of the target service, which are obtained through identification, so as to obtain the checking result;
the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service.
Preferably, the apparatus further comprises:
the system comprises a creating module and a monitoring module, wherein the creating module is used for creating a service change type unit of the service and a release monitoring index unit related to the service change type unit.
Preferably, the monitoring module specifically includes:
the time unit is used for determining the checking time for checking the target service according to the identified release monitoring index of the target service;
and the acquisition unit is used for monitoring the flow data after the target service is issued, acquiring the flow data of the target service in the checking time and taking the flow data as an issuing result of the target service.
Preferably, the checking module specifically includes:
the first checking unit is used for obtaining a checking result of whether the analysis result of the flow data in the issuing result is within the required range of the issuing monitoring index of the target service according to the issuing monitoring index of the target service;
a second checking unit, configured to obtain a checking result of continuously checking whether traffic data of a service associated with the target service is within a required range of the release monitoring index of the target service if an analysis result of the traffic data in the release result is within the required range of the release monitoring index of the target service;
and the third checking unit is used for obtaining a checking result whether the global abnormity belongs to the target service according to the monitored time information of the abnormity of the issued monitoring index if the flow data of the related service of the target service is not in the required range of the issued monitoring index of the target service.
Preferably, the apparatus further comprises:
a rollback module, configured to execute a corresponding rollback operation according to the service change type of the target service according to the inspection result, specifically including:
a first rollback unit, configured to determine whether to execute a rollback operation according to a service change type of the target service if an analysis result of the flow data in the publishing result is not within a required range of a publishing monitoring index of the target service;
the second rollback unit is used for determining whether to execute rollback operation according to the service change type of the target service if the traffic data of the associated service of the target service is within the requirement range of the release monitoring index of the target service;
and the third rollback unit is used for determining whether to execute rollback operation according to the service change type of the target service if the global exception belongs to the target service.
Preferably, the third checking unit specifically includes:
if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service, identifying whether the target service release has global abnormality or not according to the release monitoring index of the target service;
if the target service is issued with global abnormity, whether the global abnormity belongs to the inspection result of the target service is judged according to the monitored time information of the global abnormity.
Preferably, the third checking unit further comprises;
if the global influence identifier in the target service release monitoring index is negative, the target service release has no global exception, the target service is allowed to continue releasing, and a checking result of the release completion is obtained.
According to still another aspect of the present application, there is provided an electronic device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the above-mentioned method for checking the service distribution result when executing the program.
According to still another aspect of the present application, there is provided a computer-readable storage medium having at least one executable instruction stored therein, where the executable instruction causes a processor to perform operations corresponding to the method for checking a service issuance result as described above.
Compared with the scheme that the existing research and development or operation and maintenance personnel need to observe and verify service release, manually troubleshoot the release problem and manually repair the abnormity or perform rollback change by developers, the method and the device for checking the service release result determine the service change type and the release monitoring index of the released target service by identifying the service change type information and the release monitoring index information contained in the release change information of the target service and obtain the release result of the target service according to the monitored flow data after the target service is released so as to check the release result according to the service change type and the release monitoring index of the target service to obtain the check result. The release monitoring index is a checking index capable of determining whether the target service executes the rollback operation according to the service change type of the target service. Therefore, the method and the device can realize the checking of the target service release result according to the service change type and the release monitoring index of the target service, and further determine whether the target service executes the corresponding rollback operation or not based on the service change type and the release monitoring index of the target service, thereby effectively simplifying the human intervention and judgment in the existing service release process, intelligently acquiring the check result and whether the corresponding rollback operation is executed or not, reducing the corresponding loss caused by the online abnormality of the service, simultaneously effectively improving the work efficiency of repairing the abnormality or performing the rollback change in the existing service release process, and reducing the time cost and the capital investment cost.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating a method for checking a service issuance result according to an embodiment of the present application;
fig. 2 is a flowchart illustrating another method for checking a service distribution result according to an embodiment of the present application;
fig. 3 is a schematic structural diagram illustrating an inspection apparatus for issuing a result by a service according to an embodiment of the present application;
fig. 4 is a schematic structural diagram illustrating another ping apparatus for issuing a result by a service according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The method aims at the technical problems of low efficiency and intelligence of abnormal repair or rollback change of the existing service release process. The embodiment provides an inspection method for a service release result, which can effectively simplify human intervention and judgment in the existing service release process, intelligently acquire the inspection result and determine whether to execute corresponding rollback operation, reduce corresponding loss caused by online abnormality of the service, effectively improve the work efficiency of repairing the abnormality or performing rollback change of the existing service release process, and reduce time cost and capital investment cost. As shown in fig. 1, the method includes:
In this embodiment, an examination system of a service release result, which uses an examination method of the service release result, obtains a release work order of a target service, where the release work order includes the target service to be released and release change information, and the release change information of the target service includes basic information such as a service change type and a release monitoring index of the target service. According to the release change history data of the business service, determining that the service change type of the target service comprises a conventional function iteration change type, a new function on-line change type, a bugfix change type and a service configuration change type, and accordingly, the release monitoring index associated with the service change type of the target service includes an expected result (for example, an expected effect of service release), a check time, an associated service, an alarm threshold value for triggering rollback, a global influence (for example, whether the service release influences the global service when abnormal, whether the service release influences the main service flow (for example, whether the service release influences the main service flow, namely, the service flow is interrupted and cannot continue to work when the service release is abnormal), and whether the service release is automatically rolled (for example, whether the service release change can automatically execute a roll-back operation when the check is abnormal).
And step 102, obtaining a publishing result of the target service according to the monitored flow data after the target service is published.
In this embodiment, according to the ping time included in the monitoring indicator issued in the issuance change information of the target service, the monitoring mechanism is used to obtain the traffic data within the ping time after the issuance of the target service, and the traffic data is used as the issuance result to be ping for the target service. The traffic data may be an access volume and the service issuance monitoring mechanism may be zabbix or open-falcon, according to the needs of the actual application scenario, but is not limited herein.
And 103, checking the release result according to the service change type and the release monitoring index of the target service, which are obtained through identification, so as to obtain a checking result.
In this embodiment, the association relationship between the service change type of the target service and the release monitoring index is used to check the release result of the target service, specifically, the corresponding release monitoring index result in the obtained release result is checked according to the release monitoring index to obtain a check result that whether the obtained check result meets the release monitoring index, so as to further determine whether the obtained check result needs to perform a rollback operation according to the service change type of the target service.
By applying the technical scheme of the embodiment, compared with the prior art that research and development are needed or operation and maintenance personnel observe the release of the verification service, compared with the scheme of manually checking the issue problem and manually repairing the abnormity or performing rollback change by developers, the embodiment can realize the check of the issue result of the target service according to the service change type and the issue monitoring index of the target service, and further determines whether the target service performs a corresponding rollback operation based on the service change type and the release monitoring index of the target service, thereby effectively simplifying the human intervention and judgment in the existing service issuing process, intelligently acquiring the checking result and whether to execute the corresponding rollback operation, reducing the corresponding loss caused by the online abnormality of the service, meanwhile, the working efficiency of repairing abnormity or performing rollback change of the conventional service release process is effectively improved, and the time cost and the capital investment cost are reduced.
Further, as a refinement and an extension of the specific implementation of the foregoing embodiment, in order to fully illustrate the specific implementation process of the present embodiment, another method for checking a service distribution result is provided, as shown in fig. 2, where the method includes:
step 201, creating a service change type unit of a service, and associating a release monitoring index unit of the service change type unit.
In specific implementation, an option for performing interactive operation with a technician is added on the platform side of the service release result checking system applying the service release result checking method, and the option comprises a service change type unit and a release monitoring index unit which has an association relationship with the service change type unit. Specifically, when a service work order generation instruction from a technician is received, according to a service change type and a release monitoring index of a target service to be released, which are selected by the technician by clicking or the like, release change information of the target service including the service change type and the release monitoring index of the target service, and a service release work order including the release change information of the target service are generated.
Specifically, the conventional function iteration change type in the service change types refers to conventional service function iteration, that is, performing function perfection on an original service function point, for example, issuing changes such as page adjustment; the new function online change type refers to that a new service module or a service function is online, wherein the new function can exist in an existing service module, namely a historical online record exists, or the new function belongs to the new service module, namely service release is executed for the first time, and the historical online record does not exist; the Bugfix change type is used for repairing bugs existing in the existing functional codes on the line, and the code change amount is usually small; the service configuration change type is a change adjustment of the service configuration, and is usually a format adjustment of a configuration item, for example, key value is not involved, and it is simple to issue a change content.
In specific implementation, a received service release work order of a target service is analyzed, a service change type of the target service is determined according to a service change type identifier included in release change information in the service release work order, a release operation corresponding to the target service is executed, and meanwhile, a release monitoring index required to be checked by the target service is determined according to a release monitoring index identifier included in the release change information in the service release work order, so that a corresponding release monitoring index data item, namely a monitoring result of flow data of the released target service, is obtained according to the determined release monitoring index. The release monitoring index data items are all numerical value types, for example, key: value, which is not specifically limited herein.
In specific implementation, the inspection time matched with the target service is determined by identifying the inspection time identifier in the issue monitoring index of the target service, and according to the determined inspection time, all traffic data from the issue of the target service to the inspection time, for example, the access amount of each interface corresponding to the target service, and the like, are acquired by using a monitoring mechanism and are used as the issue result of the target service.
According to the requirements of an actual application scene, adding corresponding expected result options, inspection time options, associated service options, alarm threshold options for triggering rollback, whether global abnormal options exist, whether main process options are influenced, whether automatic rollback options exist, and corresponding sub-level options for the issued monitoring index unit on the platform side of the inspection system, wherein the expected result options comprise sub-level options such as flow data fluctuation trend and processing time which are expected to be set by one or more monitoring items; the examination time options comprise sub-level options of 5m, 10m, 15m, 30m, 1h and the like; the associated service options comprise sub-level options of associated monitoring item 1, associated monitoring item 2, associated monitoring item 3, associated monitoring item 4 and the like; the alert threshold options that trigger the rollback include >1000, <10, < 0, etc. sub-level options associated with sub-level options of the associated service option; and whether the global exception option includes a yes, no sub-level option; whether to influence the yes, no sub-level options included in the main flow options; the automatic rollback option includes a yes, no sub-level option. The sub-level options can also be in a character input form, so that the sub-level options are not specifically set, and therefore, the accuracy of repairing the abnormal service release process or performing rollback change can be effectively improved by further refining the release monitoring index unit.
The expected result is used for checking whether the analysis result of the flow data in the target service release result is matched with the flow data fluctuation trend (stable, rising and falling) or the processing time (change range interval) in the bound monitoring curve by binding the corresponding monitoring curve, so that the automatic checking of the expected result is realized; the checking time is set according to the bound monitoring curve characteristics, so that the checking time is properly prolonged by combining the monitoring curve characteristics in order to avoid misjudgment caused by the jitter of the monitoring curve; the associated service may default to all types of associated monitoring items under the target service, or to an associated monitoring item of a specific type or a specific name, which is not specifically limited herein.
In specific implementation, according to an expected result of monitoring indexes issued in the issuing change information, determining a traffic data fluctuation trend or processing time which is expected to be reached by monitoring items to be checked issued by a service, wherein the traffic data fluctuation trend comprises a smooth, increased and decreased query rate per second (QPS: query-per-second); the processing time includes a time-consuming reduction. Taking the QPS smoothness of the monitoring item to be inspected as an example, first traffic data of the monitoring item to be inspected of a plurality of time nodes within the inspection time 5m before the target service release change is acquired, a first QPS value of the monitoring item to be inspected is determined by using statistical methods such as mean or aggregation, and at the same time, determining a second QPS value of the monitoring item to be inspected by using statistical methods such as mean or aggregation and the like according to second flow data of the monitoring item to be inspected of a plurality of time nodes within the same time 5m after the target service is issued and changed, comparing the first QPS value with the second QPS value, judging whether the flow data fluctuation trend of the monitoring item to be inspected is stable or not, if so, then the checking result of the flow data analysis result in the required range of the target service for issuing the monitoring index is obtained, otherwise, then obtaining the checking result that the analysis result of the flow data is not in the required range of the issuing monitoring index of the target service.
Correspondingly, if the number of the monitoring items to be inspected is multiple, the monitoring items to be inspected are inspected respectively, that is, for each monitoring item to be inspected, the flow data of the corresponding interface before and after the service distribution change is acquired respectively, the inspection result of each monitoring item to be inspected is obtained, and further, corresponding processing operation is executed respectively according to the inspection result of each monitoring item to be inspected, for example, if the inspection result is the inspection result that the fluctuation trend of the flow data of the monitoring item to be inspected or the processing time is within the required range of the distribution monitoring index of the target service, step 206 is executed, otherwise, step 208 is executed directly, and whether the rollback operation is executed is determined according to the service change type of the target service.
In a specific implementation, if the fluctuation trend or the processing time of the traffic data of the monitoring item to be inspected is within the required range of the monitoring index issued by the target service, it is continuously inspected whether the access amount of the associated monitoring item of the target service is within the required range of the monitoring index issued by the target service, if the access amount of the associated monitoring item of the target service does not exceed the corresponding alarm threshold value triggering rollback, the target service is allowed to continue to be issued and the inspection result of the completion of the issuance is obtained, otherwise, the inspection result of whether the global anomaly belongs to the target service is obtained according to the monitored global anomaly time information, and the step 208 is continuously executed.
In the foregoing embodiment, in order to illustrate a specific implementation process of step 207, as an optional manner, step 207 specifically includes:
step 2071, if the traffic data of the service associated with the target service is not within the required range of the release monitoring index of the target service, identifying whether the target service release has a global anomaly according to the release monitoring index of the target service.
Step 2072, if the target service release has global anomaly, continuing to determine whether the global anomaly belongs to the inspection result of the target service according to the monitored time information of the global anomaly.
In the foregoing embodiment, in order to illustrate a specific implementation process of step 207, as an optional manner, step 207 further includes:
step 2073, if the global impact flag in the release monitoring index of the target service is negative, the target service release has no global anomaly, the target service is allowed to continue to release, and a checking result of release completion is obtained.
In specific implementation, if the access quantity of the associated monitoring item of the target service exceeds the corresponding alarm threshold value triggering rollback, whether the target service release has global anomaly is determined according to a global influence index in the release monitoring index of the target service, if the global influence index information includes 'yes', the target service release has the possibility of global anomaly, global anomaly monitoring is performed on the target service, and an inspection result whether the global anomaly belongs to the target service is obtained according to inspection time and the monitored time information of the global anomaly.
Specifically, when a global anomaly is monitored within the checking time, according to the monitored time information of the global anomaly, whether the time type of the anomaly of the time information is matched with the target service type after the target service is issued is judged, if the time type of the anomaly of the time information is matched with the target service after the target service is issued, the checking result that the global anomaly belongs to the target service is obtained, and the step 208 is continuously executed, otherwise, the global anomaly does not belong to the target service, the target service is allowed to be continuously issued, and the checking result that the issuing is completed is obtained.
According to the requirements of the actual application scenario, the global influence index here may also be whether to influence the main process index, that is, whether to influence the identifier included in the main process index information is identified, and further according to the monitored time information influencing the main process operation, whether the time information belongs to the inspection result of the target service is determined, where the issuing of the monitoring index is not specifically limited.
According to the needs of an actual application scenario, the abnormal monitoring items of the global influence indexes include the alarm index item with the highest level and the corresponding set, if any one of the alarm index items with the highest level and/or the alarm index items in the corresponding set is monitored to be abnormal, the global service has abnormal influence, the alarm index item with the highest level and the alarm index items in the corresponding set generally include key indexes such as a network, a flow inlet, a bottom storage, a database and the like, and the specific limitation is not performed here.
And step 208, according to the checking result, executing corresponding rollback operation according to the service change type of the target service.
In the foregoing embodiment, in order to illustrate the specific implementation process of step 208, as an optional manner, step 208 specifically includes:
step 2081, if the analysis result of the flow data in the distribution result is not within the required range of the distribution monitoring index of the target service, determining whether to execute a rollback operation according to the service change type of the target service.
Step 2082, if the traffic data of the service associated with the target service is within the requirement range of the release monitoring index of the target service, determining whether to execute a rollback operation according to the service change type of the target service.
Step 2083, if the global exception belongs to the target service, determining whether to execute a rollback operation according to the service change type of the target service.
In specific implementation, if the service change type of the target service is a conventional function iteration change type, a prompt message indicating that the target service releases an abnormal change is generated, automatic rollback operation cannot be realized at this time, and related technical personnel need to be notified to perform intervention processing. If the service change type of the target service is a new function online change type, sending prompt information of failure of target service release change aiming at the fact that the new function exists in the existing service module and the service change of the historical online record exists, and returning to the previous release version; and if the new function belongs to a new service module, service change of historical online records does not exist, and the new function cannot be returned to the last release version due to no historical online records, a corresponding processing means is required to be taken as a service entrance offline, so that the back-end service stops running. If the service change type of the target service is the Bugfix change type, the verification scene and the verification method are easy to confirm, so that the prompt message of the target service release change failure is sent, and the target service release change is directly returned to the last release version. If the service change type of the target service is the service configuration change type, the service change content is simple, so that the prompt message of failure of target service release change is sent, and the target service release change is directly returned to the previous release version.
By applying the method provided by the embodiment, the checking of the target service release result is realized according to the service change type and the release monitoring index of the target service, and whether the target service executes the corresponding rollback operation is further determined based on the service change type and the release monitoring index of the target service. Therefore, the service change type and the release monitoring index are set for the existing service release change, and the automatic check of the service release result is realized, so that the manual intervention and judgment in the existing service release flow are effectively simplified, the check result is intelligently obtained, whether the corresponding rollback operation is executed or not is intelligently obtained, the corresponding loss caused by the online abnormality of the service is reduced, the working efficiency of repairing the abnormality or performing the rollback change in the existing service release flow is effectively improved, and the time cost and the fund investment cost are reduced.
Further, as a specific implementation of the method shown in fig. 1 and fig. 2, an embodiment of the present application provides an apparatus for examining a service distribution result, as shown in fig. 3, the apparatus includes: identification module 32, monitoring module 33, and verification module 34.
The identification module 32 is used for identifying the service change type and the release monitoring index of the target service according to the release change information of the target service; the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service.
And the monitoring module 33 is configured to obtain a release result of the target service according to the monitored flow data after the target service is released.
And the checking module 34 is configured to check the distribution result according to the service change type and the distribution monitoring indicator of the identified target service, so as to obtain a checking result.
In a specific application scenario, as shown in fig. 4, the apparatus further includes: a creating unit 31.
The creating module 31 is configured to create a service change type unit of a service and a release monitoring index unit associated with the service change type unit.
In a specific application scenario, the monitoring module 33 includes: time unit 331, acquisition unit 332.
The time unit 331 is specifically configured to determine an inspection time for inspecting the target service according to the identified distribution monitoring indicator of the target service.
The obtaining unit 332 is specifically configured to monitor the traffic data after the target service is issued, obtain the traffic data of the target service in the check time, and use the traffic data as the issue result of the target service.
In a specific application scenario, the checking module 34 includes: a first checking unit 341, a second checking unit 342, and a third checking unit 343.
The first checking unit 341 is specifically configured to obtain, according to the issue monitoring indicator of the target service, a checking result indicating whether an analysis result of the traffic data in the issue result is within a required range of the issue monitoring indicator of the target service.
The second checking unit 342 is specifically configured to, if the analysis result of the traffic data in the distribution result is within the required range of the distribution monitoring indicator of the target service, obtain a checking result that whether the traffic data of the service related to the target service is continuously checked in the required range of the distribution monitoring indicator of the target service.
The third checking unit 343 is specifically configured to, if the traffic data of the service related to the target service is not within the requested range of the monitoring indicator issued by the target service, obtain, according to the monitored time information of the abnormality of the monitoring indicator issued, an inspection result of whether the global abnormality belongs to the target service.
In a specific application scenario, the apparatus further includes: and a rollback module 35.
And a rollback module 35, configured to execute a corresponding rollback operation according to the service change type of the target service according to the inspection result.
In a specific application scenario, the rollback module 35 includes: a first rollback unit 351, a second rollback unit 352, and a second rollback unit 353.
A first rollback unit 351, configured to determine whether to execute a rollback operation according to the service change type of the target service if the analysis result of the traffic data in the distribution result is not within the required range of the distribution monitoring index of the target service.
A second rollback unit 352, configured to determine whether to execute a rollback operation according to a service change type of the target service if traffic data of the service associated with the target service is within a required range of a release monitoring index of the target service.
A third rollback unit 353, configured to determine whether to execute a rollback operation according to a service change type of the target service if the global exception belongs to the target service.
In a specific application scenario, the third checking unit 343 includes: if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service, identifying whether the target service release has global abnormality or not according to the release monitoring index of the target service; if the target service is issued with global abnormity, whether the global abnormity belongs to the inspection result of the target service is judged according to the monitored time information of the global abnormity.
In a specific application scenario, the third checking unit 343 further includes: if the global influence identifier in the target service release monitoring index is negative, the target service release has no global exception, the target service is allowed to continue releasing, and a checking result of the release completion is obtained.
It should be noted that other corresponding descriptions of the functional modules and functional units related to the checking apparatus for a service distribution result provided in this embodiment may refer to the corresponding descriptions in fig. 1 and fig. 2, and are not described herein again.
By applying the checking device for the service release result, after receiving the query request from the user, entity identification is carried out on the key words in the received query request to obtain key word entities, meanwhile, the similarity calculation of the multi-dimensional identification result is carried out on the key word entities and the service information in the preset database to obtain multi-dimensional similarity results, and the target service information matched with the key word entities is obtained according to the multi-stage similarity results of the key word entities and the service information in the preset database and the multi-dimensional similarity results, so that the operation instruction corresponding to the query request is generated according to the obtained target service information. Therefore, through carrying out similarity calculation of multi-dimensional recognition results and multi-stage similarity calculation on two sides, structured and more accurate entity matching and recognition with service semantics can be obtained, more accurate query results can be generated, the query experience of a user is effectively improved, and the technical problem of lower keyword query accuracy under the condition that a knowledge graph is not available or is incomplete is effectively avoided.
Based on the methods shown in fig. 1 and fig. 2, correspondingly, the embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the method for checking the service distribution result shown in fig. 1 and fig. 2.
Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, or the like), and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, or the like) to execute the entity matching method of each implementation scenario of the present application.
Based on the method shown in fig. 1 and fig. 2 and the virtual device embodiment shown in fig. 3 and fig. 4, in order to achieve the above object, an embodiment of the present application further provides an electronic device, which may be specifically a server, a personal computer, a tablet computer, a smart phone, a smart watch, a POS device, or other network devices, where the terminal device includes a storage medium and a processor; a storage medium for storing a computer program; a processor for executing a computer program to implement the above-described method of pinging a service issuance result as shown in fig. 1 and 2.
Optionally, the above entity devices may further include a user interface, a network interface, a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WI-FI module, and the like. The user interface may include a Display screen (Display), an input unit such as a keypad (Keyboard), etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), etc.
It will be understood by those skilled in the art that the physical device structure of an electronic device provided in the present embodiment is not limited to the above physical device, and may include more or less components, or combine some components, or arrange different components.
The storage medium may further include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the two physical devices described above, supporting the operation of the information processing program as well as other software and/or programs. The network communication module is used for realizing communication among components in the storage medium and communication with other hardware and software in the information processing entity device.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus a necessary general hardware platform, and can also be implemented by hardware. Through applying the technical scheme of the application, compared with the prior art, the embodiment sets the service change type and the release monitoring index for the existing service release change, and realizes the automatic check of the service release result, thereby effectively simplifying the human intervention and judgment in the existing service release process, intelligently acquiring the check result and whether to execute the corresponding rollback operation, reducing the corresponding loss caused by the online abnormality of the service, effectively improving the work efficiency of repairing the abnormality or performing the rollback change of the existing service release process, and reducing the time cost and the capital investment cost.
Those skilled in the art will appreciate that the figures are merely schematic representations of one preferred implementation scenario and that the blocks or flow diagrams in the figures are not necessarily required to practice the present application. Those skilled in the art will appreciate that the modules in the devices in the implementation scenario may be distributed in the devices in the implementation scenario according to the description of the implementation scenario, or may be located in one or more devices different from the present implementation scenario with corresponding changes. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.
The above application serial numbers are for description purposes only and do not represent the superiority or inferiority of the implementation scenarios. The above disclosure is only a few specific implementation scenarios of the present application, but the present application is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present application.
Claims (16)
1. A method for checking a service distribution result, comprising:
identifying a service change type and a release monitoring index of the target service according to the release change information of the target service;
obtaining a publishing result of the target service according to the monitored flow data after the target service is published;
according to the service change type and the issuing monitoring index of the target service, which are obtained through identification, the issuing result is checked to obtain a checking result, wherein the checking result whether the analysis result of the flow data in the issuing result is within the required range of the issuing monitoring index of the target service is obtained according to the issuing monitoring index of the target service;
the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service.
2. The method of claim 1, wherein before the step of identifying the service change type and the release monitoring index of the target service according to the release change information of the target service, the method further comprises:
the system comprises a service change type unit for creating service and a release monitoring index unit related to the service change type unit.
3. The method according to claim 1 or 2, wherein the obtaining of the release result of the target service according to the monitored flow data after the release of the target service specifically comprises:
determining the checking time for checking the target service according to the identified release monitoring index of the target service;
and monitoring the flow data after the target service is issued, acquiring the flow data of the target service in the checking time, and taking the flow data as an issuing result of the target service.
4. The method according to claim 3, wherein the examining the distribution result according to the identified service change type and distribution monitoring index of the target service to obtain an examination result specifically comprises:
if the analysis result of the flow data in the release result is within the required range of the release monitoring index of the target service, obtaining an inspection result for continuously inspecting whether the flow data of the associated service of the target service is within the required range of the release monitoring index of the target service;
and if the flow data of the associated service of the target service is not in the required range of the target service for issuing the monitoring index, obtaining an inspection result whether the global anomaly belongs to the target service or not according to the monitored time information of the global anomaly.
5. The method of claim 4, further comprising:
according to the checking result, executing corresponding rollback operation according to the service change type of the target service, which specifically comprises the following steps:
if the analysis result of the flow data in the issuing result is not in the requirement range of the issuing monitoring index of the target service, determining whether to execute rollback operation according to the service change type of the target service;
if the flow data of the associated service of the target service is in the requirement range of the release monitoring index of the target service, determining whether to execute rollback operation according to the service change type of the target service;
and if the global exception belongs to the target service, determining whether to execute rollback operation according to the service change type of the target service.
6. The method according to claim 4, wherein if the traffic data of the service associated with the target service is not within the range of the requirement for the target service to issue the monitoring index, obtaining, according to the monitored time information of the global anomaly, an inspection result of whether the global anomaly belongs to the target service, specifically comprising:
if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service, identifying whether the target service release has global abnormality or not according to the release monitoring index of the target service;
if the target service is issued with global abnormity, whether the global abnormity belongs to the inspection result of the target service is judged according to the monitored time information of the global abnormity.
7. The method of claim 6, further comprising;
if the global influence identifier in the target service release monitoring index is negative, the target service release has no global exception, the target service is allowed to continue releasing, and a checking result of the release completion is obtained.
8. An apparatus for examining a result issued by a service, comprising:
the identification module is used for identifying the service change type and the release monitoring index of the target service according to the release change information of the target service;
the monitoring module is used for obtaining a publishing result of the target service according to the monitored flow data after the target service is published;
the checking module is used for checking the issuing result according to the service change type and the issuing monitoring index of the target service, which are obtained through identification, so as to obtain a checking result, wherein the first checking unit is used for obtaining the checking result whether the analysis result of the flow data in the issuing result is within the required range of the issuing monitoring index of the target service according to the issuing monitoring index of the target service;
the issuing monitoring index is a checking index for determining whether the target service executes the rollback operation according to the service change type of the target service.
9. The apparatus of claim 8, further comprising:
the system comprises a creating module and a monitoring module, wherein the creating module is used for creating a service change type unit of the service and a release monitoring index unit related to the service change type unit.
10. The device according to claim 8 or 9, wherein the monitoring module specifically comprises:
the time unit is used for determining the checking time for checking the target service according to the identified release monitoring index of the target service;
and the acquisition unit is used for monitoring the flow data after the target service is issued, acquiring the flow data of the target service in the checking time and taking the flow data as an issuing result of the target service.
11. The apparatus of claim 10, wherein the ping module specifically comprises:
a second checking unit, configured to obtain a checking result of continuously checking whether traffic data of a service associated with the target service is within a required range of the release monitoring index of the target service if an analysis result of the traffic data in the release result is within the required range of the release monitoring index of the target service;
and the third checking unit is used for obtaining a checking result whether the global anomaly belongs to the target service or not according to the monitored time information of the global anomaly if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service.
12. The apparatus of claim 11, further comprising:
a rollback module, configured to execute a corresponding rollback operation according to the service change type of the target service according to the inspection result, specifically including:
a first rollback unit, configured to determine whether to execute a rollback operation according to a service change type of the target service if an analysis result of the flow data in the publishing result is not within a required range of a publishing monitoring index of the target service;
the second rollback unit is used for determining whether to execute rollback operation according to the service change type of the target service if the traffic data of the associated service of the target service is within the requirement range of the release monitoring index of the target service;
and the third rollback unit is used for determining whether to execute rollback operation according to the service change type of the target service if the global exception belongs to the target service.
13. The apparatus according to claim 11, wherein the third verification unit specifically includes:
if the flow data of the associated service of the target service is not in the required range of the release monitoring index of the target service, identifying whether the target service release has global abnormality or not according to the release monitoring index of the target service;
if the target service is issued with global abnormity, whether the global abnormity belongs to the inspection result of the target service is judged according to the monitored time information of the global abnormity.
14. The apparatus of claim 13, wherein the third verification unit further comprises;
if the global influence identifier in the target service release monitoring index is negative, the target service release has no global exception, the target service is allowed to continue releasing, and a checking result of the release completion is obtained.
15. An electronic device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the method for verifying a service issuance result according to any one of claims 1 to 7 when executing the program.
16. A computer-readable storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to the method for pinging a service issuance result according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010240543.6A CN111506455B (en) | 2020-03-31 | 2020-03-31 | Checking method and device for service release result |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010240543.6A CN111506455B (en) | 2020-03-31 | 2020-03-31 | Checking method and device for service release result |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111506455A CN111506455A (en) | 2020-08-07 |
| CN111506455B true CN111506455B (en) | 2021-06-25 |
Family
ID=71877899
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010240543.6A Active CN111506455B (en) | 2020-03-31 | 2020-03-31 | Checking method and device for service release result |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111506455B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148329B (en) * | 2020-09-18 | 2023-03-28 | 湖南联盛网络科技股份有限公司 | Code version automatic updating method and device, computer equipment and storage medium |
| CN116506319B (en) * | 2023-06-27 | 2023-09-19 | 天津通信广播集团有限公司 | Method, device and medium for monitoring running state of PIS hardware equipment of subway operation system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002108838A (en) * | 2000-10-02 | 2002-04-12 | Ntt Comware Corp | Device and method for carrying out agent |
| CN103220163A (en) * | 2012-01-19 | 2013-07-24 | 阿里巴巴集团控股有限公司 | Updating method and system of configuring information |
| CN103440460A (en) * | 2013-09-09 | 2013-12-11 | 中国农业银行股份有限公司 | Application system change validation method and system |
| CN108170448A (en) * | 2017-12-26 | 2018-06-15 | 车智互联（北京）科技有限公司 | The system that a kind of automatic high-efficiency carries out software upgrading version publication |
| CN109391512A (en) * | 2018-09-28 | 2019-02-26 | 阿里巴巴集团控股有限公司 | A kind of service issuing method, device and electronic equipment |
| CN109783311A (en) * | 2018-12-14 | 2019-05-21 | 平安普惠企业管理有限公司 | Monitor processing method, device, equipment and the readable storage medium storing program for executing of breakpoint behavior |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108376118B (en) * | 2018-02-09 | 2021-07-13 | 腾讯科技（深圳）有限公司 | Service distribution system, method, device and storage medium |
| CN109831357B (en) * | 2019-01-30 | 2020-12-29 | 北京大米科技有限公司 | Service verification method, device, storage medium and server |
-
2020
- 2020-03-31 CN CN202010240543.6A patent/CN111506455B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002108838A (en) * | 2000-10-02 | 2002-04-12 | Ntt Comware Corp | Device and method for carrying out agent |
| CN103220163A (en) * | 2012-01-19 | 2013-07-24 | 阿里巴巴集团控股有限公司 | Updating method and system of configuring information |
| CN103440460A (en) * | 2013-09-09 | 2013-12-11 | 中国农业银行股份有限公司 | Application system change validation method and system |
| CN108170448A (en) * | 2017-12-26 | 2018-06-15 | 车智互联（北京）科技有限公司 | The system that a kind of automatic high-efficiency carries out software upgrading version publication |
| CN109391512A (en) * | 2018-09-28 | 2019-02-26 | 阿里巴巴集团控股有限公司 | A kind of service issuing method, device and electronic equipment |
| CN109783311A (en) * | 2018-12-14 | 2019-05-21 | 平安普惠企业管理有限公司 | Monitor processing method, device, equipment and the readable storage medium storing program for executing of breakpoint behavior |
Non-Patent Citations (2)
| Title |
|---|
| 基于多版本服务切换的软件动态更新系统的设计与实现;杜耕;《中国优秀硕士学位论文全文数据库》;20111015;全文 * |
| 谈版本发布中的回退(9.5);人月神话;《新浪博客http://blog.sina.com.cn/s/blog.493a84550102z3c7.html》;20190905;第1-3页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111506455A (en) | 2020-08-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108683562B (en) | Anomaly detection positioning method and device, computer equipment and storage medium | |
| CN110096430B (en) | Third party SDK access test method, device, terminal and storage medium | |
| CN109495291B (en) | Calling abnormity positioning method and device and server | |
| CN111506455B (en) | Checking method and device for service release result | |
| CN110275878B (en) | Service data detection method and device, computer equipment and storage medium | |
| CN111160329A (en) | Root cause analysis method and device | |
| CN109408361A (en) | Monkey tests restored method, device, electronic equipment and computer readable storage medium | |
| CN115757150A (en) | Production environment testing method, device, equipment and storage medium | |
| CN109542722A (en) | Anomaly analysis processing method, device and storage medium | |
| CN111143325B (en) | Data acquisition monitoring method, monitoring device and readable storage medium | |
| CN110580220B (en) | Method for measuring code segment execution time and terminal equipment | |
| CN114595765A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN116107789A (en) | Method for monitoring and analyzing application fault reasons and storage medium | |
| CN112948262A (en) | System test method, device, computer equipment and storage medium | |
| CN110011845B (en) | Log collection method and system | |
| CN116645082A (en) | System inspection method, device, equipment and storage medium | |
| CN111813872A (en) | Fault troubleshooting model generation method, device and equipment | |
| CN116610967A (en) | Bank system abnormality detection method, device and equipment based on clustering | |
| CN115794473A (en) | Root cause alarm positioning method, device, equipment and medium | |
| CN113781068B (en) | Online problem solving method, device, electronic equipment and storage medium | |
| CN114691768A (en) | Data processing method, accounting system and related equipment | |
| CN111835566A (en) | System fault management method, device and system | |
| CN110413516B (en) | Method and device for identifying slow SQL codes and electronic equipment | |
| CN109840213B (en) | Test data creating method, device, terminal and storage medium for GUI test | |
| CN109828983B (en) | PG database processing method, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |