[buildbucket] add MaxAgeScheduled in metric

This CL ports the V1 metric, and adds a V2 equivalent.

Note that PyBB and GoBB will compute and report the data
individually, once this CL is landed. However,
all the alert and dashboard configs use m.Max().
Therefore, it should be ok to have the duplicate data temporarily.

Once the data correctness is checked, PyBB will be updated to stop
computing MaxAgeScheduled.

Bug: 1249664
Change-Id: I45d93069b9b53e518fcf9cba73ad0c712d8dc3f2
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3299391
Commit-Queue: Scott Lee <ddoman@chromium.org>
Reviewed-by: smut <smut@google.com>
4 files changed
tree: 6db70c513b15371ca75ee8311d5783a81e16e9bf
  1. appengine/
  2. auth/
  3. auth_service/
  4. build/
  5. buildbucket/
  6. casviewer/
  7. cipd/
  8. client/
  9. cmdrunner/
  10. common/
  11. config/
  12. cv/
  13. dm/
  14. examples/
  15. gae/
  16. gce/
  17. grpc/
  18. hacks/
  19. hardcoded/
  20. led/
  21. logdog/
  22. luci_notify/
  23. lucicfg/
  24. lucictx/
  25. luciexe/
  26. machine-db/
  27. mailer/
  28. milo/
  29. mmutex/
  30. resultdb/
  31. scheduler/
  32. scripts/
  33. server/
  34. starlark/
  35. swarming/
  36. tokenserver/
  37. tools/
  38. tumble/
  39. vpython/
  40. web/
  41. .gitallowed
  42. .gitattributes
  43. .golangci.yml
  44. AUTHORS
  45. codereview.settings
  46. CONTRIBUTING.md
  47. CONTRIBUTORS
  48. go.mod
  49. go.sum
  50. LICENSE
  51. OWNERS
  52. PRESUBMIT.py
  53. README.md
  54. tools.go
  55. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.