New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 921588 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task



Sign in to add a comment

Setup monitoring for basic Chrome Sync health metrics

Project Member Reported by mamir@chromium.org, Jan 14

Issue description

There exist some UMA metrics in place (such as number of received invalidations, number of Client to Server messages ...etc.) that could be used to evaluate the health of sync infrastructure in Chrome.

We should setup:
1- A dashboard that would allow easier manual consumption of those metric.

2- Automated alerting system when something is fishy.



 
Labels: -Pri-3 Sync-Triaged Pri-2
Owner: mastiz@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 14

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cc6c745c687e366e6da39a6152d0d9e2c38469ad

commit cc6c745c687e366e6da39a6152d0d9e2c38469ad
Author: Mikel Astiz <mastiz@chromium.org>
Date: Mon Jan 14 21:54:04 2019

Add UMA for errors returned by sync server

This should allow investigate future issues and perhaps even do some
basic monitoring, for scenarios like users being throttled.

Bug: 921026,921588
Change-Id: Iff6036cd43863450f7561075cd8f9efb5a3a9f70
Reviewed-on: https://chromium-review.googlesource.com/c/1407084
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622620}
[modify] https://crrev.com/cc6c745c687e366e6da39a6152d0d9e2c38469ad/components/sync/engine_impl/syncer_proto_util.cc
[modify] https://crrev.com/cc6c745c687e366e6da39a6152d0d9e2c38469ad/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/cc6c745c687e366e6da39a6152d0d9e2c38469ad/tools/metrics/histograms/histograms.xml

Project Member

Comment 3 by bugdroid1@chromium.org, Jan 15

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d18eac6936e3c36c7b93c3a4811205879545c3f6

commit d18eac6936e3c36c7b93c3a4811205879545c3f6
Author: Mikel Astiz <mastiz@chromium.org>
Date: Tue Jan 15 07:50:40 2019

Add UMA to break down sync GetUpdates() per datatype

This metric should allow investigating regressions like increased
traffic load to sync servers.

Bug: 921026,921588
Change-Id: I93668afceab67014e43af01c24c2342120ab23ea
Reviewed-on: https://chromium-review.googlesource.com/c/1409555
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622771}
[modify] https://crrev.com/d18eac6936e3c36c7b93c3a4811205879545c3f6/chrome/browser/sync/test/integration/enable_disable_test.cc
[modify] https://crrev.com/d18eac6936e3c36c7b93c3a4811205879545c3f6/components/sync/engine_impl/syncer_proto_util.cc
[modify] https://crrev.com/d18eac6936e3c36c7b93c3a4811205879545c3f6/tools/metrics/histograms/histograms.xml

Sign in to add a comment