How It Works
Like the Virtualizor integration, SolusVM v2 uses a pull model. Flowtriq polls the SolusVM v2 API every 5 minutes to discover servers, their hostnames, and their primary IPs. There is nothing to install on your SolusVM server. You add your API credentials in the Flowtriq dashboard and the sync starts.
New servers get a monitoring node. Deleted servers get their node deactivated. The integration keeps both systems in sync without you touching either dashboard after initial setup.
Prerequisites
- SolusVM v2 (the v2 REST API is required)
- An API token generated in SolusVM v2 settings
- A Flowtriq account with at least one workspace
Flowtriq needs network access to your SolusVM v2 API endpoint. If your panel is behind a firewall, allow connections from flowtriq.com.
Setup
In your Flowtriq dashboard, go to Integrations > Hosting Panels > Add and select SolusVM.
Fill in the connection details:
- Panel URL: Your SolusVM v2 panel URL (e.g.,
https://solus.example.com) - API Token: The token you generated in SolusVM v2
- Workspace: Which Flowtriq workspace to create nodes in
Click Save & Test. Flowtriq connects to the SolusVM API and confirms it can list servers.
Creating an API Token in SolusVM v2
Log into your SolusVM v2 admin panel. Go to Settings > API Tokens and click Create Token. Give it a descriptive name like "Flowtriq Integration" and copy the generated token.
The token needs read access to list servers and their IPs. Flowtriq never creates, modifies, or deletes servers through the SolusVM API. It only reads.
What Gets Synced
Each sync cycle pulls the following from SolusVM v2 and maps it to a Flowtriq node:
- Server ID: Used as the external reference to link the Flowtriq node back to the SolusVM server
- Hostname: Becomes the node name in Flowtriq
- Primary IP: The IP address that Flowtriq monitors for DDoS traffic
- Status: Running, stopped, or suspended
Only servers with a "running" status get active monitoring. Stopped or suspended servers have their nodes paused until they come back online.
Auto-Provisioning Behavior
The sync runs every 5 minutes. State changes are handled like this:
- New server created: Flowtriq creates a node with the server's hostname and primary IP. A deploy token is generated for ftagent installation.
- Server deleted: The Flowtriq node is deactivated. Incident history is preserved but the node stops counting toward your limit.
- Server suspended: Monitoring pauses. No alerts fire.
- Server unsuspended: Monitoring resumes.
After provisioning, install ftagent on the server to start reporting traffic data:
curl -sSL https://flowtriq.com/install.sh | sudo bash
Dashboard View
Under Integrations > Hosting Panels in the Flowtriq dashboard, each connected SolusVM panel shows:
- Panel name and URL
- Server count: How many servers were discovered
- Last sync: Timestamp of the last successful sync
- Status: Connected, error, or syncing
Click into a panel to see every synced server with its node status, primary IP, and last check-in time. You can also trigger a manual sync from this page if you do not want to wait for the next cycle.
Note About SolusVM v1
This integration supports SolusVM v2 only. SolusVM v1 uses a different API that is not compatible. If you are still running v1, you will need to upgrade to v2 before connecting to Flowtriq.
SolusVM v2 introduced a modern REST API that makes this kind of integration straightforward. If you are evaluating whether to upgrade, the Flowtriq integration is one more reason to make the move.
Connect your SolusVM v2 panel. Go to Integrations in the Flowtriq dashboard and add your API token. Every server gets a monitoring node automatically. Start your free 14-day trial.