<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Google Drive Sensor

The Google Drive sensor monitors a Google Drive account via the Google application programming interface (API) and Open Authorization 2 (OAuth2).

For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

• Dutch: Google Drive
• French: Google Drive
• German: Google Drive
• Japanese: Google ドライブ
• Portuguese: Google Drive
• Russian: Google Диск
• Simplified Chinese: Google Drive
• Spanish: Google Drive

Remarks

• For details about OAuth2 authentication, see section Authentication via OAuth2.

• This sensor has a low performance impact.

• This sensor only supports the IPv4 protocol.

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.

PRTG requires OAuth2 authorization before you can add this sensor. Provide the required credentials in the dialog box that appears.

Google Credentials

This sensor uses OAuth2 authentication to get access to your Google account.
For details about this authentication approach, see section Authentication via OAuth2.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.

Google Credentials

Sensor Display

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.

For more information, see section Inheritance of Settings.

Scanning Interval

For more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

For more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.

For more information, see section Root Group Settings, section Channel Unit Configuration

Authentication via OAuth2

This sensor uses the OAuth2 security protocol to access the account from which you want to retrieve and monitor data. OAuth2 enables you to grant access to the target account without sharing your password with PRTG. The authorization approach of PRTG using OAuth2 works as follows.

1. Authorization Request
   First, you must request authorization for this sensor to access service resources from your account. For this purpose, you are asked to get an access code for this sensor in the Add Sensor dialog. Click Get Access Code to start the authorization process using OAuth2. A new browser window opens on the authorization server of the target service.
2. Verifying Identity
   This new window contains a login form for your account that you want to monitor. Log in to your account using your credentials for this service to authenticate your identity. This is a common login to your account on the target server so PRTG does not see your password. The service forwards you to the authorization page and asks you to permit PRTG to access the data in your account.
   If you are already logged in to the service with a user account, you do not need to enter credentials in this step and get directly to the access permission page.
3. Authorizing PRTG
   Permit PRTG to access information on your account. Note that this permission holds only for this specific sensor, not for other sensors of this type or PRTG as a whole. For each sensor of this type you add, you must confirm the access permission anew. You can change the account permissions at any time in your account at the target service.
4. Getting Authorization Code
   Permitting PRTG to access your account data forwards you to a page where the service provides an authorization code. Copy this code and switch back to the Add Sensor dialog in PRTG.
   The code is only valid for a short period of time and expires after a few minutes.
   You can use a particular code only once.
5. Providing Authorization Code
   Paste the authorization code into the OAuth Code field and complete the Add Sensor dialog. You do not need to go through further configuration steps manually. The sensor automatically accomplishes the following steps.
6. Requesting Access Token
   After receiving the authorization code, PRTG requests an access token from the API of the target service. For this purpose, PRTG transmits the authorization code together with several authentication details. The API checks if the authorization is valid and returns the access token to PRTG. Access tokens are specific for one account and one application (here: PRTG). The authorization process to read data from your account is now complete.
7. Retrieving Data
   The sensor transmits the access token with each sensor scan in the defined scanning interval to authenticate with your account. It is not necessary to use the original account credentials anew. The used tokens refresh automatically from time to time.

Channel List

Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

More

Knowledge Base

What security features does PRTG include?

• https://kb.paessler.com/en/topic/61108