Track message_bridge client UUID and connection counts and time
It is hard to tell from the status message if a node has been
reconnecting a bunch or how long it has been connected. Add both of
those numbers to both the client and server statistics.
While we are here, also add the server's boot UUID to the client.
Because of the way the protocol works, we only get this when the first
message is received, but that happens pretty quickly due to the
timestamps.
All of this should give us much better debugging around client/server
connections when things start to go south.
Change-Id: I2ed732afc81a045c7701fe47d1460a7df9c3d778
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
diff --git a/aos/events/logging/logger_test.cc b/aos/events/logging/logger_test.cc
index 97b293a..7a569eb 100644
--- a/aos/events/logging/logger_test.cc
+++ b/aos/events/logging/logger_test.cc
@@ -2614,9 +2614,9 @@
}
constexpr std::string_view kCombinedConfigSha1(
- "644a3ab079c3ddfb1ef866483cfca9ec015c4142202169081138f72664ffd589");
+ "9e07da76098ad1b755a7c3143aca300d66b6abb88745f6c36e603ef1441f0ad5");
constexpr std::string_view kSplitConfigSha1(
- "20bb9f6ee89519c4bd49986f0afe497d61c71b29d846f2c51f51727c9ef37415");
+ "85ef8be228bf4eb36f4d64ba68183b2a9a616bfb9b057e430d61e33bd273df86");
INSTANTIATE_TEST_SUITE_P(
All, MultinodeLoggerTest,