PRTG Manual: Device Settings

On a device's details page, click on the Settings tab to change settings.

Add Device

The Add Device dialog appears when adding a new device to a group. It only shows the setting fields that are imperative for creating the device. Therefore, you will not see all setting fields in this dialog. For example, the Device Status option is not available in this step.

You can change all settings in the device's Settings tab later.

Device Settings

The following settings are available in the Settings tab of every device. As you may not need all of these for every device, just regard those settings you really need, ignoring the others.

We recommend defining as many settings as possible in the Root group, so you can inherit them to all other objects further down in the tree hierarchy.

For device settings, there is also multi-edit available. This enables you to change properties of many devices at a time. For more details, please see Multi-Edit Lists section.

Note: This documentation refers to the PRTG System Administrator user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.

Basic Device Settings

Device Name

Enter a meaningful name to identify the device. The name will be shown by default in the device tree and in all alarms.

Status

Choose if monitoring for this device is started or paused.

  • Started: Monitor this device.
  • Paused: Pause monitoring for this device. All sensors on it will be paused until this setting is changed again.

IP Version

Define which IP protocol PRTG will use to connect to this device. The setting is valid for all sensors created on this device. Choose between:

  • Connect using IPv4: Use IP version 4 for all requests to this device.
  • Connect using IPv6: Use IP version 6 for all requests to this device.

IP Address/DNS Name

Enter the IP address (either v4 or v6, depending on your selection above) or DNS name for the device. Most sensors created on this device will inherit this setting and they will try to connect to this address for monitoring. (However, some sensor types still have their own setting for IP address/DNS name.)

Tags

Enter one or more tags, separated by space or comma. You can use tags to group sensors and use tag-filtered views later on. Tags are not case sensitive. We recommend using the default value. You can add additional tags to it, if you like.

Priority

Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).

Additional Device Information

Device Icon

Choose a device icon from the list. It will be shown in the device tree. For information on how to add your custom icons, please see the link in the More section below.

Service URL

Specify a URL you would like to open directly when choosing Device Tools | Go To Service URL from the device's context menu. For example, you can configure this option to call the address http://www.example.com/service.html. Enter a valid URL or leave the field empty.

Device Type

Sensor Management

