Count flakiness pipeline issue tracker requests

infra/services/builder_alerts/crbug_issues.py

Index: infra/services/builder_alerts/crbug_issues.py
diff --git a/infra/services/builder_alerts/crbug_issues.py b/infra/services/builder_alerts/crbug_issues.py
index 31a04ff2d80c658469820b5b47f6d916e5718620..b4d49ab075175442e4bb2ae00845a8919ae4c2ad 100644
--- a/infra/services/builder_alerts/crbug_issues.py
+++ b/infra/services/builder_alerts/crbug_issues.py
@@ -21,6 +21,11 @@ WHITELISTED_LABELS = {'sheriff-chromium': 'chromium',
 BATCH_SIZE = 10
 
 
+issue_tracker_requests = ts_mon.CounterMetric(
+    'flakiness_pipeline/issue_tracker_requests',
+    description='Number of requests to the issue tracker')
+
+
 def _build_crbug_service(crbug_service_account):  # pragma: no cover
   with open(crbug_service_account) as crbug_sa_file:
     service_account = json.load(crbug_sa_file)
@@ -45,6 +50,8 @@ def _list_issues(crbug_service_account):
           projectId='chromium', label=whitelisted_label,
           startIndex=start_index, maxResults=BATCH_SIZE, can='open')
       response = request.execute(num_retries=5)
+      issue_tracker_requests.increment(
+          {'source': 'builder_alerts', 'operation': 'issues_list'})
   
       # Issue Tracker may omit certain issues occasionally, so counting whether
       # they add up to 'totalResults' in response is not relaible. However, we