Shulou(Shulou.com)05/31 Report--

This article mainly introduces the distributed link tracking SkyWalking configuration management, the article is very detailed, has a certain reference value, interested friends must read it!

SkyWalking is an open source APM system that includes monitoring, tracking, and diagnosing functions for distributed systems in the Cloud Native architecture. The core functions are as follows:

-Analysis of service, service instance and endpoint metrics

-Root cause analysis, analyzing code at run time

-Analysis of service topology diagram

-Service, service instance and endpoint dependency analysis

-slow services and endpoints detected

-performance optimization

-distributed tracking and context propagation

-Database access metrics. Detect slow database access statements (including SQL statements)

-call the police

SkyWalking is currently a top-level Apache project, as such an excellent open source project, its architectural design concept will certainly have a lot to learn from.

# distributed configuration Ecological Methodology

Distributed configuration is an old distributed topic. All systems with distributed capabilities should consider distributed configuration. What are the mainstream and mature distributed configuration systems? If we want to talk about ecological methodology, we must consider these problems.

# Apollo

Anyone who has done distributed development should know that Ctrip's very popular distributed configuration framework is very mature, and many companies directly use open source Apollo, which can be said to fully trust this framework.

Apollo can centrally manage the configuration of different environments and clusters, and can be pushed to the application side in real time after configuration modification, and has standardized permissions, process governance and other features, so it is suitable for micro-service configuration management scenarios. The server is developed based on Spring Boot and Spring Cloud, which can be packaged and run directly without additional installation of application containers such as Tomcat. The Java client does not rely on any framework and can run in all Java runtime environments. It also has good support for the Spring/Spring Boot environment.

Applications from centralized single architecture to micro-service architecture, there are more and more services, and the original single-based configuration is becoming more and more difficult to manage, which can not meet the business scenarios of rapid release and delivery. The expectation of program configuration is getting higher and higher: real-time effective after configuration modification, grayscale release, sub-environment, sub-cluster management configuration, perfect authority, audit mechanism …...

In such a large environment, the traditional configuration files, databases and other ways have been increasingly unable to meet the needs of developers for configuration management.

In this way, a separate configuration framework like Apollo is produced, which is mainly to improve the efficiency of the business, because it can be used to build the ecology of application configuration management.

For a detailed introduction to Apollo, you can refer to the official documentation, which lists only a few of its core concepts:

-application (application): this is the `spring.application.name=api- alarm` in the analogy application, which isolates the configuration from the application level.

-environment (environment): configure the corresponding environment. The Apollo client needs to know which environment the current application is in at run time, so that it can obtain the configuration of the application.

-cluster (cluster): a grouping of different instances under an application. For example, the application instance of the data center in Hangzhou can be divided into one cluster, and the application instance of the data center in Suzhou into another cluster.

-namespace (Namespace): a grouping of different configurations under an application. You can simply compare namespace to files. Different types of configurations are stored in different files, such as database configuration files, RPC configuration files, application configuration files, and so on. For example, you can also do a tenant isolation within the cluster according to the namespace.

# Nacos

Nacos is a service governance and configuration platform used out of the box, designed for dynamic service discovery, configuration, and service management. It helps you easily build cloud-native applications and micro-service platforms. Service is the service governance dimension of Nacos, which is different from Dubbo. Nacos supports almost all types of services, such as Dubbo/gRPC services, Spring Cloud RESTFul services, or Kubernetes services.

Nacos provides the following four main functions.

-Service discovery and service health check: Nacos simplifies service registration and discovery of other services through DNS or HTTP interfaces. Nacos also provides real-time health checks for services to prevent requests from being sent to unhealthy hosts or service instances.

-dynamic configuration management: dynamic configuration services allow you to manage the configuration of all services across all environments in a centralized and dynamic manner. Nacos eliminates the need to redeploy applications and services when updating the configuration, which makes configuration changes more efficient and agile.

-dynamic domain name service: Nacos supports weighted routing, which makes it easier for you to implement middle-tier load balancing, flexible routing policy, flow control and simple DNS resolution service in the production environment of the data center. It helps you easily implement DNS-based service discovery and prevents applications from coupling with vendor-specific service discovery API.

-Service and metadata management: Nacos provides an easy-to-use service dashboard to help you manage service metadata, configuration, Kubernetes DNS, service health and metrics statistics.

Here the author only lists two popular distributed configuration frameworks, and of course there are others, such as Disconf and Spring Cloud Config, but the basic usage frequency is not as high as Apollo and Nacos.

Because my company currently uses Nacos to complete the service governance and configuration management of micro-services, the author gives priority to using Nacos, mainly based on the following considerations:

-out of the box

-the function is simple, efficient and easy to use

-full support for K8s

-full support for cloud natives

-full support for Spring Cloud Alibaba

-very high level of community activity

-brings together the service governance and soft load functions of Ali's internal high-traffic business scenario verification

-A single service can complete service governance and configuration management, saving machine resources.

These are all the contents of the article "distributed Link tracking SkyWalking how to configure and manage". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.