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

# PRTG Network Monitor

> Connect PRTG so agents can investigate sensors and alarms, read history, and act on monitoring objects

Connect PRTG Network Monitor with an API key to investigate sensors, alarms, devices, and history. With permission, CloudThinker can also change a monitoring object through [Approvals](https://docs.cloudthinker.io/guide/approvals/overview.md).

## Prerequisites

* A PRTG web server reachable from CloudThinker over HTTPS with a trusted certificate. See [Reaching private services](https://docs.cloudthinker.io/guide/connections/overview.md#reaching-private-services).
* A PRTG account that can read the monitoring objects you want to investigate.
* Permission to add connections in your CloudThinker workspace.

## Setup

**1. Create an API key**

In PRTG, open **Setup → Account Settings → API Keys**. Hover over the add icon and select **Add API Key**. Name the key and select **Read access** for investigations. Copy the key before clicking **OK**: PRTG will not show it again. See [Paessler's API key guide](https://www.paessler.com/manuals/prtg/api_keys).

**2. Add the connection**

In CloudThinker, open **More → Workspace settings → Connections** and select **PRTG Network Monitor**. Enter the HTTPS server root in **Server URL**, without a path or query. Paste the key into **API key** and click **Connect**.

**Success state:** the connection shows **Connected**. CloudThinker checks the PRTG server status.

## Connection details

| Field | Description |
| - | - |
| **Server URL** | The HTTPS address of your PRTG web server, without a path or query |
| **API key** | The key created in PRTG |

## Required permissions

Start with **Read access** on the API key and a user that can read the monitoring objects you want to investigate. PRTG limits what the user can see based on its access rights. See [Paessler's access rights guide](https://www.paessler.com/manuals/prtg/access_rights_management).

To allow changes, the key and its user must have the necessary permissions in PRTG, and the connection's write tool must be enabled. Review your [Approval mode](https://docs.cloudthinker.io/guide/approvals/approval-mode.md) before allowing changes.

## Agent capabilities

| Capability | What CloudThinker can do |
| - | - |
| **Discovery** | Summarize the server, sensors, alarms, and devices |
| **Alarm investigation** | Read down, acknowledged, and warning sensors and recent logs |
| **Sensor history** | Read a sensor's recent history and channel values |
| **Changes** | Pause, resume, acknowledge, scan, rename, or change priority for a supported object |

Pausing a device or group also pauses its sensors. Deleting or cloning objects and changing other settings are not available through this connection.

### Verify the connection

```text theme={null}
Summarize my PRTG sensor and device counts and show the current down and warning sensors
```

Compare the answer with PRTG. A successful connection check confirms server status, so verify that the expected monitoring objects are visible too.

### Example prompts

```text theme={null}
Which PRTG sensors are down, and what are their latest messages?
Show the last 24 hours of history for this sensor
```

## Troubleshooting

> **PRTG rejected the API key**
>
> Check that the key is active and copied correctly. If necessary, create a new key in PRTG and update the connection.

> **PRTG answered with a redirect**
>
> Use the exact HTTPS address of the PRTG web server, without a path. Check the API key as well.

> **Could not reach the PRTG server**
>
> Check the server address, network access, and certificate. CloudThinker requires a trusted certificate.

> **The API key's user cannot read the server status**
>
> Check the PRTG user's permissions and access to the server and monitoring objects.

## Security

* **Least privilege** — grant only the permissions the agents need for your use case; start read-only and widen later.
* **Read-only by default** — use read-only credentials unless you want agents to make changes through this connection.
* **Rotate credentials** — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
* **Revoke on offboarding** — remove the credential at the provider when you delete a connection or a teammate leaves.

- **Start with read access**: use a key and account scoped to the objects CloudThinker needs.
- **Review changes**: use your Approval settings and PRTG permissions to control actions.

## Related

> **[Approval modes](https://docs.cloudthinker.io/guide/approvals/approval-mode.md)**
>
> Choose how changes are approved.

> **[Alert sources](https://docs.cloudthinker.io/guide/incident/connect-alert-sources.md)**
>
> Send monitoring alerts to Resolve.


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