Aid triaging of bugs by printing notifications about interesting parts of an event log.
Notifications are printed for gaps in seq number, capture timestamp, arrival and send times for RTP and RTCP, and high average loss.
The notifications are printed to stderr by default, but internally they are represented as subclasses to a TriageNotification base class in order to facilitate other output formats.
Initially, this is only run if the event_log_visualizer is given the flag --print_triage_notifications.
Only the first (LOG_START, LOG_END) segment is processed.
Bug: webrtc:8383
Change-Id: If43ef7f115f622fa5552dc50951a11d5f9e3cbaa
Reviewed-on: https://webrtc-review.googlesource.com/8720
Commit-Queue: Björn Terelius <terelius@webrtc.org>
Reviewed-by: Philip Eliasson <philipel@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20974}diff --git a/rtc_tools/event_log_visualizer/main.cc b/rtc_tools/event_log_visualizer/main.cc
index e028a0f..3bc79be 100644
--- a/rtc_tools/event_log_visualizer/main.cc
+++ b/rtc_tools/event_log_visualizer/main.cc
@@ -132,6 +132,11 @@
"Show the state of the delay based BWE detector on the total "
"bitrate graph");
+DEFINE_bool(
+ print_triage_notifications,
+ false,
+ "Print triage notifications, i.e. a list of suspicious looking events.");
+
void SetAllPlotFlags(bool setting);
@@ -305,6 +310,11 @@
collection->Draw();
+ if (FLAG_print_triage_notifications) {
+ analyzer.CreateTriageNotifications();
+ analyzer.PrintNotifications(stderr);
+ }
+
return 0;
}