> ## 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 Element Deleter

> Configure a PRTG Element Deleter and its access settings.

## Preface

With the "PRTG Element Deleter", you can create a task within an automation that deletes groups, devices, or sensors based on user-defined conditions. Depending on the information Qbilon has collected about the IT landscape, multiple groups, devices, or sensors can be deleted in a batch. Additionally, multiple deleters can be created to address different PRTG core servers, ensuring monitoring remains compliant with 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).

## Configuration

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

![PRTG Element Deleter: Configuration](https://mintcdn.com/qbilon-docs/aJQhbcvq7mtvhV0w/.gitbook/assets/1e4c9105-055d-4f11-b8ad-12ce3fe7be0c-screenshot-2026-10-06-175725.png?fit=max\&auto=format\&n=aJQhbcvq7mtvhV0w\&q=85\&s=2c003ce6f18f7d6ea0cdfb2460ef870a)

### Name and Identifier

The name to be displayed for this task when it is displayed within an automation. This name is freely selectable. Qbilon automatically calculates a valid identifier from the name, which does not have to be edited by the user. The name can e.g. express for which PRTG core the task was created, if you have several core servers in use.

### Host and API Token

This information is required so that the PRTG Element Deleter knows which PRTG Core Server to delete groups, devices, or sensors from. Groups, devices, or sensors located on a different PRTG Core Server will be automatically ignored when deleting if they are selected through the subsequent configuration of the "Type" parameter (see below).

![PRTG Element Deleter: Host and API Token](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/bc2e34e5-fc12-4c02-9b88-d7393e126cc9-screenshot-2026-10-06-180433.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=9e4f15b8d9f7e2534a9bf0eef5466048)

The API token must have been created by the user in PRTG and have "Full Access" rights to ensure that the PRTG Deleter has the necessary permissions to delete the defined assets in the PRTG instance.

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

![PRTG Element Deleter: Host and API Token](https://mintcdn.com/qbilon-docs/lr-P4KF_9wn8x9Vs/.gitbook/assets/d8ab8bf6-2a66-45c4-8d45-77fea1a7b6b3-image.png?fit=max\&auto=format\&n=lr-P4KF_9wn8x9Vs\&q=85\&s=377d6af700874b392d07dfe3a5155a9e)

> [!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](https://doc.qbilon.io/06-data-sources/internal-connectors/prtg.md) connector, 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.

### Type

Use the "Type" configuration parameter to select which PRTG assets to delete from monitoring. Although you can select asset types other than PRTG Groups, Devices, and Sensors, this will have no effect because the prerequisite is that the identified asset must have a PRTG Object ID.

Therefore, it is recommended that you only select assets of type PRTG Group, Device, or Sensor at this point. In addition to selecting a type, you can restrict assets using additional conditions. For example, you can specify that only devices with too many sensors in the "Down" state or that have not been "seen" for a certain time should be deleted.


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