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 (561 forks)batch import
enhancementgood first issueneed help

Repository metrics

Stars
 (4,948 stars)
PR merge metrics
 (Avg merge 1d 22h) (209 merged PRs in 30d)

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

Research direction
Look for where service restart status is tracked (e.g., in configserver or cluster controller) and expose it as a metric using the Vespa metrics framework.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70