Impotant Notes! Please Read!
1. Copy & Pasteing Parameters from the Admin Guide to PRTG:
Please be aware that sometimes Copying and Pasteing the parameters from the Admin Guide to PRTG Parameters Line the Minus signs (-) become corrupted.
This usually results in Password Index User (or any other combination) missing error in PRTG.
To fix this just retype the minus (-) signs manually on the PRTG sensor parameters line and remove any excessive spaces in between:
Example:
-t:%host\VEEAMSQL2012 -u:%windowsuser -p:%windowspassword -d:%windowsdomain -i:jobperf
Correct Minus signs, no spaces between -xx:parameter, and brackets removed in the examples.
2. Bracked ([-db:any]) options in PRTG Parameters examples:
Bracked options stated in the parameters line meraly highlight that this is an optional parameter.
If you need/choose to use the parameter option please remove the brackets on the PRTG Parameters line.
Example:
In Admin Guide options an optional parameter is shown:
[-n:VEEAMSQL2012]
And change it to:
-n:VEEAMSQL2012
What does this %windowsuser mean on PRTG Parameters?
In order to convey the target device and it's credentials information for connection to the PRTGPlugins Sensor a place holder on the PRTG is used.
The information %windowsuser marks the place holder for the User Field value given in the "Credentials for Windows Systems" on PRTG Device Settings page and when PRTG is calling the plugin it replaces the placeholder with a real values provided in the mentioned Field.
PRTG Supports the following placeholders:
Placeholder | Description |
---|---|
%sensorid | The ID of the EXE/Script sensor |
%deviceid | The ID of the device the sensor is created on |
%groupid | The ID of the group the sensor is created in |
%probeid | The ID of the probe the sensor is created on |
%host | The IP address/DNS name entry of the device the sensor is created on |
%device | The name of the device the sensor is created on |
%group | The name of the group the sensor is created in |
%probe | The name of the probe the sensor is created on |
%name or %sensor | The name of the EXE/Script sensor |
%windowsdomain | The domain for Windows access (may be inherited from parent) |
%windowsuser | The user name for Windows access (may be inherited from parent) |
%windowspassword | The password for Windows access (may be inherited from parent) |
%linuxuser | The user name for Linux access (may be inherited from parent) |
%linuxpassword | The password for Linux access (may be inherited from parent) |
%snmpcommunity | The community string for SNMP v1 or v2 (may be inherited from parent) |
3. SQL Based Parameters in PRTG and Plugins:
In PRTGPlugins some options are based on SQL connectivity, like in Veeam-plugin all information is derived from the Veeam Database. Depending of the Setup used for Veeam Instaaltion there are some options you need to configure to establish a successful connection.
The SQL Instance?
The SQL connection instance can be delivered to the sensor by using two methods: By using the target parameter (-t:) or by using a separate parameter -n:instance_name.
Using target parameter to deliver the instalnce name by adding a back slash and the instance name:
-t:%host\instance_name
or by instance name parameter:
-t:%host ..... -n:instance_name
SQL Connectivity Options for Domain or SQL-Authentication
Like in normal SQL connectivity the plugins support both Domain and SQL based authentication. SQL based authentication is achieved simply by omitting the -d: Domain parameter Information for the sensor.
Example using Domain Based Authentication:
-t:%host\VEEAMSQL2012 -u:%windowsuser -p:%windowspassword -d:%windowsdomain
Example using SQL Based Authentication:
-t:%host\VEEAMSQL2012 -u:%windowsuser -p:%windowspassword
Naturally this requires the SQL based authentication is enabled on the SQL instance and corresponding user is configured properly.