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-Go Metrics Monitoring

Dubbo-Go can collect runtime metrics for RPC calls, metadata, registries, config centers, and other components. This guide uses dubbo-go-samples/observability/prometheus_grafana to show both Prometheus Pull mode and Pushgateway mode.

Note: some older descriptions may still mention metrics/prometheus_grafana. The current sample directory is observability/prometheus_grafana.

1. Monitoring Modes

1.1 Pull Mode

Dubbo-Go application exposes /prometheus or /metrics
 |
 v
Prometheus scrapes the application
 |
 v
Grafana queries Prometheus and renders dashboards

Pull mode is the standard Prometheus model and is recommended for long-running Dubbo-Go providers and consumers. In this sample:

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.

Kubernetes Lifecycle Probe

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

Dubbo-Go Kubernetes Lifecycle Probe

Dubbo-Go provides a built-in Kubernetes HTTP Probe service that supports:

✅ liveness
✅ readiness
✅ startup

The probe service runs on an independent HTTP port and supports:

Custom health check logic
Optional alignment with Dubbo internal lifecycle state
Controlled restart risk management

For a complete runnable example, see:

https://github.com/apache/dubbo-go-samples/tree/main/observability/probe

1. Design Goals

Goal	Description
Extensibility	Supports custom health check callbacks
Risk Control	Liveness does not bind complex internal logic by default
Lifecycle Alignment	Readiness and startup can align with Dubbo lifecycle
Independent Port	Isolated from business service port

2. Default Behavior

When Probe is enabled, it exposes endpoints on: