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

This article will explain in detail what is the guide to the use of the micro service gateway SIA-GateWay. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

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 groups

Owning instances: number of gateway group instances

Gateway status: current status of the gateway group

Gateway description: gateway group description information, which can be modified

Second, home page

The home page shows the current operation of the gateway.

It mainly includes the following parts:

Gateway call trend: the amount of each node is adjusted per hour, for a total of 30 hours

Gateway health status: health status of each node per hour, for a total of 30 hours

Monitoring alarms: warnings sent during operation

Gateway cluster status: monitoring of CPU, JVM and connection number 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: the only indication of the route, which is also the database table primary key

Gateway cluster group name: enter the current gateway group name. You can see it in the upper right corner.

Application name: optional, generally fill in the application name

Matching path: path of the backend service

Back-end service policy: there are three options:

The backend service policy states that the backend service ID enters the name of the application registered in the registry. When the route matches, the corresponding instance will be matched according to the service list of the registry. The backend service URL route matching will be directly forwarded to the filled URLListofServer route matching, and then use the polling policy to select an instance for forwarding.

Backend service URL: when backend service policy selects backend service URL and ListofServer, enter backend ip:port

Whether the prefix is valid: if you choose Yes, the real matching path = matching path + common 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. You can select some routes to export. Click Route Export to download the routerList.json file.

Route import: click 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 edited.

3.3 routing operation

The routing operation is divided into two parts:

Modify routing status: the routing status can be divided into three states: edit, release and offline, and the operations should be published, undone, modified, deleted and viewed.

Routing component management: API gateway provides rich components. After routing is bound in component management, you can view or configure components under this route. Refer to component management for the function and usage of each component.

3.4 routing Topology

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 a component, you first need to bind routes in component management, and then view or configure the component 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 components and canary components

Monitoring: statistics components, statistics of routing access

Current limiting: current limiting component to limit the number of routing requests per unit time

Security: security certification components and blacklist components

4.2 third-party components

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: displays the contents of the current log file, with data from Actuator

JVM: monitoring load, class loading, threads, etc., data from Actuator

Memory: monitor JVM memory, data from Actuator

Garbage collection: monitoring parnew and CMS collectors, data from Actuator

Configuration: including internal and external configuration files, data from Actuator

5.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 under the gateway group is published.

The administrator can request a new registry address.

IX. 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.

On the micro service gateway SIA-GateWay guide is shared here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

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.