Shulou(Shulou.com)06/03 Report--

1. DeskTop

DeskTop shows each gateway group currently registered. Clicking on a gateway group will select the gateway group and jump to the home page.

Each gateway group includes the following four items:

Role value: gateway application name prefix, used to distinguish gateway group owning instance: number of gateway group instance gateway status: gateway group current status gateway description: gateway group description information, can modify second, home page

The home page shows the current operation of the gateway.

It mainly includes the following parts:

Gateway invocation trend: hourly call volume of each node, total 30 hours gateway health status: hourly health status of each node, total 30 hour monitoring alarm: warning gateway cluster status sent during operation: CPU, JVM and connection number monitoring of each node, in which CPU and JVM data are taken from Actuator III, routing management

Route management is divided into four parts:

3.1 New Route

Fill in the following options for the new route:

Routing ID: unique indication of the route, also database table primary key gateway cluster group name: fill in the current gateway group name, and the application name can be seen in the upper right corner: optional, generally fill in the application name matching path: backend service path backend service policy: there are three choices: backend service policy description backend service ID enter the application name registered with the registry During route matching, the corresponding instance will be matched according to the service list of the registry. After the URL route matching is directly forwarded to the filled-in URLListofServer route match, a polling policy will be used to select an instance to forward the backend service URL: when selecting the backend service URL and ListofServer, enter whether the backend ip:port prefix is valid: if you choose yes, the real matching path = matching path + public prefix

3.2 Route Import and Export

Route import and export can be used to synchronize routing data between test environment and production environment

Route export: all routes in the current gateway group are exported by default, and some routes can be selected. Click the route export to download the routerList.json file route import: click the route import to select the imported route file. After import, you will be prompted to import the successful and failed route ID. The imported route is an edit status 3.3route operation.

The routing operation is divided into two parts:

Modify the routing status: the routing status is divided into three states: edit, publish, and offline. Manage the routing components that should be published, offline, modified, deleted and viewed. API Gateway provides components with rich features. After the routing is bound in the component management, you can view or configure the components under the routing.

Click the routing topology diagram to show the real-time topology diagram of the route. The topology diagram is divided into three segments: application-> gateway-> back-end service. If there is no request for the route, the route topology diagram is empty.

IV. Component management

The gateway provides feature-rich public components and allows users to upload third-party components. When using components, you first need to bind routes in component management, and then view or configure components in routing management.

4.1 Common components

The common component description describes the function and usage of the component, which is divided into the following categories:

Log: divided into request log component and impact log component grayscale: divided into blue-green deployment component and canary component monitoring: statistical component, statistical routing access limit: current limiting component, limit routing per unit time request security: security authentication component and blacklist component 4.2 third-party component

Third-party components are implemented by user definition and can be used after uploading. Click the third-party component to view the uploaded third-party component, and click component upload to upload the custom third-party component.

V. Gateway monitoring

Gateway monitoring is divided into two parts: health monitoring and topology diagram.

5.1 operational status monitoring

Running status monitoring includes the following monitoring items:

Monitoring: integrated Hystrix dashboard log: showing the contents of the current log file, data from ActuatorJVM: monitoring load, class loading, threads, etc., data from Actuator memory: monitoring JVM memory, data from Actuator garbage collection: monitoring parnew and CMS collector, data from Actuator configuration: including internal and external configuration files, data from Actuator5.2 topology diagram

The topology diagram shows the service flow diagram of the gateway, which is a collection of all routing topology diagrams.

VI. Log management

Log management is integrated with Kibana. When users click log management, they will jump to Kibana to display the log data of the gateway group ES index. If the route is bound to a log request component or log response component, you can jump in Route Management-Operations-> request Log component or response Log component.

VII. Fuse management

Circuit breaker management shows the request information of Hystrix circuit breaker during gateway operation, including circuit breaker type, error message, stack information and so on.

VIII. Registry management

Registry management mainly includes two parts: registration information query and dynamic modification of registry address.

8.1 Registration Information query

The registration information comes from the Eureka of the current gateway group. Click to query the applications that meet the criteria.

8.2 dynamically modify the registry address

The Eureka server address is configured locally by default. Users can modify the Eureka address by setting Eureka. If the setting is successful, the newly set Eureka address will be saved in the database, and the gateway group node will be notified to modify the in-memory registry address and re-register. Clicking reset Eureka clears the Eureka address in the database and notifies the gateway group node to use the local configuration. The pop-up window will prompt for the result after setting / resetting.

Registry address setting / reset success criteria:

The stateless route manager under the gateway group can request access to the new registry address. 9. Routing connectivity test

GET and POST are supported to test whether the route is connected.

10. Gateway Swagger

The gateway Swagger integrates all the gateway interface documents of the services registered in the registry. You can view the interface documents by selecting different services in the upper right corner.

11. System blacklist

The system blacklist can be set as a global blacklist. The IP blocking policy is supported. All requests from the IP will be blocked after the blacklist is set.

12. Gateway audit

The gateway audit shows all the users, behaviors and performance operating on the gateway management side, which is convenient to monitor and analyze user behavior.

XIII. Gateway setting

The gateway setting is divided into three parts: early warning mailbox, log level operation, and viewing version number.

13.1 early warning mailbox

When an early warning occurs, an early warning email will be sent to the set mailbox.

13.2 Log level operation

The gateway log level defaults to INFO, and users can view or dynamically adjust the log level when debugging. Log names are com.creditease and root, and log levels are INFO and DEBUG.

In logging frameworks such as Logback, the logger level is similar to java inheritance, organized by name, using "." Split the logger name into the parent logger and the child logger, and if the child logger does not set the log level, the parent log level is used until ROOT,ROOT is equivalent to the Object in Java. When the child log level is set, the parent (including ROOT) log level is no longer valid for the child log, similar to the java subclass overriding the parent class method.

13.3 View version number

The gateway version number is used to distinguish the version of each instance of the gateway. The default configuration of the next version number is: sag_x.y_timestamp,timestamp is a packaging timestamp, which can be modified through zuul.version in the configuration file.

Links to SIA related open source products

Micro-service task scheduling framework: https://github.com/siaorg/sia-task micro-service routing gateway: https://github.com/siaorg/sia-gatewayRabbitmq queue service PLUS: https://github.com/siaorg/sia-rabbitmq-plus

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.