vespa-engine/vespa

Expose NEED_RESTART as a metric

Open

#4,631 创建于 2018年1月11日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Java (4,948 star) (561 fork)batch import
enhancementgood first issueneed help

描述

After a meeting today with Zedge we concluded that only providing information about the need to restart services upon deploy is not enough.

When config changes are deployed that require services to be restarted the services should themselves report that either in health or as a metric.

贡献者指南

技术栈
java
领域
backendobservability
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Java knowledgeVespa internalsMetrics system understanding
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Examine Vespa's existing metric reporting infrastructure, particularly how services expose health and metrics via REST APIs. Look at the config server or node repository code to understand where NEED RESTART state is tracked. The goal is to add a metric (e.g., a gauge) that reports the restart requirement status. Consider extending the /state/v1/health endpoint or adding a custom metric to the metrics API. Review similar past contributions for patterns.
Expose NEED_RESTART as a metric · vespa-engine/vespa#4631 | Good First Issue