Prerequisites
- A PRTG web server reachable from CloudThinker over HTTPS with a trusted certificate. See 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.
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
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. 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 before allowing changes.Agent capabilities
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
Example prompts
Troubleshooting
PRTG rejected the API key
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
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
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
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
Choose how changes are approved.
Alert sources
Send monitoring alerts to Resolve.