appengine/findit/crash/monitoring.py - Issue 2514413003: [Predator] Monitor found_suspects, has_regression_range and found_components using ts_mon

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: appengine/findit/crash/monitoring.py

Issue 2514413003: [Predator] Monitor found_suspects, has_regression_range and found_components using ts_mon (Closed)

Patch Set: Update docs. Created 4 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 # Copyright 2016 The Chromium Authors. All rights reserved.

	2 # Use of this source code is governed by a BSD-style license that can be

	3 # found in the LICENSE file.

	4

	5 import gae_ts_mon

	6

	7 found_suspects = gae_ts_mon.CounterMetric(

	8 'predator/found_suspects',

	9 description=('Metric monitoring ``found_suspects`` value of a '

	10 'crash analysis of Predator. This metric has fields like:'
	wrengr 2016/11/23 22:04:55 Much better :) The "crash analysis of Predator" p Much better :) The "crash analysis of Predator" part is still a bit awkward though. I'd rephrase to something like "Metric monitoring whether Predator found CLs for the crash reports". Similarly for the others. Sharu Jiang 2016/11/23 23:59:47 My bad documenting... thanks for the advises! Show quoted text On 2016/11/23 22:04:55, wrengr wrote: > Much better :) > > The "crash analysis of Predator" part is still a bit awkward though. I'd > rephrase to something like "Metric monitoring whether Predator found CLs for the > crash reports". Similarly for the others. My bad documenting... thanks for the advises!
	11 '{found_suspects: True/False,'

	12 ' client_id: Cracas/Fracas/Clusterfuzz}'))

	13

	14 has_regression_range = gae_ts_mon.CounterMetric(

	15 'predator/has_regression_range',

	16 description=('Metric monitoring ``has_regression_range`` value of a '

	17 'crash analysis of Predator. This metric has fields like:'

	18 '{has_regression_range: True/False,'

	19 ' client_id: Cracas/Fracas/Clusterfuzz}'))

	20

	21 found_components = gae_ts_mon.CounterMetric(

	22 'predator/found_components',

	23 description=('Metric monitoring ``found_components`` value of a '

	24 'crash analysis of Predator. This metric has fields like:'

	25 '{found_components: True/False,'

	26 ' client_id: Cracas/Fracas/Clusterfuzz}'))

OLD	NEW

« no previous file with comments | « appengine/findit/crash/crash_pipeline.py ('k') | appengine/findit/crash/test/crash_testcase.py » ('j') | no next file with comments »