Liveness endpoint does not consider overall agent state, only component state #9576
Description
In a container with a config referencing an undefined output:
elastic-agent status
┌─ fleet
│ └─ status: (STOPPED) Not enrolled into Fleet
└─ elastic-agent
└─ status: (FAILED) Invalid component model: failed to render components: invalid 'inputs.0.use_output', references an unknown output 'iam'
The results from hitting /liveness show healthy:
# curl -w 'HTTP %{http_code}' 'http://localhost:6791/liveness?failon=heartbeat'
HTTP 200
# curl -w 'HTTP %{http_code}' 'http://localhost:6791/liveness?failon=degraded'
HTTP 200
# curl -w 'HTTP %{http_code}' 'http://localhost:6791/liveness?failon=failed'
HTTP 200It looks like we aren't considering the overall agent status, only the component status:
elastic-agent/internal/pkg/agent/application/monitoring/liveness.go
Lines 80 to 94 in 72e346e