Visual Observation on Apache Dubbo

Configure and Manage Framework Logs

Mon, 01 Jan 0001 00:00:00 +0000

This example demonstrates how to configure the dubbo-go framework log component to save the framework’s runtime logs to a specified location. You can view the complete example source code here.

Note

The configuration here only affects the log component behavior of the dubbo-go framework itself, which is the internal logging used by the framework and does not affect the use of business logging frameworks!

1. Log Configuration

As shown below, you can set the dubbo framework log behavior using log.WithZap() and log.WithLevel("warn"):

Metrics Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

Dubbo supports the collection of runtime Metrics indicators and their integration with Prometheus and Grafana systems to achieve visual monitoring of microservice clusters. Below is a specific usage example. You can view the complete source code of the example.

server/main.go - is the main definition of the service, handler and rpc server
client/main.go - is the rpc client
proto - contains the protobuf definition of the API

How to run

Run server

go run ./go-server/cmd/main.go

test server work as expected:

Link Tracing

Mon, 01 Jan 0001 00:00:00 +0000

Dubbo-go supports end-to-end tracing based on the OpenTelemetry standard, while also supporting export to different tracing backend systems through the following exporters.

Usage

Please note that tracing functionality is only enabled when creating the Dubbo application via dubbo.NewInstance, which is the microservice application mode mentioned in our quick start. The lightweight RPC API does not currently support enabling tracing.

Example Explanation

You can view the full example source code here.

Visual Observation on Apache Dubbo

Configure and Manage Framework Logs

Note

1. Log Configuration

Metrics Monitoring

Contents

How to run

Run server

Link Tracing

Usage

Example Explanation