refactor(observability): new observability infra based on OTeL#464
Merged
Conversation
…t calls to record span in api/rpc/*
Member
|
可以先修一下 CI |
Contributor
Author
|
unit test 没过好像不是我的问题:\ |
Member
现在没过这单测也能合就是了 |
Member
|
merge 一下主分支,那边单测是好的了现在 |
Signed-off-by: Cai <13110818005@qq.com>
Codecov Report❌ Patch coverage is @@ Coverage Diff @@
## main #464 +/- ##
==========================================
- Coverage 62.95% 62.71% -0.24%
==========================================
Files 224 230 +6
Lines 5852 6027 +175
==========================================
+ Hits 3684 3780 +96
- Misses 2051 2126 +75
- Partials 117 121 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Member
|
为什么这个 docker-compose 是单独开的,而不是合并在 /docker/docker-compose.yml 里面 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
自查 PR 结构
PR 标题符合这个格式: <type>(optional scope): <description>
此 PR 标题的描述以用户为导向,足够清晰,其他人可以理解。
我已经对所有 commit 提供了签名(GPG 密钥签名、SSH 密钥签名)
这个 PR 属于强制变更/破坏性更改
这个 PR 的类型是什么?
这个 PR 做了什么 / 我们为什么需要这个 PR?
一个可以算作 feature 的可观测性基础设施,支持导出为 Otel traces & logs
(可选)这个 PR 解决了哪个/些 issue?
对 Reviewer 预留的一些提醒