[health check] health_check_path 目前是全局维度的,理想情况下应该是服务维度
Open
feature
- Dominant language
- C++
- Stars
- 17.6k
- Forks
- 4.1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 69
Description
**Is your feature request related to a problem? (你需要的功能是否与某个问题有关?)**
health_check_path 目前是全局维度的(gflags方式设置),实际上每个服务的健康检查接口可能都不一样,因此这个应该是服务维度的。
**Describe the solution you'd like (描述你期望的解决方法)**
在ChannelOptions中增加health_check_path,并且优先级高于全局的health_check_path
**Describe alternatives you've considered (描述你想到的折衷方案)**
**Additional context/screenshots (更多上下文/截图)**
Contributor guide
Research direction
Start by locating the ChannelOptions definition and the existing global health_check_path handling. Trace how service options are applied, then verify that a per-service path takes precedence while the global path remains the fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100