You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Improve observability and error semantics for application-level metadata / 增强应用级 metadata 链路观测与错误语义 #3356
The application-level metadata path after #2534 includes local MetadataInfo, revision calculation, metadata report publishing/loading, service-app mapping, and RPC MetadataService. When service discovery fails, it is currently difficult to identify which stage caused the failure. This issue only focuses on observability for the application-level metadata path.
Current observability is not enough to diagnose application-level metadata failures.
Specific problems:
Mapping register, get, listen, and remove operations do not have unified metrics or structured logs.
Revision calculation and metadata cache hit/miss are hard to observe.
Errors from metadata report loading, RPC metadata loading, URL construction, and mapping are not clearly categorized.
When consumers cannot discover services, it is hard to tell whether the root cause is mapping, metadata report, RPC metadata service, revision, or cache.
Suggestions
Add metrics and structured logs for mapping register, get, listen, and remove operations.
Expose metadata source, storage type, revision, and cache hit/miss where appropriate.
Use clear error categories for metadata report failure, RPC metadata failure, URL construction failure, revision mismatch, and mapping failure.
Include useful context such as app, revision, service key, registry id, and storage type.
Add failure-path tests that verify error messages or categories.
changed the title [-][metadata] 增强应用级 metadata 链路观测与错误语义[/-][+][FEATURE] Improve observability and error semantics for application-level metadata / 增强应用级 metadata 链路观测与错误语义[/+]on May 30, 2026
@Alanxtl is this issue still active, I can take it up?
this issue have been assigned to @Oxidaner , if you are insterested in contributing to dubbo-go you can refer to the latest issues, which have not been assigned
@Modo-me I am almost done with the code on this PR I have just been busy due to a personal emergency I will be able to close the issue with pr over weekend
@Alanxtl Could I take over this issue? It looks like there hasn’t been much activity recently. I d like to work on it and plan to split the larger change into several smaller PRs so each part can be reviewed incrementally.
@Alanxtl Could I take over this issue? It looks like there hasn’t been much activity recently. I d like to work on it and plan to split the larger change into several smaller PRs so each part can be reviewed incrementally.
Current plan divides the required PRs into two dimensions Observability and Error semantics.目前的计划将所需的 PR 分为两个维度:可观测性和错误语义。
Observability: 可观测性:
PR1: Complete observability for mapping operations — unified metrics and structured logs for register, get, listen, and removePR1:映射操作的完全可观测性——统一的指标和结构化日志,用于注册、获取、监听和删除操作。
PR2: Expose observability for metadata source, storage type, revision, and cache hit/miss along the metadata pathPR2:公开元数据路径上的元数据来源、存储类型、版本和缓存命中/未命中情况的可观测性
Error semantics: 错误语义:
PR3: Classify errors, enrich them with useful context, and add failure-path testsPR3:对错误进行分类,添加有用的上下文信息,并添加故障路径测试
Activity
[-][metadata] 增强应用级 metadata 链路观测与错误语义[/-][+][FEATURE] Improve observability and error semantics for application-level metadata / 增强应用级 metadata 链路观测与错误语义[/+]Oxidaner commentedon Jun 1, 2026
please assign to me
Rachit-Gandhi commentedon Jun 13, 2026
@Alanxtl is this issue still active, I can take it up?
Alanxtl commentedon Jun 14, 2026
this issue have been assigned to @Oxidaner , if you are insterested in contributing to dubbo-go you can refer to the latest issues, which have not been assigned
Alanxtl commentedon Jun 14, 2026
after discussion with @Oxidaner , u can take up this issue, I assign it to you
Rachit-Gandhi commentedon Jun 14, 2026
thanks @Alanxtl
Modo-me commentedon Jul 23, 2026
I'm interested in this observability issue and would like to help move it forward. Could I continue working on it?
Rachit-Gandhi commentedon Jul 23, 2026
@Modo-me I am almost done with the code on this PR I have just been busy due to a personal emergency I will be able to close the issue with pr over weekend
1 remaining item
Alanxtl commentedon Jul 27, 2026
@Rachit-Gandhi are you still working on it?
Modo-me commentedon Aug 5, 2026
@Alanxtl Could I take over this issue? It looks like there hasn’t been much activity recently. I d like to work on it and plan to split the larger change into several smaller PRs so each part can be reviewed incrementally.
Alanxtl commentedon Aug 5, 2026
sure
Modo-me commentedon Aug 5, 2026
Current plan divides the required PRs into two dimensions Observability and Error semantics.
Observability:
Error semantics:
Alanxtl commentedon Aug 6, 2026
注意一下别和这个的职责划分冲突了#3562
Modo-me commentedon Aug 6, 2026
已查看 与现有工作不产生冲突
Modo-me commentedon Aug 6, 2026
@Alanxtl 关于增加结构化日志这里,可能需要进一步讨论。目前没看到仓库里有现成的结构化日志标准,仓库内logger给的是
Debug/Info/Warn/Error + f的方法,并不是结构化日志。PR #3605 暂时先采用了logger的那一套日志方法Alanxtl commentedon Aug 11, 2026
我就是这个意思 使用gost的logger
Modo-me commentedon Sep 9, 2026
@Alanxtl 这个issue应该都解决了,可以close了