Select which type of auto-discovery you would like to perform for this device. Choose between:

  • Manual (no auto-discovery): Do not auto-discover any sensors, but only add sensors manually.
  • Automatic device identification (standard, recommended): Use a small set of auto-discovery templates. This will scan your LAN and usually create a view standard sensors on your device.
  • Automatic device identification (detailed, may create many sensors: Use an extended set of auto-discovery templates. This will scan your LAN and usually create many sensors on your device.
  • Automatic sensor creation using specific device templates: Use specific auto-discovery templates only. Please select templates below. This will scan your LAN and add sensors defined in the template.

Discovery Schedule

This option is only visible if one of the auto-discovery options is selected above. Define when the auto-discovery will be run. Choose between:

  • Once: Perform auto-discovery only once. For existing devices, this will initiate a one-time sensor update for the current device.
  • Hourly: Perform auto-discovery for new sensors every hour.
  • Daily: Perform auto-discovery for new sensors every day.
  • Weekly: Perform auto-discovery for new sensors every week.

Device Template(s)

This option is only visible if using specific device templates (last option) is enabled above. Please choose one or more templates by adding a check mark in front of the respective template name. These will be used for auto-discovery on the current device. Choose from:

  • Cisco Device (Generic)
  • DNS Server
  • FTP Server
  • Generic Device (PING only)
  • Generic Device (SNMP-enabled)
  • Generic Device (SNMP-enabled, Detailed)
  • HTTP Web Server
  • Hyper V Host Server
  • Linux/UNIX Device (SNMP or SSH enabled)
  • Mail Server (Generic)
  • Mail Server (MS Exchange)
  • NTP Server
  • Printer (HP)
  • RDP Server
  • Server (Compaq/HP agents)
  • Switch (Cisco Catalyst)
  • Switch (Cisco IOS Based)
  • Switch (HP Procurve)
  • UNIX/Linux Device
  • UPS (APC)
  • Virtuozzo Server
  • VMware ESX Server
  • Windows (Detailed via WMI)
  • Windows (via WMI)
  • Windows IIS (via SNMP)
  • XEN Server

Inherited Settings

By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below.

Location

Location (for geo maps)

When using geo maps using Google's API please enter a location in the first line. Objects will then be displayed on a geographical map with a flag, showing the current status using a color code similar to the sensor status icons (green - yellow - orange - red). You can enter a full postal address, city and country only, or latitude and longitude. A minus sign (-) in the first line will hide an object from geo maps. In this case you can enter location information in line two and following.

Credentials for Windows Systems

Domain or Computer Name

Define the authority for Windows access. This is used for Windows Management Instrumentation (WMI) and other Windows sensors. If you want to use a Windows local user account on the target device, please enter the computer name here. If you want to use a Windows domain user account (recommended), please enter the (Active Directory) domain name here. If not explicitly defined, PRTG will automatically add a prefix in order to use the NT LAN Manager (NTLM) protocol. Please do not leave this field empty.

Username

Enter the username for Windows access. Usually, you will use credentials with administrator privileges.

Password

Enter the password for Windows access. Usually, you will use credentials with administrator privileges.

Credentials for Linux/Solaris/Mac OS X (SSH/WBEM) Systems

Username

Enter a login name for the access via SSH and WBEM. Usually, you will use credentials with administrator privileges.

Login

Define which authentication method will be used for login. Choose between:

  • Login via Password: Provide a password for login. Enter below.
  • Login via Private Key: Provide a private key for authentication. Note: PRTG can only handle keys in OpenSSH format which are not encrypted. You cannot use password protected keys here. In the text field, please paste the entire private key, including the "BEGIN" and "END" lines. Please make sure the according public key is provided on the target machine. For details, please see Monitoring via SSH.

Password

This field is only visible if password login is selected above. Enter a password for the Linux access via SSH and WBEM. Usually, you will use credentials with administrator privileges.

Private Key

This field is only visible if private key login is selected above. Paste a private key into the field (OpenSSH format, unencrypted). Usually, you will use credentials with administrator privileges. Note: If you do not insert a private key for the first time, but change the private key, you need to restart your PRTG core server service in order for the private key change to take effect! For details, please see Monitoring via SSH.

For WBEM Use Protocol

Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between:

  • HTTP: Use an unencrypted connection for WBEM.
  • HTTPS: Use an SSL-encrypted connection for WBEM.

For WBEM Use Port

Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between:

  • Set automatically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above.
  • Set manually: Use a custom port. Define below.

WBEM Port

This setting is only visible if manual port selection is enabled above. Enter the WBEM port number.

SSH Port

Please define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors, unless you define a different port number in the sensor settings.

Credentials for VMware/XenServer

User

Enter a login name for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.

Password

Enter a password for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.

Protocol

Define the protocol used for the connection to VMware and XenServer. Choose between:

  • HTTPS (recommended): Use an SSL-encrypted connection to VMware and XenServers.
  • HTTP: Use an unencrypted connection to VMware and XenServers.

Credentials for SNMP Devices

SNMP Version

Select the SNMP version that will be used for device connection. Choose between:

  • v1: Use the simple standard v1 protocol for SNMP connections. This protocol only offers clear-text data transmission, but it is usually supported by all devices.
  • v2c: Use the more advanced v2c protocol for SNMP connections. Data is still transferred as clear-text, but it supports 64-bit counters.
  • v3: Use the latest v3 protocol for SNMP connections. It provides secure authentication and data encryption.

Note for SNMP v3: Due to internal limitations you can only monitor a limited number of sensors per second using SNMP v3. The limit is somewhere between 1 and 50 sensors per second (depending on the SNMP latency of your network). This means that using an interval of 60 seconds you are limited to between 60 and 3000 SNMP v3 sensors for each probe. If you experience an increased "Interval Delay" or "Open Requests" reading of the probe health sensor you need to distribute the load over multiple probes. SNMP v1 and v2 do not have this limitation.

Community String

This setting is only visible if SNMP version v1 or v2c are enabled above. Enter the community string of your devices. This is a kind of "clear-text password" used for simple authentication. We recommend using the default value.

Authentication Type

This setting is only visible if SNMP version v3 is enabled above. Choose between:

  • MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
  • SHA: Use Secure Hash Algorithm (SHA) for authentication.

Your device must be set to the same value.

User

This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. Your device must be set to the same value.

Password

This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. Your device must be set to the same value.

Data Encryption Key (DES)

This setting is only visible if SNMP version v3 is enabled above. Enter a Data Encryption Standard (DES) key here. If you provide a key in this field, SNMP data packets will be enrypted using the DES encryption algorithm, providing increased security. Your device must be set to the same value. Note: If the key entered in this field does not match the key configured in the target SNMP device you will not get an error message! Please enter a string or leave the field empty.

SNMP Port

Enter the port used for SNMP communication. We recommend using the default value.

SNMP Timeout (sec.)

Enter a timeout in seconds for the request. If the reply takes longer than this value the request is aborted and an error message is triggered.

Windows Compatibility Options

When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting.

Primary Method

Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between:

  • Performance Counters and fallback to WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality.
  • Performance Counters only: Query data via performance counters only. If this is not possible, a sensor will return no data.
  • WMI only: Query data via WMI only. If this is not possible, a sensor will return no data.

Timeout Method

Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between:

  • Use 1.5x scanning interval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings).
  • Set manually: Enter a timeout value manually.

