The page below is from the manual of PRTG, our quick-to-install and easy-to-use network monitoring software

Try PRTG now and see how it can make your job easier.

Free Trial Download
You will be up and running in 2 minutes
Learn More
Screenshots, Features, Videos

Aurelio, System Admin at Paessler AG

The Common SaaS Sensor monitors the availability of several Software as a Service (SaaS) providers. Because your business processes more and more depend on cloud hosts, this sensor type is an important pillar for unified monitoring. With this sensor you can get alarms if your cloud services are not reachable anymore.

This sensor shows the following:

  • Available services in percent
  • Response times of the following SaaS providers:
    • Bing
    • Dropbox
    • Facebook
    • GitHub
    • Google Apps
    • Office 365
    • Salesforce
    • Twitter
    • Youtube
Common SaaS SensorCommon SaaS Sensor

Click here to enlarge:


  • The server on which the PRTG probe with this sensor runs must have access to the internet.
  • PRTG creates this sensor automatically on every new probe device. If the system running the probe has no connection to the internet, please pause or delete this sensor manually to avoid error messages.
  • This sensor type has predefined limits for several metrics. You can change these limits individually in the channel settings. For detailed information about channel limits, please refer to the manual section Sensor Channels Settings.

Add Sensor

The Add Sensor dialog appears when adding a new sensor to a device manually. It only shows the setting fields that are required for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.

Select which SaaS providers you want to monitor. The sensor creates one channel for each service you choose in the Add Sensor dialog.

The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page.

Common SaaS Specific

SaaS Checklist

Select the services you want to monitor with this sensor. You see a list with the names of all items which are available to monitor. Select the desired items by adding check marks in front of the respective lines. The sensor creates on channel for each selection. You can also select and deselect all items by using the check box in the table head.

Sensor Settings

On the details page of a sensor, click on the Settings tab to change its settings.

Note: Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created this sensor. See the Device Settings for details. For some sensor types, you can define the monitoring target explicitly in the sensor settings. Please see below for details on available settings.

Basic Sensor Settings

Sensor Name

Enter a meaningful name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

Parent Tags

Shows Tags that this sensor inherits from its parent device, group, and probe. This setting is shown for your information only and cannot be changed here.


Enter one or more Tags, separated by space or comma. You can use tags to group sensors and use tag–filtered views later on. Tags are not case sensitive. We recommend that you use the default value.

You can add additional tags to it, if you like. Other tags are automatically inherited from objects further up in the device tree. These are visible above as Parent Tags.


Select a priority for the sensor. This setting determines where the sensor is placed in sensor lists. Top priority is at the top of a list. Choose from one star (low priority) to five stars (top priority).

Common SaaS Specific

Period (Interval)

Define the scanning interval of this sensor. The period you choose here specifies how often the sensor requests the target services. Choose between:

  • 15 minutes
  • 30 minutes
  • 1 hour
  • 4 hours
  • 6 hours
  • 12 hours
  • 24 hours

Note: This sensor cannot inherit scanning intervals nor use other intervals than given here.

Debug Options

Sensor Result

Define what PRTG will do with the sensor results. Choose between:

  • Discard sensor result : Do not store the sensor result.
  • Write sensor result to disk (Filename: "Result of Sensor [ID].txt") : Store the last result received from the sensor to the "Logs (Sensor)" directory (on the Master node, if in a cluster). File names: Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt . This is for debugging purposes. PRTG overrides these files with each scanning interval. For more information on how to find the folder used for storage, please see the Data Storage section.

Sensor Display

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed below the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's Overview tab.

Graph Type

Define how different channels will be shown for this sensor.

  • Show channels independently (default) : Show an own graph for each channel.
  • Stack channels on top of each other : Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Settings settings).

Stack Unit

This setting is only available if stacked graphs are selected above. Choose a unit from the list. All channels with this unit will be stacked on top of each other. By default, you cannot exclude single channels from stacking, if they use the selected unit. However, there is an advanced procedure to do so.

Inherited Settings

By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root group's settings. To change a setting only for this object, disable inheritance by clicking on the check mark before the corresponding setting name. You will then see the options described below.

Schedules, Dependencies, and Maintenance Window

Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted. The corresponding settings from the parent objects will always be active. However, you can define additional settings here. They will be active at the same time as the parent objects' settings.


Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) every week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings.

Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active at the same time.

Maintenance Window

Specify if you want to set up a one-time maintenance window. During a "maintenance window" period, this object and all child objects will not be monitored. They will be in a paused state instead. Choose between:

  • Not set (monitor continuously) : No maintenance window will be set and monitoring will always be active.
  • Set up a one-time maintenance window : Pause monitoring within a maintenance window. You can define a time span for a monitoring pause below and change it even for a currently running maintenance window.

Note: To terminate a current maintenance window before the defined end date, change the time entry in Maintenance Ends field to a date in the past.

Maintenance Begins

This field is only visible if you enabled the maintenance window above. Use the date time picker to enter the start date and time of the maintenance window.

Maintenance Ends

This field is only visible if you enabled the maintenance window above. Use the date time picker to enter the end date and time of the maintenance window.

Dependency Type

Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between:

  • Use parent : Pause the current sensor if the device, where it is created on, is in Down status, or is paused by another dependency.
  • Select object : Pause the current sensor if the device, where it is created on, is in Down status, or is paused by another dependency. Additionally, pause the current sensor if a specific other object in the device tree is in Down status, or is paused by another dependency. Select below.
  • Master object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device, where it is created on: If the sensor is in Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in Down status, or if it is paused by another dependency.

Note: Testing your dependencies is easy! Simply choose Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. You can check all dependencies in your PRTG installation by selecting Devices | Dependencies from the main menu bar.


This field is only visible if the Select object option is enabled above. Click on the reading-glasses and use the object selector to choose an object on which the current sensor will depend.

Dependency Delay (Sec.)

Define a time span in seconds for a dependency delay. After the master object for this dependency goes back to Up status, PRTG will start monitoring the depending objects after this extra delayed. This can help to avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value.

Note: This setting is not available if you choose this sensor to Use parent or to be the Master object for parent . In this case, please define delays in the parent Device Settings or in the superior Group Settings .

Access Rights

User Group Access

Define which user group(s) will have access to the object you're editing. A table with user groups and types of access rights is shown: It contains all user groups from your setup. For each user group you can choose from the following access rights:

  • Inherited : Use the access rights settings of the parent object.
  • None : Users in this group cannot see or edit the object. The object neither shows up in lists nor in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible.
  • Read : Users in this group can see the object and review its monitoring results.
  • Write : Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings.
  • Full : Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.

You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option.

For more details on access rights, please see the section User Access Rights .

Edit Sensor Channels

To change display settings, spike filter, and limits, switch to the sensor's Overview tab and click the gear icon of a specific channel. For detailed information, please see the Sensor Channels Settings section.


Click the Notifications tab to change notification triggers. For detailed information, please see the Sensor Notifications Settings section.


For more general information about settings, please see the Object Settings section.

Sensor Settings Overview

Copyright © 1998 - 2017 Paessler AG