osbase/logtree.LeveledLogger -> go/logging.Leveled
This factors out the common leveled logger interface out of the logtree.
We want to use the same interface outside of logtree/supervisor usage
within the resolver code, which will be exposed to clients.
Change-Id: I299e76d91e8cefddf8f36f1e58432418c4694df2
Reviewed-on: https://review.monogon.dev/c/monogon/+/3411
Reviewed-by: Tim Windelschmidt <tim@monogon.tech>
Tested-by: Jenkins CI
diff --git a/osbase/logtree/kmsg_test.go b/osbase/logtree/kmsg_test.go
index e2faf82..24f2acf 100644
--- a/osbase/logtree/kmsg_test.go
+++ b/osbase/logtree/kmsg_test.go
@@ -8,6 +8,8 @@
"time"
"github.com/google/go-cmp/cmp"
+
+ "source.monogon.dev/go/logging"
)
func TestParseKmsg(t *testing.T) {
@@ -26,13 +28,13 @@
{"6,30962,1501094342185,-;test\n", &LeveledPayload{
messages: []string{"test"},
timestamp: time.Date(2023, 8, 9, 14, 57, 23, 35675222, time.UTC),
- severity: INFO,
+ severity: logging.INFO,
}},
// With metadata and different severity
{"4,30951,1486884175312,-;nvme nvme2: starting error recovery\n SUBSYSTEM=nvme\n DEVICE=c239:2\n", &LeveledPayload{
messages: []string{"nvme nvme2: starting error recovery"},
timestamp: time.Date(2023, 8, 9, 11, 00, 32, 868802222, time.UTC),
- severity: WARNING,
+ severity: logging.WARNING,
}},
} {
got := parseKmsg(now, nowMonotonic, []byte(te.line))