diff options
author | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-30 21:32:24 +0000 |
---|---|---|
committer | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-30 21:32:24 +0000 |
commit | 3e2dbbc1fa2f7160ecb0b88e58f6c4422ac3ec67 (patch) | |
tree | 7a91f035bd0cfbbda181aec85dcc6fb0a596ac03 /sync/sessions/sync_session.h | |
parent | 6c14fefae02783edf15a7012a36d8c2d8af76759 (diff) | |
download | chromium_src-3e2dbbc1fa2f7160ecb0b88e58f6c4422ac3ec67.zip chromium_src-3e2dbbc1fa2f7160ecb0b88e58f6c4422ac3ec67.tar.gz chromium_src-3e2dbbc1fa2f7160ecb0b88e58f6c4422ac3ec67.tar.bz2 |
Track merged nudge sources
There's a lot of valuable information in coalesced nudges. Currently, one
nudge source can overwrite another, which leaves us in the dark as to why the
client behaved a certain way. In fact, today we can't even determine whether
or not any coalescing was done.
By logging all the coalesced sources and their payloads, we can learn a lot
more about client behaviour. I'm hoping to use this to improve our
notification effectiveness metrics.
BUG=138613
Review URL: https://chromiumcodereview.appspot.com/11416126
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170549 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/sessions/sync_session.h')
-rw-r--r-- | sync/sessions/sync_session.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sync/sessions/sync_session.h b/sync/sessions/sync_session.h index 19cba8c..58065b7 100644 --- a/sync/sessions/sync_session.h +++ b/sync/sessions/sync_session.h @@ -165,6 +165,10 @@ class SyncSession { // The source for initiating this sync session. SyncSourceInfo source_; + // A list of sources for sessions that have been merged with this one. + // Currently used only for logging. + std::vector<SyncSourceInfo> debug_info_sources_list_; + // Information about extensions activity since the last successful commit. ExtensionsActivityMonitor::Records extensions_activity_; |