Service Mesh #
Service mesh is a one-stop solution for intelligent micro service governance. Its product structure includes: Registration Center, Governance Center, log center, gateway center, CA center, telemetry center, CA center, security center BI data and runtime.
The basic functions of each module are summarized as follows:
Dashboard #
The platform dashboard focuses on the events that need attention at the platform level and refines the core indicators of major centers. It provides a macro perspective of the operation of the whole platform, and can be drilled in by clicking the indicators that need attention.
The main function points of this module are as follows
- Resource overview of each center
- Overview of pending events in each center
- Application performance monitoring overview
Registration #
The registry undertakes the important task of service discovery and registration in the microservice governance system. It is a facility that needs to be paid attention to.
Through the “Registration” module function, we can see the operation overview and service registration information of the registration center. The main functions of this module are as follows
- Register engine management, including engine access and engine node viewing.
- Registration engine resource status monitoring, including CPU and memory usage, resource list and resource warning.
- The registration engine views registered services, including service list, instance list, service topology and metadata information.
Governance #
The Governance Center focuses on the observability and governance of operation services.
The main functions of this module are as follows
- View the metadata of the running service, such as uniqueID, host, structure key, etc.
- View service operation status, such as operation log and resource (CPU, memory) consumption trend.
- Service governance status and rule management currently include: Service fusing and service current limiting.
- Abnormal service identification, such as health check topn, governance event topn, etc.
- Service security policy control, such as MTLs function on
- View of application lifecycle
- Service traffic configuration
- Service gateway information viewing
- Service trace information viewing.
- View service topology information.
- Service APM alarm information viewing.
- Service Custom monitoring information management and viewing
Logs #
Focus on log access, log governance and log viewing.
The main functions of this module are as follows
- Log key access management.
- Log key governance, including interception and flow restriction.
- Platform log viewing.
Gateway #
Focus on Gateway Routing and traffic log viewing.
The main functions of this module are as follows
- View the gateway routes.
- View gateway log traffic.
Telemetry #
Focus on service telemetry information.
The main functions of this module are as follows
- View the complete telemetry information of the service from the service dimension
- Infrastructures monitoring display, such as redis cluster, gateway and other information
CA #
Through the “CA center” module, we can observe the running status of the CA center and view and manage certificates.
At present, the main functions are
- CA center operation overview
- View certificate topology information and certificate details
- Certificate management
BI #
In the process of service operation, various operation analysis requirements will be derived, including view and analysis of business indicators and collection and view of system operation indicators.
Through the built-in observation function of MSP platform, we can have a good detection and early warning of system level indicators (CPU, memory, traffic, etc.) of services. However, for some customized observation indicators, we can meet this requirement through “BI”. User defined query statements can meet various analysis scenarios.
At present, the module includes the following functions
- BI panel management, users can customize panel layout and related query strategies
- BI settings (used by platform developers) to define the panel ID to be embedded. At present, this function is dedicated by developers and can be ignored by platform users.
Runtime #
For runtime, the current platform provides two functions: Pub/sub and confidential storage.
Pub/sub: focus on sending and receiving messages between services
- View and manage pub/sub engines
- View and manage the service’s use of the pub/sub engine
- Pub/sub telemetry information viewing
Secret storage: focus on the storage and management of Secret information
- View and manage Secret storage engines
- View and manage service usage of Secret storage engine
- Secret storage telemetry information viewing
Around microservice governance, service mesh provides a visible, controllable, traceable and predictable system wide view of microservices to support business stability and efficient iteration.