Search
Clear search
Close search
Google apps
Main menu

Chrome kiosk health monitoring

You can remotely monitor Chrome devices running Chrome 43 and later to make sure they’re functioning properly. This functionality is only available for Chrome devices configured to auto-launch a Chrome packaged app or a Public Session. These Chrome devices can include kiosks, digital signs, and purpose-built devices like check-out stands and self service kiosks.

If your Chrome device goes offline, you can opt in to receive an email or text message notifying you about this. Even if the app is crashing, you will still get these alerts because they’re sent at the operating-system level. If your device goes offline, you can see the connectivity history in the reporting, and can have an alert sent to you if a kiosk device goes offline. Additionally, you can choose who gets notified via email or SMS when there’s an outage.

Health monitoring settings

  1. Sign in to the Admin console.
  2. Go to Device Management > Chrome devices
  3. Click on the serial number of the device you want to monitor. Under System Activity and Troubleshooting, you can see the following:
Setting What it monitors
Active Times Shows up to the last 15 days of activity on the device, including when it was last used and for how long. The times and dates shown are based on the time zone of the device. You can turn this feature on in the Admin console at Device management > Chrome management > Device settings > Device State Reporting.
Recent Users Displays the last users of the Chrome device. Public, kiosk, and guest-mode sessions are not reported. Email addresses for unmanaged users are not displayed; instead these display as "User not managed by your domain". You can turn on this feature in the Admin console at Device management > Chrome management > Device settings > Device Reporting Device User Tracking.
Wifi Signal

Shows the Wi-Fi signal strength for devices in kiosk mode.

Device Volume (Audio)

Shows the volume level for devices in kiosk mode.

CPU Utilization Displays how much of the CPU the Chrome device is using.
CPU Temperatures Displays the temperature of each CPU core in degrees celsius.
Memory Usage Displays how much memory the Chrome device is using.
Disk Space Shows how much of the disk space the device is using.
Kiosk App Info Reports app name and version number. This feature is not available for devices that are in public-session mode.
IP Addresses Last Updated Time Shows the last date and time the LAN and WAN IP addresses for the device were reported. The time and date are based on the time zone of the device. IP addresses are only reported when the device is in public session or kiosk mode. The IP address will stop being reported when a user signs in.
LAN IP Address Displays the wired or wireless network that your device is connected to. In certain businesses, you can use this to locate the exact floor and building the device is in. This feature is not available when a user is signed in to the device with a Google account.
WAN IP Address Shows the unique IP address that the device is connected to the Internet with. This feature is not available when a user is signed in to the device with a Google account.
Device Volume (Audio)

Remotely sets the volume level for managed devices in kiosk mode.

Enter a value between 0 and 100 and click Set volume. You’ll see a message that lets you know if the volume was successfully set on the device.

Reboot Device Clicking Reboot Now will restart the Chrome device if it's been running for at least 10 minutes. For more restart options, see FAQ.
Screen Capture

Clicking Capture takes a screenshot of the device's screen and stores it in Screen Captures.

The most recent screen captures of Chrome devices are listed in reverse chronological order. Click a blue link to view the screen capture.

If a screen capture fails, you’ll see a message with one of the following error codes:

  • 0—Generic failure.
  • 1—Screen capture failed because user input was detected.
  • 2—Failed to get screenshots. For example, there is no screen connected to the device.
  • 3, 4—Failed due to server error.
  • 5—Failed due to client error.
  • 6—Failed because the upload url is invalid.

Note: Devices that are in kiosk mode but have had user input (for example, mouse or keyboard movements within a kiosk session) are not eligible for screenshots until they are reset. If an input is detected, screenshots can't be taken until the device is restarted to reset the input trigger. The device must auto-launch into a kiosk app for screenshots to work.

Device Logs and attributes Clicking Capture triggers a fresh upload of device attributes and logs on devices in kiosk mode. You’ll see a message that lets you know if the device attributes were successfully uploaded.
System Logs

Shows system logs that were automatically captured from kiosk devices. When Device system log upload is enabled, system logs are captured every 12 hours and uploaded here. Logs are stored for a maximum of 60 days. At any one time, 7 logs are available for download—1 for each day for the past 5 days, 1 for 30 days ago, and 1 for 45 days ago.

Tip: Use Log Analyzer to examine the system logs.

Health monitoring status displays

  1. Sign in to the Admin console.
  2. Go to Device management > Chrome management > Device settings.
  3. Under Device State Reporting, set Enable device state reporting.

After doing this, when you go to Device management > Chrome devices, you'll see an Online Status column. A green circle means that the device is online and working properly. Heartbeats are sent every few minutes to check if devices are still online. If a device goes offline, it can take up to 12 minutes for the online status of the device to be updated and a further 5 minutes before you receive an email or SMS alert.

The device status can be in one of these three states:

Device status color What it means
Green The device is running in kiosk mode and the admin has opted-in to reporting and monitoring. This monitoring also works for Chrome devices devices set to Auto-Launch Public Session and auto-login is set to 0.
Red The device is not successfully sending “heartbeats” to Google servers. These are sent every 120 seconds. The device may be turned off or could have network connectivity issues.
Grey The device is not eligible for health monitoring. This could be caused by either of these scenarios:
  • Your Chrome device is running a version of Chrome prior to Chrome 43. It needs to be running Chrome 43 or later for monitoring to work.
Or
  • There is an active user on the system. For example, if they aborted the kiosk app from loading at startup, then you won’t be able to use device monitoring.

Configure health reporting

  1. Sign in to the Admin console.
  2. Go to Device management > Chrome management > Device settings.
  3. Set Kiosk Settings to Auto-Launch Kiosk App. Also, Enable device health monitoring.
Auto-launch kiosk app and monitoring

Because this is a device setting, it can be configured by organizational unit. For example, you may have devices organized by physical location or type of device.

Fill out Kiosk Device Status Alerting Contact Info. Put email addresses or phone numbers you want to receive status updates in. Note that you will only receive one message per outage.

Under Kiosk Device Status Alerting Delivery, check whether you want to receive updates by email, SMS, or both.

If you use SMS, format the number like the following. Put country code followed by the full number. For an example, a United States phone number would be formatted like the following: +1 country code, and then the full 10 digit number. Example: +16502530000

FAQs

How do I schedule a Chrome device to reboot?

There are 3 ways to remotely reboot a Chrome device.

  1. Reboot on-demand using the Reboot Now setting (see the first table above).
  2. Use the Chrome Kiosk App tool to program the reboot schedule.
  3. Use the Scheduled Reboot setting in the Admin console with the following tips:
  • A kiosk app should use chrome.power.requestKeepAwake() to ensure that the device stays on. This is enabled by default with most kiosk apps.
  • An admin can schedule Chrome devices to reboot using the Admin console with up to one-day granularity. When the day to reboot comes, Google sends the the app a notification to reboot via chrome.runtime.onRestartRequired. The app should be programed to receive this notification.
  • When the notification arrives, the app has one day to choose a good time to reboot (often when the app is idle). When the app calls chrome.power.releaseKeepAwake(), the device reboots.

For more information, see the chrome.power API and the design doc on Chromium.

Was this article helpful?
How can we improve it?