We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value.

Timeout Value (Sec.)

This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.

SNMP Compatibility Options

When experiencing problems while monitoring via Simple Network Management Protocol (SNMP) sensors, you can set some compatibility options for trouble shooting.

SNMP Delay (ms)

Add a time in milliseconds that will be waited between two SNMP requests. This can help increase device compatibility. Please enter an integer value. We recommend using the default value. If you experience SNMP connection failures, please increase it.

Failed Requests

Define if an SNMP sensor will try again after a request fails.

  • Retry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures.
  • Do not retry: Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be put to error state earlier.

Overflow Values

Define how PRTG will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks.

  • Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data.
  • Handle overflow values as valid results: Regard all overflow values as regular data and include them in the monitoring data.

We recommend using the default value. If you experience problems, change this option.

Zero Values

Define how PRTG will handle zero values. Some devices send incorrect zero values. This can cause false peaks.

  • Ignore zero values for delta sensors (recommended): Ignore zero values and do not include them in the monitoring data.
  • Handle zero values as valid results for delta sensors: Regard all zero values as regular data and include them in the monitoring data.

We recommend using the default value. If you experience problems, change this option.

32-bit/64-bit Counters

Define which kind of traffic counters PRTG will search for on a device.

  • Use 64-bit counters if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices.
  • Use 32-bit counters only: The interface scan will always use 32-bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices.

We recommend using the default value. If you experience problems, change this option.

Request Mode

Define which kind of request method PRTG uses for SNMP sensors.

  • Use multi get (recommended): Bundle multiple SNMP requests into one request.
  • Use single get: Use one request for each SNMP value. This can increase compatibility with older devices.

We recommend using the default value. If you experience problems, change this option.

Port Name Template

Define how the name of SNMP sensors created on a device will be put together. Enter a template using several variables. When adding new sensors, PRTG scans the interface for available counters at certain OIDs. At each OID usually several fields are available with interface descriptions. They are different for every device/OID. PRTG will use the information in these fields to name the sensors. If a field is empty or not available, an empty string is added to the name. As default, ([port]) [ifalias] is set as port name template, which will create a name such as (001) Ethernet1, for example. You can use any field names available at a certain OID of your device, among which are:

  • [port]
  • [ifalias]
  • [ifname]
  • [ifindex]
  • [ifdescr]

Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names.

Port Name Update

