vespa-engine/vespa

Expose NEED_RESTART as a metric

Open

#4,631 opened on Jan 11, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,948 stars) (561 forks)batch import
enhancementgood first issueneed help

Description

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.

Contributor guide

Tech stack
java
Domain
backendobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Java knowledgeVespa internalsMetrics system understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
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