PRTG Manual: Business Process Sensor

The Business Process sensor gives you a summarized status of entire business processes while monitoring several process components.

This means that you can create a customized sensor with channels based on data from other sensors ("source sensors") that are specific to your network.

The sensor can show the following:

  • Summarized status of the objects contained in each channel according to the individually defined error and warning thresholds
  • Overall and summarized status of all channels in the Global State channel

icon-i-roundThe Business Process sensor does not show values in the Downtime channel because they cannot be calculated for this sensor.

icon-i-roundIf you want to process values from other sensors and you want to perform calculations with these values, for example, use the Sensor Factory sensor instead.

icon-i-roundWhich channels the sensor actually shows might depend on the monitored device and the sensor setup.

Business Process Sensor

Business Process Sensor

Sensor in Other Languages

Dutch: Bedrijfs Proces, French: Processus métier, German: Business Process, Japanese: ビジネスプロセス, Portuguese: Processo de Negócio, Russian: Бизнес-процесс, Simplified Chinese: 业务进程, Spanish: Proceso commercial

Remarks

  • This sensor does not officially support more than 50 channels.
  • This sensor uses lookups to determine the status values of one or more sensor channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
  • Knowledge Base: How does the Business Process sensor calculate summarized sensor states?

Limited to 50 Sensor Channels

icon-i-bluePRTG does not officially support more than 50 sensor channels. Depending on the data used with this sensor, you might exceed the maximum number of supported sensor channels. In this case, PRTG will try to display all sensor channels. Be aware, however, that you will experience limited usability and performance.

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. 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.

Sensor Settings

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

icon-i-roundUsually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the Device Settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. 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.

Tags

Enter one or more Tags, separated by spaces or commas. 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.

There are default tags that are automatically predefined in a sensor's settings when you add a sensor. See section Default Tags below.

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

icon-i-roundIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

Priority

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

Default Tags

factorysensor, businessprocesssensor

Business Process Specific Settings

Channel Name

Enter a meaningful name to identify the channel. To add a new channel to the sensor, click the Enter Channel Name field, enter a name for the channel, and confirm with the Enter or Tab key.

icon-i-roundIt might take several sensor scans until new channel names or changes to existing channel names become visible.

Error Threshold %

Set a percentage limit to define when the sensor channel displays a Down status. Enter an integer value. The default is 50%.

icon-i-roundThis value depends on how many objects you feed into a Business Process sensor channel.

If the percentage of source objects in the "up" condition is less than the error threshold defines, the channel and the Global State channel of the Business Process sensor show a Down status.

The Sensor States that are mapped to the "up" condition icon-arrow-blue-up-full for a Business Process sensor channel are the following:

  • Up
  • Warning
  • Unusual
  • Down (Partial)

All other sensor states are mapped to the "down" condition icon-arrow-blue-down (see Up and Down Conditions below).

For example, if you define 4 source sensors for a channel, an error threshold of 50% means that 3 source sensors have to be in the "down" condition to set this channel to a Down status. So, 50% means that more than half of the source sensors must not be in the "up" condition to set the sensor to the Down status.

icon-book-bulbFor more information, an illustration of the business process mechanisms, and some use cases for the Business Process sensor, see the table below and the Knowledge Base: How can I use the Business Process sensor?

Warning Threshold %

Set a percentage limit to define when the sensor channel displays a Warning status. Enter an integer value. The default is 75%.

icon-i-roundThis value depends on how many objects you feed into a Business Process sensor channel.

If the percentage of source objects in the "up" condition than the threshold defines, the channel and the Global State channel of the Business Process sensor show a Warning status.

The Sensor States that are mapped to the "up" condition icon-arrow-blue-up-full for a Business Process sensor channel are the following:

  • Up
  • Warning
  • Unusual
  • Down (Partial)

All other sensor states are mapped to the "down" condition icon-arrow-blue-down(see Up and Down Conditions below).

For example, if you define 4 source sensors for a channel, a warning threshold of 75% means that all 4 source sensors have to be in the "down" condition to set this channel to a Warning status. So, 75% means that more than three out of four of the source sensors must not be in the "up" condition to set the sensor to the Warning status.

