Update infra_libs to 1.1.15 / 0b44aba87c1c6538439df6d24a409870810747ab

appengine/third_party/gae_ts_mon/README.md

 # Setting up timeseries monitoring on App Engine.
 
 1.  Symlink this directory into your appengine app.
 
         cd infra/appengine/myapp
         ln -s ../../appengine_module/gae_ts_mon .
 
 1.  Add the scheduled task to your `cron.yaml` file.  Create it if you don't
     have one already.
 
@@ skipping 41 matching lines @@
         @endpoints.method(...)
         def your_method(self, request):
           ...
 
 1.  Give your app's service account permission to send metrics to the API.
     You need the email address of your app's "App Engine default service
     account" from the `IAM & Admin` page in the cloud console.  It'll look
     something like `app-id@appspot.gserviceaccount.com`.
     Add it as a "Service Account Actor" of the "App Engine Metric Publishers"
     service account in the
-    (google.com:prodx-mon-chrome-infra project)[https://console.developers.google.com/iam-admin/serviceaccounts/project?project=google.com:prodx-mon-chrome-infra&organizationId=433637338589]
+    [google.com:prodx-mon-chrome-infra project](https://console.developers.google.com/iam-admin/serviceaccounts/project?project=google.com:prodx-mon-chrome-infra&organizationId=433637338589)
     by selecting it from the list and clicking "Permissions".
     If you see an error "You do not have viewing permissions for the selected
     resource.", then please ask the current chrome-trooper to do it for you.
 
 1.  You also need to enable the Google Identity and Access Management (IAM) API
     for your project if it's not enabled already.
 
 You're done!  You can now use ts_mon metrics exactly as you normally would using
 the infra_libs.ts_mon module. Here's a quick example, but see the
 [timeseries monitoring docs](https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/ts_mon.md)
@@ skipping 63 matching lines @@
 only one instance will be running it at a time. A global metric is
 then cleared the moment it is sent.  Thus, global metrics will be sent
 at the correct intervals, regardless of the number of instances the
 app is currently running.
 
 Note also the use of `target_fields` parameter: it overrides the
 default target fields which would otherwise distinguish the metric per
 module, version, or instance ID. Using `target_fields` in regular,
 "local" metrics is not allowed, as it would result in errors on the
 monitoring endpoint, and loss of data.