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

Issue 845407 link

Starred by 2 users
Status: Fixed
Owner:
marinaciocea@chromium.org
Closed: May 2018
Cc:
█ olka@chromium.org
maxmorin@chromium.org
solenberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Add observed audio service lifetime UMA metrics

Project Member Reported by marinaciocea@chromium.org, May 22 2018 
Add UMA metrics to AudioServiceListener:
1. Startup time: time between created and started received
2. Service start status (count hist)
   - Failed to start: count - check when called
   - Succeeded to start - count
   - Init
3. Service process stop status (count hist)
   - Process disconnect
   - Process killed
   - Process crashed
4. Downtime: time between service started and service stopped
5. Uptime: time between service started and service stopped
Project Member

Comment 1 by bugdroid1@chromium.org, May 23 2018 

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

commit a24a3874335d2b14a32f20d2b8911a788efd2a17
Author: Marina Ciocea <marinaciocea@chromium.org>
Date: Wed May 23 22:59:16 2018

Add observed audio service lifetime UMA metrics.

Add lifetime metrics for audio service, logged from browser process in AudioServiceListener.
List of added metrics:
- ObservedStartupTime: how long it took audio service to start.
- ObservedStartStatus: success, failure, or service started before listener.
- ObservedServiceProcessTerminationStatus: disconnect (normal termination), kill (e.g through
  SIGKILL or taskmanager kill) or crash.
- ObservedDowntime: time between service started or listener init and service stopped.
- ObservedUptime: time between service started and service stopped (normal stop, kill or crash).

Audio service design doc: https://docs.google.com/document/d/1s_Fd1WRDdpb5n6C2MSJjeC3fis6hULZwfKMeDd4K5tI/edit?usp=sharing

Bug:  845407 
Change-Id: I1d55314a40d00e64942d63eba1b8de6b392beceb
Reviewed-on: https://chromium-review.googlesource.com/1068709
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561296}
[modify] https://crrev.com/a24a3874335d2b14a32f20d2b8911a788efd2a17/content/browser/renderer_host/media/audio_service_listener.cc
[modify] https://crrev.com/a24a3874335d2b14a32f20d2b8911a788efd2a17/content/browser/renderer_host/media/audio_service_listener.h
[modify] https://crrev.com/a24a3874335d2b14a32f20d2b8911a788efd2a17/content/browser/renderer_host/media/audio_service_listener_unittest.cc
[modify] https://crrev.com/a24a3874335d2b14a32f20d2b8911a788efd2a17/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/a24a3874335d2b14a32f20d2b8911a788efd2a17/tools/metrics/histograms/histograms.xml

Comment 2 by marinaciocea@chromium.org, May 24 2018

Status: Fixed (was: Started)

Comment 3 by anatolid@chromium.org, Jun 7 2018 

[bulk-edit: disregard if N/A] Can the owner please set milestone to this bug if applicable?
►

Sign in to add a comment