Define how PRTG will react if you change port names in your physical device (e.g. a switch or router). Choose between:

  • Keep port names (use this if you edit the names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually.
  • Automatic sensor name update if name changes in device: If PRTG detects changes of port names in your physical device it will try to automatically adjust sensor names accordingly. For detailed information please see More section below.

Port Identification

Define which field will be used for SNMP interface identification. Choose between:

  • Use ifAlias (recommended): For most devices ifAlias is the best field to get unique interface names.
  • Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field.

Start Port

For SNMP Traffic sensors, define at which port number PRTG will start to create sensors. Use 0 for automatic. We recommend using the default value.

End Port

For SNMP Traffic sensors, define at which port number PRTG will stop to create sensors. Use 0 for automatic. We recommend using the default value.

Proxy Settings for HTTP Sensors

HTTP Proxy Settings

The proxy settings determine how a sensor connects to a given URL. You can enter data for a proxy server that will be used when connecting via HTTP or HTTPS. Note: This setting is valid for the monitoring only and determines the behavior of sensors. In order to change proxy settings for the core server, please see System Administration—System and Website.

Name

Enter the IP address or DNS name of the proxy server to use. If you leave this field empty, no proxy will be used.

Port

Enter the port number of the proxy. Often, port 8080 is used. Please enter an integer value.

User

If the proxy requires authentication, enter the username for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.

Password

If the proxy requires authentication, enter the password for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.

Scanning Interval

Scanning Interval

The scanning interval determines the time the sensor waits between two scans. Select a scanning interval (seconds, minutes, or hours) from the list. You can change the available intervals in the system administration.

Cluster Usage

Scanning Distribution

This box is only visible if you're running a PRTG cluster. Sometimes you want to exclude a certain node from monitoring the sensors running on this probe, group, or device, for example, if a device is not reachable from every node configured in your cluster. In the list of cluster nodes, please select the nodes that will not be included in sensor scans. By default, this setting is inherited to all objects underneath.

Schedules, Dependencies, and Maintenance Window

Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings.

Schedule

Select a schedule from the list. Schedules can be used to pause monitoring for a certain time span (days, hours) throughout the week. You can create new schedules and edit existing ones in the account settings. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active.

Maintenance Window

Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between:

  • Not set (monitor continuously): No maintenance window will be set.
  • Set up a one-time maintenance window: Pause monitoring within a maintenance window.

Maintenance Begins At

This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window.

Maintenance Ends At

This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window.

Dependency Type

Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between:

  • Use parent: Pause the current object if its parent object is in a Down status, or if it is paused by another dependency.
  • Select object: Pause the current object if its parent object is in a Down status, or if it is paused by another dependency. Additionally, pause the current object if a specific other object in the device tree is in a Down status, or if it is paused by another dependency. Select below.

Note: Testing your dependencies is easy! Simply choose Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused.

Dependency

This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector to choose an object on which the current object will be dependent on.

Delay (Seconds)

Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds.

Access Rights

User Group Access

Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights:

  • Inherited: Use the settings of the parent object.
  • None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible.
  • Read: Users in this group can see the object and review its monitoring results.
  • Write: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings.
  • Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.

You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option.

Channel Unit Configuration

Channel Unit Types

For each type of sensor channel, define the unit in which data is displayed. If defined on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available):

  • Bandwidth
  • Memory
  • Disk
  • File
  • Custom

Note: Custom channel types can be set on sensor level only.

Click on the Save button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!

Notifications

The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to you needs. In an object's detail page, click on the Notifications tab to change sensor notification triggers. The defined triggers will be inherited down to sensor level. For detailed information, please see Sensor Notifications Settings section.

Others

For more general information about settings, please see Object Settings section.

More

Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time Index?

Knowledge Base: How can I add my own device icons for use in the PRTG web interface?

Knowledge Base: How can I change the defaults for names automatically generated for new SNMP sensors?

Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when the device changes them

 

Ajax Web Interface—Device and Sensor Setup—Topics

 

Other Ajax Web Interface Sections

 

Related Topics

Continue

Keywords: Configure,Configure Device

Hilfe
Benötigen Sie weitere Hilfe?

Hier geht's zum Hilfe-Center.

Update verfügbar Klicken Sie hier, um das neueste Update zu installieren
  FEEDBACK Klicken Sie hier, um Ihr Feedback an Paessler zu schicken