Add logdog and logcat tips to perf sheriffing doc.

tools/perf/docs/perf_bot_sheriffing.md

 # Perf Bot Sheriffing
 
 The perf bot sheriff is responsible for keeping the bots on the chromium.perf
 waterfall up and running, and triaging performance test failures and flakes.
 
 **[Rotation calendar](https://calendar.google.com/calendar/embed?src=google.com_2fpmo740pd1unrui9d7cgpbg2k%40group.calendar.google.com)**
 
 ## Key Responsibilities
 
 *   [Handle Device and Bot Failures](#Handle-Device-and-Bot-Failures)
@@ skipping 172 matching lines @@
     *   The revision range the test occurred on.
     *   A list of all platforms the test fails on.
 2.  Disable the failing test if it is failing more than one out of five runs.
     (see below for instructions on telemetry and other types of tests). Make
     sure your disable cl includes a BUG= line with the bug from step 1 and the
     test owner is cc-ed on the bug.
 3.  After the disable CL lands, you can downgrade the priority to Pri-2 and
     ensure that the bug title reflects something like "Fix and re-enable
     testname".
 4.  Investigate the failure. Some tips for investigating:
+    *   When viewing buildbot step logs, **use the **<font color="blue">[stdout]</font>** link to view logs!**.
+        This will link to logdog logs which do not expire. Do not use or link
+        to the logs found through the <font color="blue">stdio</font> link
+        whenever possible as these logs will expire.
+    *   When investigating Android, look for the logcat which is uploaded to
+        Google Storage at the end of the run. logcat will contain much more
+        detailed Android device and crash info than will be found in
+        Telemetry logs.
     *   If it's a non flaky failure, indentify the first failed
         build so you can narrow down the range of CLs that causes the failure.
         You can use the
         [diagnose_test_failure](https://code.google.com/p/chromium/codesearch#chromium/src/tools/perf/diagnose_test_failure)
         script to automatically find the first failed build and the good & bad
         revisions (which can also be used for return code bisect).
     *   If you suspect a specific CL in the range, you can revert it locally and
         run the test on the
         [perf trybots](https://www.chromium.org/developers/telemetry/performance-try-bots).
     *   You can run a return code bisect to narrow down the culprit CL:
@@ skipping 76 matching lines @@
 
 **[Pri-2 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3APerformance-Sheriff-BotHealth+label%3APri-2)**
 are for disabled tests. These should be pinged weekly, and work towards fixing
 should be ongoing when the sheriff is not working on a Pri-1 issue. Here is the
 [list of Pri-2 bugs that have not been pinged in a week](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label:Performance-Sheriff-BotHealth%20label:Pri-2%20modified-before:today-7&sort=modified).
 
 <!-- Unresolved issues:
 1. Do perf sheriffs watch the bisect waterfall?
 2. Do perf sheriffs watch the internal clank waterfall?
 -->