chromeperf: Add anomaly config to anomalies

This change does two important things:

1. Changes the order of operation with anomaly detection, where we only
   perform the anomaly detection if there is a subscription associated
   with a measurement.

2. Associate the anomaly detection configuration to the anomalies found
   by the anomaly detection implementation.

For now we're only debug-logging the configurations that are served by
the sheriff-config service.

R=abennetts@google.com, fancl@chromium.org

Bug: chromium:1158326
Change-Id: Ic291ee289ca9b0a9e2180eaac814b0c7c18196aa
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/2814124
Commit-Queue: Dean Berris <dberris@chromium.org>
Reviewed-by: Chenlin Fan <fancl@chromium.org>
3 files changed
tree: 92a940a8d14f5274f92807df725de3a04f4e2179
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. firefighter/
  10. hooks/
  11. infra/
  12. netlog_viewer/
  13. systrace/
  14. telemetry/
  15. third_party/
  16. trace_processor/
  17. tracing/
  18. web_page_replay_go/
  19. .eslintignore
  20. .eslintrc
  21. .gcloudignore
  22. .gitignore
  23. .vpython
  24. AUTHORS
  25. BUILD.gn
  26. codereview.settings
  27. CONTRIBUTING.md
  28. DIR_METADATA
  29. generate_telemetry_build.py
  30. LICENSE
  31. navbar.md
  32. OWNERS
  33. PRESUBMIT.py
  34. pylintrc
  35. README.md
  36. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide