> ## Documentation Index
> Fetch the complete documentation index at: https://doc.qbilon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# PRTG Sensor Creator

> Configure the creation of PRTG devices and sensors from Qbilon assets.

## Preface

The PRTG Sensor Creator enables users to create tasks within automations that generate devices and associated sensors based on conditions defined by the user.

Multiple devices or sensors can be created in a batch depending on the information that Qbilon has collected about the IT landscape. In addition, several Sensor Creators can be created that address different PRTG Core Servers in order to keep the monitoring compliant with the actual assets across a larger IT landscape.

A practical example of use is described here: [Automate PRTG Monitoring](https://doc.qbilon.io/13-how-to/automate-prtg-monitoring/index).

> [!NOTE]
>
> Even if the name displayed in Qbilon does not imply it directly, the Sensor Creator can also be used to create devices without sensors.

## Configuration

The "PRTG Sensor Creator" is one of several PRTG-specific task types that can be found in the “Data Writer” section:

![PRTG Sensor Creator: Configuration](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/fe1ab8eb-5f9b-4a93-892d-a33feb0c45aa-screenshot-2026-10-06-175725.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=0f61447c9285348623b47daf43f35e83)

### Name and Identifier

This is the name that will be displayed for this task within an automation. This name can be chosen freely. Qbilon automatically generates a valid identifier from the name, so it does not need to be edited by the user. The name can express which PRTG core the task was created for, for example, if you have several core servers in use.

### Host and API Token

The host information is required so that the PRTG Sensor Creator knows on which PRTG core server it should create devices or sensors. Here you only need to enter the URL under which your PRTG system is accessible.

The API token must have been created by the user in PRTG beforehand and should have “Full access” rights to ensure that the PRTG Sensor Creator has the necessary permissions to create the defined assets in the PRTG instance.

The API token can be created in PRTG under "Setup → Account Settings → API Keys":

![PRTG Sensor Creator: Host and API Token](https://mintcdn.com/qbilon-docs/aJQhbcvq7mtvhV0w/.gitbook/assets/43ab8831-2466-458f-8c73-bb02910c1a8d-image.png?fit=max\&auto=format\&n=aJQhbcvq7mtvhV0w\&q=85\&s=3d4c5783281145476fda097dcaf4f18a)

> [!NOTE]
>
> The API token created has the same access rights as the user who created it. If possible, the same user should be used as for reading the PRTG data via a [PRTG connector](https://doc.qbilon.io/06-data-sources/internal-connectors/prtg.md), as otherwise the visible groups, devices and sensors may differ from those that the user will create.

### Allow Insecure Connections

Select this option if you are running PRTG with a self-signed certificate (the default installation) or if the certificate was issued by an unknown Trusted Third Party Authority that is not traditionally found in the default Java Trust Stores. Otherwise, connection problems may occur.

### Group ID

Please enter the ID of the group under which the devices and their sensors are to be created. You can find the group ID in your PRTG instance by navigating to the relevant group on the right-hand side, where you will also find the group's status and other high-level information:

![PRTG Sensor Creator: Group ID](https://mintcdn.com/qbilon-docs/aJQhbcvq7mtvhV0w/.gitbook/assets/3ce30867-0e68-468f-99c4-80c393e317a4-image.png?fit=max\&auto=format\&n=aJQhbcvq7mtvhV0w\&q=85\&s=01692f4aff95f51f7112d0035ce972b4)

> [!NOTE]
>
> Important: only enter the numerical value of the ID, i.e. WITHOUT the hashtag. Make sure that you do not enter any superfluous spaces.

### Type

Use the type configuration parameter to select which PRTG assets from the recorded IT landscape are to be transferred to monitoring as a device. The other configuration parameters always refer to one of the assets found by this type filter.

In addition to selecting a type, you can restrict the assets using additional conditions. For example, you could create a filter to only include devices for EC2 instances that have a public IP address or whose "First Seen" value is within the last hour. This would imply that they have been newly added.

### Name Attribute

The "Name Attribute" configuration parameter is always the first one evaluated in the context of one of the assets found (defined by your specifications in the type configuration parameter). Previous configuration parameters had static values that could be specified directly, whereas final values, such as the name of the device to be created, are calculated based on your specifications.

Thus, enter the name of the attribute whose value you want to use as the name of the respective device here.

**Example**
You created a configuration parameter of the type "EC2 instances". All EC2 instances in Qbilon have a property called "Public IP Address". If you enter "Public IP Address" in the "Name Attribute" configuration parameter, Qbilon will create a new device for each found EC2 instance. The name of each new device will be the value of the respective EC2 instance's "Public IP Address" property, e.g., `123.456.789.123`.

### Host Attribute

Similar to the "Name Attribute" configuration parameter, the "Host Attribute" configuration parameter is always evaluated in the context of one of the found assets, as defined by the specifications in the "Type" configuration parameter.

If you enter a value for "Public IP Address" here, that value will be searched for among the found assets and entered as the host when devices are created.

### Sensor Creation Information

The other details are optional because the PRTG Sensor Creator can be used to create devices in a specific group only. To create only a device, simply leave the following fields empty.

However, if you decide to create sensors in addition to the newly created devices, you can do so in two ways. One option is to use the "Auto-Discovery" feature in PRTG with one of their standard device templates. The other option is to explicitly specify the sensor(s) to be created.

#### Auto-Discovery

If you decide to create the sensor using one of the standard PRTG device templates, you can check the box here and then select one of the many standard device templates to be used for sensor creation in PRTG:

![PRTG Sensor Creator: Auto-Discovery](https://mintcdn.com/qbilon-docs/Jmla3tEw4FRYjkNT/.gitbook/assets/a503069f-e608-4f59-99e8-038735af6a2c-image.png?fit=max\&auto=format\&n=Jmla3tEw4FRYjkNT\&q=85\&s=1b4e60b58de6a2213a84a0cc50535934)

> [!NOTE]
>
> If you have activated "Auto-Discovery", it is no longer possible to explicitly create sensors using Qbilon.

#### Select Sensor

Alternatively, you can select one or more sensors from the list of supported sensors that Qbilon should automatically add to the created device:

![PRTG Sensor Creator: Select Sensor](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/be5bece8-7e0b-4b44-8523-4bc6a92022c2-image.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=227b0ec0eaa93e89edd45aac5ab8117b)

Each sensor comes with several pre-filled configuration parameters that normally do not require further editing. These parameters are specifically geared towards EC2 instances or Azure Virtual Machines, whose values are already known in Qbilon.

**Azure VM Sensor**
Based on Virtual Machines (VMs) that are loaded from Azure, we can create sensors for them in PRTG. For that we need some information:

* "VM ID": Unique identifier for the VM (by default: `id` property from Azure Virtual Machine)
* "VM Name": Name of the VM (by default `Name` property from Azure Virtual Machine)
* "VM Operating System": OS running on the VM (by default `OS-Type` property from Azure Virtual Machine)
* "VM Resource Group Name": Name of the resource group for the VM (by default `Resource Group Name` property from Azure Virtual Machine)
* "VM Region": Region name of the VM (by default `Region` property from Azure Virtual Machine)

> [!NOTE]
>
> **All of the property values above are required.** Hence, if any of the assets to create does not contain any of the properties above, it is skipped.

> [!WARNING]
>
> Please note that when using Kubernetes, Azure contains "Virtual Machine Scale Sets" that manage virtual machines of their own. PRTG only considers virtual machines that are not managed by Kubernetes. To determine this, we read the `Type` property, which contains a reference to "Scale Sets". We only consider virtual machines without a reference to "Scale Sets".

**AWS EC2 Sensor**
Based on EC2 instances that are loaded from AWS, we can create sensors for them in PRTG. For that we need some information:

* "EC2 ID": Unique identifier for the EC2 instance (by default `id` property from AWS EC2)
* "EC2 Name": Name for the EC2 instance (by default `aws-tag-Name` property from AWS EC2)
* "EC2 Availability Zone": Name of the Availability Zone for the EC2 instance (by default `Availability Zone` property from AWS EC2)
* "EC2 Region": Name of the Region for the EC2 instance (by default `Region` property from AWS EC2)

> [!NOTE]
>
> **All of the property values above are required.** Hence, if any of the assets to create does not contain any of the properties above, it is skipped.

**Currently supported sensor types:**

* AWS EC2 Sensor
* Azure VM Sensor
* Ping Sensor
* Ping Sensor (V2)
* SNMP System Uptime
* SNMP Uptime v2
* SNMP CPU Load


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.