Forward output glitch information from stream WebRTC log

media/audio/mac/audio_low_latency_input_mac.cc

Index: media/audio/mac/audio_low_latency_input_mac.cc
diff --git a/media/audio/mac/audio_low_latency_input_mac.cc b/media/audio/mac/audio_low_latency_input_mac.cc
index d351940041d9b892f4be92be6477d990c850a514..5c711b748c72908e9680e2b69e64737f53f531d7 100644
--- a/media/audio/mac/audio_low_latency_input_mac.cc
+++ b/media/audio/mac/audio_low_latency_input_mac.cc
@@ -14,6 +14,7 @@
 #include "base/metrics/sparse_histogram.h"
 #include "base/sys_info.h"
 #include "base/time/time.h"
+#include "media/audio/audio_logging.h"
 #include "media/audio/mac/audio_manager_mac.h"
 #include "media/base/audio_bus.h"
 #include "media/base/data_buffer.h"
@@ -1327,6 +1328,8 @@ void AUAudioInputStream::ReportAndResetStats() {
   // A value of 0 indicates that we got the buffer size we asked for.
   UMA_HISTOGRAM_COUNTS_10000("Media.Audio.Capture.FramesProvided",
                              number_of_frames_provided_);
+  WebRtcLogMessage("(Example) Here the stats will be logged.");

[DaleCurtis, 2016/04/05 21:56:52]

No, this is a layering violation. media/ shouldn't know anything about WebRTC.
This should be some generic logging infrastructure (likely attached to the
existing AudioLog).

[Henrik Grunell, 2016/04/06 12:25:31]

What about adding something like
AudioLog::OnStatistic(int component_id, const std::string& name, int value);
?
And use like:
audio_log->OnStatistic(stream_id, "Media.Audio.Capture.Glitches",
glitches_detected_);

Then media internals can format and forward to the WebRTC log (maybe filtered on
stat name), and in the future we could add presentation of component specific
stats in media-interals (I think that would be useful).

+
   // Even if there aren't any glitches, we want to record it to get a feel for
   // how often we get no glitches vs the alternative.
   UMA_HISTOGRAM_COUNTS("Media.Audio.Capture.Glitches", glitches_detected_);