nightly_sanity: analyze the glusterfs logs daily and include the results in mailHEADmaster

Using the log_analyzer script analyze the bricks and client logs, which
tells what functions are called how much times. Thus excessive logging can
be stopped.

Change-Id: I74ee71b29865612332603a2ffc7fb5c7055c921d
Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

1 files changed, 15 insertions, 0 deletions

diff --git a/sanity/nightly_sanity/nightly_updated.sh b/sanity/nightly_sanity/nightly_updated.sh
index 652cdbb..33c26cc 100755
--- a/sanity/nightly_sanity/nightly_updated.sh
+++ b/sanity/nightly_sanity/nightly_updated.sh
@@ -684,6 +684,21 @@ function send_results()
             grep "\ C\ " $i >> $LOGDIR/logs_failed_$translator;
         done
 
+        # log-analyzer which says which functions are called how many times
+        # Excessive logging can be minimized.
+
+        for i in $(find $DEFAULT_LOGDIR/bricks -type f -iname "*.log")
+        do
+            echo $i >> $LOGDIR/logs_failed_$translator;
+            log_analyzer.sh $DEFAULT_LOGDIR/bricks/$i >> $LOGDIR/logs_failed_$translator;
+        done
+
+        for i in $(find $DEFAULT_LOGDIR -type f -iname "*.log")
+        do
+            echo $i >> $LOGDIR/logs_failed_$translator;
+            log_analyzer.sh $DEFAULT_LOGDIR/$i >> $LOGDIR/logs_failed_$translator;
+        done
+
         rm -rf $DEFAULT_LOGDIR/*.log;
         rm -rf $DEFAULT_LOGDIR/bricks/*;