CN116860381A - Method for releasing visual micro-service gray scale - Google Patents
Method for releasing visual micro-service gray scale Download PDFInfo
- Publication number
- CN116860381A CN116860381A CN202311127160.8A CN202311127160A CN116860381A CN 116860381 A CN116860381 A CN 116860381A CN 202311127160 A CN202311127160 A CN 202311127160A CN 116860381 A CN116860381 A CN 116860381A
- Authority
- CN
- China
- Prior art keywords
- service
- service instance
- instance
- block diagram
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000000007 visual effect Effects 0.000 title claims abstract description 24
- 238000000034 method Methods 0.000 title claims abstract description 18
- 238000010586 diagram Methods 0.000 claims abstract description 69
- 238000004519 manufacturing process Methods 0.000 claims abstract description 14
- 238000012360 testing method Methods 0.000 claims description 15
- 238000012800 visualization Methods 0.000 claims description 9
- 238000012423 maintenance Methods 0.000 claims description 8
- 239000003086 colorant Substances 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 claims description 4
- 235000014510 cooky Nutrition 0.000 claims description 3
- 229910003460 diamond Inorganic materials 0.000 claims description 3
- 239000010432 diamond Substances 0.000 claims description 3
- 238000005070 sampling Methods 0.000 claims description 3
- 238000001514 detection method Methods 0.000 description 2
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- User Interface Of Digital Computer (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for releasing visual micro-service gray scale, which comprises the steps of firstly displaying a service gateway, a service cluster, a service instance, a release strategy and a production call relation through a block diagram or an icon, and establishing a service topological graph in a visual system in a dragging mode; then, representing all metadata by using a block diagram and a text description, clicking a block diagram or an icon of a service cluster by right click to open a configuration center, and pulling down the metadata in the configuration center to configure routing rules so as to generate a routing strategy; after the gray level user requests the service, the service gateway receives the user information and matches the corresponding routing strategy, the block diagram of the service cluster is clicked by the left key to open the service instance detail bullet frame, the flow weight of the appointed service instance is adjusted by dragging to be on line, then the flow weight of the new version service instance is gradually adjusted to transfer all the flow to the new version service instance.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a method for releasing visual micro-service gray scale.
Background
Microservices are an emerging software architecture that splits a large single application and service into tens of supporting microservices, and a microservice policy allows for easier operation, which can extend individual components rather than the entire application stack, thereby meeting service level agreements.
Based on the above-mentioned advantages of the micro-service, the micro-service is becoming a current hot topic and is being popularized by more and more enterprises. In the micro-service architecture, gray level release provides effective guarantee for smooth upgrade of the micro-service of rapid iteration without stopping. Gray release is a release mode of smooth transition upgrade of service. The existing gray release is configured by writing properties, yaml and other files, or through a configuration center, the configuration items are edited and modified by using a text editing box through XML, JSON, YAML, so that the release of the service is achieved. The configuration mode extremely tests the condition of operation and maintenance personnel in grasping system configuration items, the operation and maintenance personnel cannot see the on-line service at a glance, the configuration is invalid due to the fact that the operation and maintenance personnel are wrongly matched, and the operation is complex and the efficiency is low.
Disclosure of Invention
The invention aims to provide a method for visually releasing micro service gray scale, which displays micro service examples and service metadata information on a visual interface in the form of a block diagram or an icon and solves the problems that the configuration mode of the existing gray scale release cannot be clear at a glance, the operation is complex and the efficiency is low.
To achieve the above object, the solution of the present invention is: a method for visually releasing the gray scale of a micro-service comprises the following steps:
s1, displaying a service gateway, a service cluster, a service instance, a release strategy and a production call relation in a distributed system through block diagrams or icons with different colors and different shapes, and establishing the production call relation between the service gateway and the service and between the service and the service in a visual system in a mode of dragging the block diagrams or the icons to form a service topological diagram;
s2, representing all metadata representing service information by using a block diagram and a text description through a metadata block diagram server, clicking a block diagram or an icon of a service cluster to open a configuration center, and carrying out configuration of a routing rule by dragging the block diagram or the icon according to the metadata information in the configuration center so as to generate a routing strategy;
s3, the gray level user requests service, the service gateway receives user information and matches a corresponding routing strategy, an operation and maintenance personnel clicks a block diagram of the service cluster through a left key to open a service instance detail popup frame, the service instance detail popup frame displays service instance information and flow weight proportion of all service instances in the service cluster, the flow weight of a designated service instance is adjusted through dragging, the designated service instance is enabled to be gray and is on line, then the flow weight of a new version service instance is gradually increased, the flow weight of an old version service instance is gradually reduced, and finally all flow is migrated from the old version service instance to the new version service instance, so that the lossless downlink old version service instance is realized.
Further, after the routing policy in step S3 is generated, a plurality of test cases are created, the test cases automatically complete the routing policy test according to the routing rules, a test result document is automatically generated through a preset estimated value and collected sampling information, whether the routing policy accords with the expectation or not is analyzed through verification and detection, and finally a report is generated, if the routing policy accords with the expectation, the flow weight is adjusted, and all flows are migrated from the old version service instance to the new version service instance; and if the routing strategy is not in accordance with the expectations, adjusting the routing strategy until the routing strategy is in accordance with the expectations.
Further, in steps S1 and S2, the service gateway is displayed by a square block diagram with a gateway icon, the service cluster is displayed by a square block diagram, the service instance is displayed by a circular diagram, the distribution policy is displayed by a diamond diagram, the production calling relationship is displayed by an arrow, and the metadata is represented by an elliptic block diagram.
Further, in step S2, the metadata includes base metadata including a version number and a service name, and request information metadata including a client IP, a request header, a request Cookie, a request parameter, and a request address.
Further, in step S2, the configuration of the routing rule configures one or more routing policies according to the traffic weight, the client IP, the request address, the request parameter, the request header, the version number, and the metadata information of the service name, and after the routing policies are validated and the service instance feature hits the routing policies, the traffic will migrate to the new version service instance.
Further, in step S3, a data request generates a link through the service gateway under the branching condition of flowing through a plurality of different service clusters, the data traffic is color-marked in each service instance flowing through, the color of the unused service instance is gray, the normally requested service instance is green, and the abnormally requested service instance is marked with red.
Further, one or more service instances are provided in one service cluster, and each service instance is distinguished into different versions by a marked metadata version number.
Further, in step S1, the visualization system includes a Nacos component on a Spring Cloud-based micro service framework, a custom load scheduler, a d3.Js or Echarts chart component used by a reaction front end framework, and a dynamic service discovery, configuration management and service management visualization platform for Cloud native applications is built by the Nacos component, and service management, routing configuration and monitoring are performed on the visualization platform; the self-defined load scheduler matches the corresponding service instance according to the metadata information and the flow weight of the acquired service; a B/S-based visual block diagram configuration interface is developed through a D3.js or Echarts chart component, and various service metadata information, traffic, service gateways and service clusters are displayed through block diagrams and icon forms with different shapes.
After the scheme is adopted, the beneficial effects of the invention are as follows:
the invention displays the service gateway, the service cluster, the service instance, the release strategy and the production calling relation in the distributed system through the block diagrams or icons with different colors and different shapes, all metadata are represented by the block diagrams and the text descriptions, the production calling relation between the gateway and the service cluster and between different service clusters is presented in a topological diagram mode, the operation and maintenance personnel has a clear view on the online service, the operation and maintenance personnel only needs to open a visual system, monitors the service topological diagram in real time through a visual interface, and can finish the operations of the service instance such as online and offline, arrangement, monitoring, flow switching and the like by clicking, dragging and pulling a mouse, thereby simplifying the work of the operation and maintenance personnel, improving the efficiency, and being simple, safe and efficient.
Drawings
FIG. 1 is a flow chart of a method for gray level publication of a microservice of the present invention;
FIG. 2 is a block diagram of the architecture of the system of the present invention;
FIG. 3 is a diagram of a relationship represented by a block diagram or icon of the present invention;
FIG. 4 is a schematic diagram of a metadata block diagram server page according to the present invention;
FIG. 5 is a block diagram showing a service cluster b according to the present invention;
FIG. 6 is a service topology diagram of an embodiment of the present invention;
FIG. 7 is a schematic diagram of a routing policy configuration page of the present invention;
FIG. 8 is a schematic diagram of a page of a link log of the present invention;
FIG. 9 is a detailed bullet box schematic of a service instance of the service cluster a of the present invention;
fig. 10 is a detailed bullet frame diagram of a service instance of the service cluster b according to the present invention.
Detailed Description
The invention will be described in detail with reference to the accompanying drawings and specific embodiments.
As shown in fig. 1-10, the present invention provides a method for visual micro-service gray scale distribution, comprising the following steps:
s1, displaying a service gateway, a service cluster, a service instance, a release strategy and a production call relation in a distributed system through block diagrams or icons with different colors and different shapes, and establishing the production call relation between the service gateway and the service and between the service and the service in a visual system in a mode of dragging the block diagrams or the icons to form a service topological diagram, wherein the service topological diagram is shown in FIG. 6;
as shown in fig. 3, the service gateway may be displayed by a square block diagram with a gateway icon, the service cluster may be displayed by a square block diagram, the service instance may be displayed by a circular diagram, the release policy may be displayed by a diamond diagram, the production calling relationship may be displayed by an arrow, and the release policies between the service gateway and the service clusters and between different service clusters are connected by an arrow;
s2, as shown in FIG. 4, representing all metadata representing service information by using a block diagram and a text description through a metadata block diagram server, wherein the metadata comprises basic metadata and request information metadata, the basic metadata comprises a version number and a service name, and the request information metadata comprises a client IP, a request header, a request Cookie, a request parameter, a request address and the like, and is represented by using an elliptic block diagram and text in the elliptic block diagram; right clicking the block diagram or icon of the service cluster to open a configuration center, which is also a visual popup interface, as shown in fig. 7, in which the configuration of the routing rule can be performed according to the metadata by dragging the block diagram or icon, thereby generating a routing policy;
s3, gray level user request service, service gateway receives user information and matches corresponding routing strategy, with emphasis on FIG. 6, one user request service often needs to call multiple services at the same time, for example, when one user requests a service, b service and c service may need to be called, then b service and c service are producers, a service is consumer, they are related by multiple single service clusters into link relation of multiple service clusters, at this time, one service cluster may have one or more instances at the same time, each instance distinguishes different versions through a marked metadata version number, for example, in service cluster b, as shown in FIG. 5, service instance with new version: [ v1.1]10.83.3.1, [ v1.1]10.83.3.2, [ v1.1]10.83.3.3, and old version service instances: [ v1.0]10.83.3.4, [ v1.0]10.83.3.5, [ v1.0]10.83.3.6, the new version service instance corresponds to the new version gray test user policy, and the old version service instance corresponds to the original policy;
a data request generates a link under the condition of branching flowing through a plurality of different service clusters through a service gateway, data traffic is marked by adopting a color or other modes when flowing through each service instance, in one embodiment, service instances of different conditions are marked by adopting a color, the color of an unused service instance is gray, namely, the service instance which is not online is displayed by a gray circular graph, the service instance which is normally requested is green, namely, the normal service instance is displayed by a green circular graph, and the service instance which is abnormally requested is marked by red, namely, the service instance which is failed is displayed by a red circular graph; in another embodiment, as shown in fig. 3, normally requested service instances are marked with solid hollow circles, non-online service instances are marked with dotted hollow circles, and failed service instances are marked with solid circles; thus, as shown in fig. 6, in the service cluster a, service instances [ v1.0]10.83.3.4, [ v1.0]10.83.3.5, [ v1.0]10.83.3.6 are normal request service instances, [ v1.1]10.83.3.1 are service instances which are not online, and [ v1.0]10.83.3.3 are fault service instances, so that the state and depth of each service instance are clear at a glance by not only graphically representing the service instance but also marking the service instance by color or other means;
the service instance does not have a request flow immediately after being started, the service instance presents gray in a corresponding service cluster block diagram immediately after being started, at this time, an operator needs to open a service instance detail popup frame by clicking the service cluster block diagram on the left, as shown in fig. 9 and 10, the service instance detail popup frame is also a visual interface, the service instance detail popup frame displays all service instance information and flow weight proportion in the service cluster, the flow weight is displayed in a progress bar mode, the flow weight can be adjusted through dragging left and right, the designated service instance has the flow weight through dragging left and right, the designated service instance gray is enabled to be online, the designated service instance can comprise a new version service instance and an old version service instance, then the flow weight of the service instance is gradually increased, the flow weight of the old version service instance is gradually reduced, the old version service instance is offline under the condition that no flow exists, finally, all flow is migrated from the old version service instance to the service instance, the new version of the offline version service instance is realized, and gray release is completed.
In addition, after the service instance is started, the new version service instance is not only on line, but also can be used simultaneously, and then the flow weight of the new version service instance is gradually increased and the flow weight of the old version service instance is gradually decreased, so that the flow of the old version service instance is migrated to the new version service instance without loss, and the lossless off-line old version service instance is realized.
Referring to fig. 7, the bullet frame of the configuration center has a policy name, a policy drop-down selection frame, an insertion production service key and an insertion condition key; the configuration of the routing rule may configure one or more policies according to the traffic weight, the client IP, the request address, the request parameter, the request header, and the user login information, that is, the version number and the service name, taking the configuration policy shown in fig. 7 as an example, the routing policy name is: 10.83 beginning network segment can access new function 1 of service b, namely, new version service instance of online service cluster b, drag and insert service cluster a, click and insert condition metadata, open metadata block diagram server, drag and insert user's IP, and set up the condition containing 10.83 IP address, click and insert production service, search service cluster b, pick up new version service instance, deploy new version service instance to server, set up the flow weight of each new version service instance, click strategy drop down selection frame selection weight, generate routing strategy; after the gray level user requests a service, the service gateway matches whether the IP address of the user accords with the 10.83 head according to the routing strategy, if so, the routing strategy is downloaded step by using the routing strategy mode service gateway created above, the gateway requests the service cluster a, the service cluster a requests an instance of the new function 1 of the service b according to the routing strategy when the service cluster b is called, the traffic is regulated to enable the traffic weight of the new version service instance to reach the value set by the routing strategy in the process from the service cluster a to the service set weight b, the routing strategy is effective, the service instance characteristics hit the condition of the routing strategy, and the traffic is migrated to the new version service instance to realize the online of the new version service instance.
Referring to fig. 8 with emphasis, clicking on a link may reveal log information of all services of the link, including request time, request status, client information, request content, service topology, etc., which may be revealed in the form of a paging table.
As a preferred scheme, after the routing policy in step S3 is generated, test case management may be performed, multiple test cases are created, that is, a service is requested by a simulated gray user, the test cases automatically complete the test of the routing policy according to the routing rule, a test result document is automatically generated through a preset pre-estimated value and collected sampling information, whether the routing policy accords with the expectation or not is analyzed through verification and detection, and finally a report is generated, if the routing policy accords with the expectation, gray release is performed, the traffic weight is adjusted, and all traffic is migrated from the old version service instance to the new version service instance; and if the routing strategy is not in accordance with the expectations, adjusting the routing strategy until the routing strategy is in accordance with the expectations.
The visualization system used in the invention comprises a Nacos component based on a Spring Cloud micro-service framework, a custom load scheduler, a D3.Js or Echarts chart component used by a reaction front-end framework, and a dynamic service discovery, configuration management and service management visualization platform of a Cloud native application can be constructed by the Nacos component, and service management, namely a service topology diagram, route configuration and monitoring, can be established on the visualization platform; the self-defined load scheduler is an expansion of the load scheduler (LoadBalancer, ribbon), and can be matched with a corresponding set service instance according to the acquired metadata information and the flow weight of the service, so that the routing rule can be adjusted in a configuration center and the flow weight can be adjusted in a service instance detail bullet frame; through the D3.js or Echarts chart component, a B/S-based visual block diagram configuration interface can be developed, and various service metadata information, traffic, service gateways and service clusters can be displayed through different shapes of block diagrams, icons and the like.
The above embodiments are only preferred embodiments of the present invention, and are not limited to the present invention, and all equivalent changes made according to the design key of the present invention fall within the protection scope of the present invention.
Claims (8)
1. A method for visually releasing the gray scale of a micro-service is characterized by comprising the following steps: the method comprises the following steps:
s1, displaying a service gateway, a service cluster, a service instance, a release strategy and a production call relation in a distributed system through block diagrams or icons with different colors and different shapes, and establishing the production call relation between the service gateway and the service and between the service and the service in a visual system in a mode of dragging the block diagrams or the icons to form a service topological diagram;
s2, representing all metadata representing service information by using a block diagram and a text description through a metadata block diagram server, clicking a block diagram or an icon of a service cluster to open a configuration center, and carrying out configuration of a routing rule by dragging the block diagram or the icon according to the metadata information in the configuration center so as to generate a routing strategy;
s3, the gray level user requests service, the service gateway receives user information and matches a corresponding routing strategy, an operation and maintenance personnel clicks a block diagram of the service cluster through a left key to open a service instance detail popup frame, the service instance detail popup frame displays service instance information and flow weight proportion of all service instances in the service cluster, the flow weight of a designated service instance is adjusted through dragging, the designated service instance is enabled to be gray and is on line, then the flow weight of a new version service instance is gradually increased, the flow weight of an old version service instance is gradually reduced, and finally all flow is migrated from the old version service instance to the new version service instance, so that the lossless downlink old version service instance is realized.
2. The method for visual micro-service gray scale distribution according to claim 1, wherein: creating a plurality of test cases after generating the routing strategy in the step S3, automatically completing the routing strategy test by the test cases according to the routing rule, automatically generating a test result document through a preset estimated value and collected sampling information, checking, detecting and analyzing whether the routing strategy accords with the expectation and finally generating a report, and if the routing strategy accords with the expectation, adjusting the flow weight and transferring all the flows from the old version service instance to the new version service instance; and if the routing strategy is not in accordance with the expectations, adjusting the routing strategy until the routing strategy is in accordance with the expectations.
3. The method for visual micro-service gray scale distribution according to claim 1, wherein: in steps S1 and S2, the service gateway is displayed by a square block diagram with a gateway icon, the service cluster is displayed by a square block diagram, the service instance is displayed by a circular diagram, the distribution policy is displayed by a diamond diagram, the production calling relationship is displayed by an arrow, and the metadata is represented by an elliptic block diagram.
4. The method for visual micro-service gray scale distribution according to claim 1, wherein: in step S2, the metadata includes basic metadata including a version number and a service name, and request information metadata including a client IP, a request header, a request Cookie, a request parameter, and a request address.
5. The method for visual micro-service gray scale distribution according to claim 4, wherein: in step S2, the configuration of the routing rule configures one or more routing policies according to the traffic weight, the client IP, the request address, the request parameter, the request header, the version number and the metadata information of the service name, and after the routing policies are validated and the service instance feature hits the routing policies, the traffic will migrate to the new version service instance.
6. The method for visual micro-service gray scale distribution according to claim 1, wherein: in step S3, a data request generates a link through the service gateway under the condition of branching of a plurality of different service clusters, the data traffic is color-marked when flowing through each service instance, the color of the unused service instance is gray, the normally requested service instance is green, and the abnormally requested service instance is marked with red.
7. The method for visual micro-service gray scale distribution according to claim 1, wherein: one service cluster has one or more service instances therein, each of which distinguishes between different versions by a signed metadata version number.
8. The method for visual micro-service gray scale distribution according to claim 1, wherein: in step S1, the visualization system includes a Nacos component on a Spring Cloud micro service framework, a custom load scheduler, and a d3.Js or Echarts chart component used by a reaction front end framework, and a dynamic service discovery, configuration management and service management visualization platform of a Cloud native application is constructed by the Nacos component, and service management, routing configuration and monitoring are performed on the visualization platform; the self-defined load scheduler matches the corresponding service instance according to the metadata information and the flow weight of the acquired service; a B/S-based visual block diagram configuration interface is developed through a D3.js or Echarts chart component, and various service metadata information, traffic, service gateways and service clusters are displayed through block diagrams and icon forms with different shapes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311127160.8A CN116860381B (en) | 2023-09-04 | 2023-09-04 | Method for releasing visual micro-service gray scale |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311127160.8A CN116860381B (en) | 2023-09-04 | 2023-09-04 | Method for releasing visual micro-service gray scale |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116860381A true CN116860381A (en) | 2023-10-10 |
| CN116860381B CN116860381B (en) | 2023-11-28 |
Family
ID=88221967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311127160.8A Active CN116860381B (en) | 2023-09-04 | 2023-09-04 | Method for releasing visual micro-service gray scale |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116860381B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180309637A1 (en) * | 2017-04-25 | 2018-10-25 | Nutanix, Inc. | Systems and methods for networked microservice modeling and visualization |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
| CN112118565A (en) * | 2020-08-14 | 2020-12-22 | 金蝶医疗软件科技有限公司 | Multi-tenant service gray level publishing method and device, computer equipment and storage medium |
| CN114527995A (en) * | 2021-12-29 | 2022-05-24 | 浙江中控技术股份有限公司 | Graphical deployment and state monitoring integrated system and method |
| CN114840248A (en) * | 2022-05-12 | 2022-08-02 | 江苏方天电力技术有限公司 | System gray level publishing method based on enterprise level distributed application service |
-
2023
- 2023-09-04 CN CN202311127160.8A patent/CN116860381B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180309637A1 (en) * | 2017-04-25 | 2018-10-25 | Nutanix, Inc. | Systems and methods for networked microservice modeling and visualization |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
| CN112118565A (en) * | 2020-08-14 | 2020-12-22 | 金蝶医疗软件科技有限公司 | Multi-tenant service gray level publishing method and device, computer equipment and storage medium |
| CN114527995A (en) * | 2021-12-29 | 2022-05-24 | 浙江中控技术股份有限公司 | Graphical deployment and state monitoring integrated system and method |
| CN114840248A (en) * | 2022-05-12 | 2022-08-02 | 江苏方天电力技术有限公司 | System gray level publishing method based on enterprise level distributed application service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116860381B (en) | 2023-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3211831B1 (en) | N-tiered end user response time eurt breakdown graph for problem domain isolation | |
| US7035919B1 (en) | Method for calculating user weights for thin client sizing tool | |
| US9374278B2 (en) | Graphic user interface based network management system to define and execute troubleshooting procedure | |
| CN100492319C (en) | System and method for installing storage area network | |
| US20140201642A1 (en) | User interface for visualizing resource performance and managing resources in cloud or distributed systems | |
| CN107800565A (en) | Method for inspecting, device, system, computer equipment and storage medium | |
| CN108399114A (en) | A kind of system performance testing method, apparatus and storage medium | |
| CN102724079B (en) | Method and system for auxiliary configuration of Ethernet equipment | |
| CN107508722A (en) | A kind of business monitoring method and device | |
| CN110505079A (en) | For the visual system and method for multidimensional network based on context | |
| CN109560996B (en) | Automatic testing system and method for terminal of Internet of things | |
| CN102457390A (en) | Fault location method and system based on quality of experience (QoE) | |
| CN102387028A (en) | Network system, network management server, and OAM test method | |
| CN103326902A (en) | Configurable monitoring system and monitoring method for distributed type mainframe performance testing data | |
| CN110968479B (en) | Service level full-link monitoring method and server for application program | |
| CN115686280A (en) | Deep learning model management system, method, computer device and storage medium | |
| CN114070707A (en) | Internet performance monitoring method and system | |
| JP2010128597A (en) | Information processor and method of operating the same | |
| CN116860381B (en) | Method for releasing visual micro-service gray scale | |
| CA2341889A1 (en) | Web application system having functions of session management and distributed management and operation management mechanisms therefor | |
| US20110125852A1 (en) | Keyword filtered alerts for group chats | |
| JP5088233B2 (en) | Operation management apparatus, display method, and program | |
| CN113347060A (en) | Power network fault detection method, device and system based on process automation | |
| CN103117880A (en) | Web technology based network topological generation method | |
| US20050204290A1 (en) | System and method for generating distributed application and distributed system topologies with management information in a networked environment |
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 |