icon-book-bulbFor more information, an illustration of the business process mechanisms, and some use cases for the Business Process sensor, see the table below and the Knowledge Base: How can I use the Business Process sensor?

Objects

Enter the objects that you want to have in a channel by clicking button_add_objects. This way, you can select the desired objects from the device tree with the Object Selector. You can also start to type the object's ID, name, or a tag. PRTG then suggests the possible objects.

You can add sensors, devices, groups, and probes to a channel. Each object you add is weighted equally, no matter if it is a single sensor or a device with many sensors. To give more weight to a specific object, add it several times. For example, add the object twice to give double weight to it, add it three times to give it triple weight.

icon-i-roundA probe, group, or device is in the "up" condition icon-arrow-blue-up-full as long as it does not contain any sensors in the "down" condition icon-arrow-blue-down.

Up and Down Conditions

The Business Process "up" icon-arrow-blue-up-full and "down" icon-arrow-blue-down conditions are different from the normal Up and Down Sensor States. This is necessary for the Business Process sensor to be able to calculate summarized states and to show a calculated result for an entire business process. This table illustrates which sensor status leads to which Business Process condition.

The Relation Between Object States And Business Process Conditions

Channel Object Status

Business Process Condition

Reason: Why does a specific sensor status correspond to a specific Business Process condition?

led_green_big Up

Up

icon-arrow-blue-up-full

The monitored object works, so everything is fine.

led_yellow_big Warning

Up

icon-arrow-blue-up-full

The sensor may show a warning, but the monitored object still works.

icon_green-red Down (Partial)

Up

icon-arrow-blue-up-full

This status is available in a cluster setup and is displayed if at least one cluster node reports the sensor as Up and at least one cluster node reports it as Down. With at least one Up report, the monitored object is supposed to be working and meets the Business Process "up" condition.

led_orange_big Unusual

Up

icon-arrow-blue-up-full

The sensor may show unusual values, but the monitored object works.

led_grey_big Collecting

Up

icon-arrow-blue-up-full

The sensor is still waiting for more monitoring data to definitely decide on the sensor status, but so far the monitored object works. This PRTG internal status is visualized as Unknown in the PRTG web interface.

led_red_big Down

Down

icon-arrow-blue-down

The monitored object does not work.

led_grey_big Unknown

Down

icon-arrow-blue-down

The sensor does not know if the monitored object works, for example because it has not yet received any data or because it has not received any data for a certain amount of time.

led_grey_big None

Down

icon-arrow-blue-down

The sensor has not yet received any monitoring data from the monitored object. This PRTG internal status is visualized as Unknown in the PRTG web interface.

led_blue_big Paused

Down

icon-arrow-blue-down

The monitored object does not work and monitoring has been paused, for example actively by the user, by inheritance, or by schedules. It might be convenient to exclude regularly or frequently paused objects from your business process monitoring, so you do not give more weight than necessary to a Business Process "down" condition because of issues you already know about.

led_redok_big Down (Acknowledged)

Down

icon-arrow-blue-down

The monitored object does not work and someone already knows.

icon-i-roundIf you encounter issues with your Business Process sensor and want to contact our support team, send us your exact configuration. It helps us find the cause more easily and quickly. Click the clipboard icon in the upper-right corner of the Business Process Specific Settings table to copy your configuration:

The Business Process Sensor Configuration Clipboard

The Business Process Sensor Configuration Clipboard

A window opens that contains your configuration. Copy the highlighted text and paste it into the support form to send it to our support team.

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 is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

icon-i-roundYou can set a different primary channel later by clicking the pin symbol of a channel on the sensor's Overview tab.

Graph Type

Define how different channels will be shown for this sensor.

  • Show channels independently (default): Show a 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 a graph that visualizes the different components of your total traffic.
    icon-i-roundThis option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channel Settings settings).

Stack Unit

This field is only visible if you enable Stack channels on top of each other above. Select 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 of the following settings are inherited from objects that are 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. For more information, see section Inheritance of Settings. To change a setting for this object only, disable inheritance by clicking the button next to inherit from under the corresponding setting name. You will then see the options described below.

