management.Status constants could not be used directly in log (elasti…

…c#23849) * management.Status constants could not be used directly in log This add stringer generator to the Status const to allow them to be understood by a human in log. ref: elastic#23812
Richardjgq · Feb 4, 2021 · a52c744 · a52c744
1 parent 3a53670
commit a52c744
Show file tree

Hide file tree

Showing 3 changed files with 48 additions and 0 deletions.
diff --git a/libbeat/management/management.go b/libbeat/management/management.go
@@ -31,6 +31,7 @@ import (
 // Status describes the current status of the beat.
 type Status int
 
+//go:generate stringer -type=Status
 const (
 	// Unknown is initial status when none has been reported.
 	Unknown Status = iota

diff --git a/libbeat/management/status_string.go b/libbeat/management/status_string.go
diff --git a/x-pack/elastic-agent/CHANGELOG.asciidoc b/x-pack/elastic-agent/CHANGELOG.asciidoc
@@ -32,6 +32,7 @@
 - Fixed nil pointer during unenroll {pull}23609[23609]
 - Fixed reenroll scenario {pull}23686[23686]
 - Fixed Monitoring filebeat and metricbeat not connecting to Agent over GRPC {pull}23843[23843]
+- Fixed make status readable in the log. {pull}23849[23849]
 
 ==== New features