Fix Predator metric |
||||
Issue description
As Aaron suggested (many thanks!), the metric should be as below instead of those in predator/common/monitoring.py
reports_processed = gae_ts_mon.CounterMetric(
'predator/reports_count',
'Metric counting the number of crash reports that Predator has processed. '
'Contains fields describing whether Predator was successful at finding a '
'regression range, a components, or suspect changes for each report.',
[gae_ts_mon.BooleanField('found_suspects'),
gae_ts_mon.BooleanField('found_components'),
gae_ts_mon.BooleanField('has_regression_range'),
gae_ts_mon.StringField('client_id')])
,
Oct 31 2017
,
Nov 2 2017
,
Jan 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/45c1a38001a3e900766f4eb743749be60ddb1c1f commit 45c1a38001a3e900766f4eb743749be60ddb1c1f Author: Sharu Jiang <katesonia@google.com> Date: Wed Jan 03 19:17:07 2018 [Predator] Modify monitoring metrics. Bug: 729149 Change-Id: Ib86d89d01455435a85ed0d167122ac5a5a5dc867 Reviewed-on: https://chromium-review.googlesource.com/848304 Commit-Queue: Sharu Jiang <katesonia@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> [modify] https://crrev.com/45c1a38001a3e900766f4eb743749be60ddb1c1f/appengine/predator/app/common/monitoring.py [modify] https://crrev.com/45c1a38001a3e900766f4eb743749be60ddb1c1f/appengine/predator/app/common/crash_pipeline.py
,
Jan 17 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by kateso...@chromium.org
, Oct 31 2017