Scanning Interval

Click inherited_settings_button to interrupt the inheritance. See section Inheritance of Settings for more information.

Scanning Interval

Select a scanning interval (seconds, minutes, or hours). The scanning interval determines the amount of time that the sensor waits between two scans. You can change the available intervals in the system administration on PRTG on premises installations.

If a Sensor Query Fails

Define the number of scanning intervals that the sensor has time to reach and check a device again in case a sensor query fails. Depending on the option that you select, the sensor can try to reach and check a device again several times before the sensor will show a Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor will show a Warning status. Choose from:

  • Set sensor to down immediately: Set the sensor to a Down status immediately after the first failed request.
  • Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to a Warning status after the first failed request. If the following request also fails, the sensor will show an error.
  • Set sensor to warning for 2 intervals, then set to down: Set the sensor to a Down status only after three consecutively failed requests.
  • Set sensor to warning for 3 intervals, then set to down: Set the sensor to a Down status only after four consecutively failed requests.
  • Set sensor to warning for 4 intervals, then set to down: Set the sensor to a Down status only after five consecutively failed requests.
  • Set sensor to warning for 5 intervals, then set to down: Set the sensor to a Down status only after six consecutively failed requests.

icon-i-roundSensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show a Down status. It is not possible to immediately set a WMI sensor to a Down status, so the first option will not apply to these sensors. All other options can apply.

icon-i-roundIf you define error limits for a sensor's channels, the sensor will immediately show a Down status. No "wait" option will apply.

icon-i-roundIf a channel uses lookup values, the sensor will immediately show a Down status. No "wait" options will apply.

Schedules, Dependencies, and Maintenance Window

icon-i-roundYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. 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.

Schedule

Select a schedule from the list. Schedules can be used to monitor for a certain time span (days or hours) every week.

icon-book-arrowsYou can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Account Settings—Schedules.

icon-i-roundSchedules are generally inherited. New schedules will be added to existing schedules, 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, the current sensor and all child objects will not be monitored. They will be in a Paused status 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.

icon-i-roundTo terminate a current maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

This field is only visible if you enable Set up a one-time 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 enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the maintenance window.

Dependency Type

Define a dependency type. You can use dependencies to pause monitoring for an object depending on the status of another object. You can choose from:

  • Use parent: Use the dependency type of the parent device.
  • Select a sensor: Use the dependency type of the parent device. Additionally, pause the current sensor if another specific sensor is in a Down status or in a Paused status caused by another dependency. Select below.
  • Master sensor for parent: Make this sensor the master object for its parent device. The sensor will influence the behavior of its parent device: If the sensor is in a 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 is paused by another dependency.

icon-i-roundTo test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects will be paused. You can check all dependencies in your PRTG installation by selecting Devices | Dependencies from the main menu bar.

Dependency

This field is only visible if you enable Select a sensor above. Click the Search button and use the object selector to select a sensor on which the current sensor will depend.

Dependency Delay (Sec.)

This field is only visible if you enable Select a sensor above. Define a time span in seconds for dependency delay.

After the master sensor for this dependency comes back to an Up status, monitoring of the dependent objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Enter an integer value.

icon-i-round-redThis setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent Device Settings or in its parent Group Settings.

Access Rights

Click inherited_settings_button to interrupt the inheritance. See section Inheritance of Settings for more information.

User Group Access

Define the user groups that will have access to the selected object. 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 but it cannot be accessed.
  • 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 its settings. They cannot edit access rights settings.
  • Full: Users in this group can see the object, review its monitoring results, edit its 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.

icon-book-arrowsFor more details on access rights, see section User Access Rights.

More

Knowledge Base: How does the Business Process sensor calculate summarized sensor states?

Knowledge Base: How can I use the Business Process sensor?

Knowledge Base: How can I avoid numerous notifications for branch offices?

Edit Sensor Channels

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

Notification Triggers

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

Others

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

Sensor Settings Overview

For information about sensor settings, see the following sections: