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

Issue 876689 link

Starred by 1 user
Status: Verified
Owner:
antrim@chromium.org
Closed: Aug 30
Cc:
atwilson@chromium.org
antrim@chromium.org
█ snambiar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Add UMA to track idle time behavior for CRD access to Kiosks

Project Member Reported by mnissler@chromium.org, Aug 22 
issue 864384 adds support for admins to establish chromoting sessions with Kiosk devices.

To help the admin not invade user privacy, we decided that the device will perform idle detection before establishing the connection and warning the admin if there's recent user interaction (but allow to still connect).

We'd like to understand how this feature behaves in practice, hence the request to add a UMA histogram that collects data on how often admins end up connection to non-idle sessions in practice.

atwilson@ - since your team owns the feature, can you handle this?

Comment 1 by antrim@chromium.org, Aug 22 

By the design the client only receives the expected idleness (which can be 0, meaning that we can connect even if user is currently active).

We can report number of attempts that fail due to user activity, as well as number of successful attempts with 0 idleness cutoff. Does it sound reasonable?

Comment 2 by atwilson@chromium.org, Aug 22 

Is UMA the right way to track this vs a server-side dashboard? UMA is somewhat unreliable since customers may disable this.

Comment 3 by atwilson@chromium.org, Aug 28

Cc: atwilson@chromium.org
Owner: antrim@chromium.org
antrim@, let's log the UMA you suggest. It's easy to add and is a reasonable (albeit not 100% accurate) indicator of how admins are using this feature.
Project Member

Comment 4 by bugdroid1@chromium.org, Aug 30 

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

commit bcc1fe8c31d575cf8b24bd96fc854613abfa1efb
Author: Denis Kuznetsov <antrim@google.com>
Date: Thu Aug 30 19:00:25 2018

Add UMA to track idle time behavior for CRD access to Kiosks

Bug:  876689 
Change-Id: I999a7cdfaf703e898365b5838d06fc2d8615abe7
Reviewed-on: https://chromium-review.googlesource.com/1194075
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#587685}
[modify] https://crrev.com/bcc1fe8c31d575cf8b24bd96fc854613abfa1efb/chrome/browser/chromeos/policy/remote_commands/device_command_start_crd_session_job.cc
[modify] https://crrev.com/bcc1fe8c31d575cf8b24bd96fc854613abfa1efb/tools/metrics/histograms/histograms.xml

Comment 5 by antrim@chromium.org, Aug 30

Status: Fixed (was: Available)

Comment 6 by kathrelk...@chromium.org, Dec 3

Status: Verified (was: Fixed)
Enterprise.RemoteCommand.RemoteSession.*
►

Sign in to add a comment