PRTG Manual: System Administration—User Interface

PRTG Site Name

When using the web interface, the site name is shown in the title bar of your browser window. It is also used by default in notification emails. Please enter a string.

DNS Name

If your PRTG web interface is (additionally) reachable via a DNS name, enter it here. It is used, for example, by default in notification emails to generate links. Please enter a string.

The special characters " and \ are not allowed in the DNS Name.

This option is not available in PRTG hosted by Paessler.

Website Language

Choose the system language from the dropdown list. Default is English. Depending on your installation, you may be able to choose other languages here. This setting defines the language of the PRTG web interface, as well as of the PRTG Administration Tool.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

Graph Type

Select how graphs will be displayed throughout the web interface and in reports.

• Use area graphs (recommended): Display filled graphs.
• Use line graphs: Display graphs using single lines only.

We recommend that you use area charts, as they're better to read.
Graphs containing data from more than one cluster node will always be displayed with line graphs automatically.

Automatic Logout

Define if a user who is inactive for a certain period of time will be logged out from the PRTG interface automatically for security reasons. Choose between:

• Keep user logged in, even for a longer period of inactivity.
• Log out user automatically after a certain period of inactivity.

Automatic Logout after Minutes

This field is only visible if you select the logout option above. Specify in minutes after which period of inactivity a user will be logged out automatically. Please enter an integer value. PRTG will redirect to the login page once this time has expired.

If the value you enter here is greater than 1 minute, a logout countdown will appear 1 minute before you are logged out. If the value is 1 minute, you will see the logout countdown 30 seconds before you are logged out. Click into the browser to stop the countdown and stay logged in.

Logout Countdown

Google Analytics Tracking ID

You can track the usage of PRTG web pages with Google Analytics by entering your Google Universal Analytics Tracking ID into this field. You need a Google Analytics account for this feature. Create a tracking ID within the Google Analytics portal and provide it here. PRTG will then dynamically integrate it into the website.

Please enter a string or leave the field empty. The string will look like this: UA-xxxxxx-xx

For details, see the Knowledge Base: How can I integrate Google Analytics in PRTG?

This option is not available in PRTG hosted by Paessler.

Map Service Provider

Select if and how you want to integrate the Geo Maps feature into the web interface. If enabled, PRTG uses the first line of the location setting of an object to show it on a geographical map. Choose a map provider:

• Do not show maps (disables Geo Maps integration): Disable Geo Maps integration and do not show geographical maps in the web interface.
• Default (recommended): The recommended default option currently reroutes the map requests to Nokia Maps. See this blog article for details: Geo Maps Requires a Change of Map Service Provider
• HERE Maps: Use HERE Maps to show geographical maps.
• CloudMade (API key required): Use CloudMade to show geographical maps. Please sign up for an API key on their developer website to use this service.
• Google Static Maps (API key required): Use Google Static Maps to show geographical maps. Please sign up for a Google Maps API v3 key to use this service as of PRTG version 13!

For more information about the different map providers, see the Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?

Map Type

This setting is only visible for some map providers. Depending on the chosen provider, several options are shown. Each will show map tiles in a different appearance. Choose a map type from the list.

API Key (required)

This field is only visible if you selected a provider that requires an API key. Obtain your personal key and paste it here.

For more information on how to get a Google API key, see the Knowledge Base: How do I get a Google Maps API key for use in PRTG?

Performance Strategy

Select if you want to enable performance improvements for the web interface.

• All Features: Show all features and live data (recommended): Provide full functionality and show all menu items.
• More Speed: Limit features and delay display (experimental): Improve reaction time and speed of the web interface by delaying display of monitoring data and hiding some features.

For more information on how to speed up the web interface, see the Knowledge Base: How can I speed up PRTG—especially for large installations?

IP Address for Web Server

PRTG is running a web server in order to provide access via the web and Windows interface. Please specify the IP address this web server will run on. Later, you can log in to PRTG by simply pointing your browser to the specified IP address.

Choose between:

• Localhost, 127.0.0.1 (PRTG will not be accessible from other computers): Use 127.0.0.1 only. The PRTG web interface and the Enterprise Console will only be accessible from the computer PRTG is installed on. Either the selected port or at least one port in the range from 8080 to 8089 has to be available on 127.0.0.1.

If you run PRTG on localhost, please do not use the DNS name http://localhost to log in to the web server, as this may considerably slow down the PRTG web interface. Please use your local IP address or http://127.0.0.1 instead.

• All IPs available on this computer: Use all IP addresses available on this computer and enable access to the web server for all of these addresses. The TCP port selected below must be free on every available IP address.
• Specify IPs: Select specific IP addresses on which the PRTG web server will run. A list specific to your system is shown. Add a check mark in front of every IP address you want the PRTG web server to be available at. You can also select and deselect all addresses by clicking on the check box in the table header. Either the selected port or at least one port in the range from 8080 to 8089 has to be available on the specified IP address.

Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so PRTG can create reports. The report engine will try to connect to the core server on one of these ports.

If PRTG does not find a network card on startup, it will switch the IP setting to Localhost. This setting will remain even if a network card is available later on. If you disabled or removed the network card on the machine running the PRTG core server, please re-check this setting.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

TCP Port for Web Server

PRTG runs a web server in order to provide access via the web interface and the Enterprise Console. Please specify on which port this web server will run. Choose between:

• Secure HTTPS server (recommended, mandatory for internet access): We recommend this setting and you need it to access the PRTG server via the internet. Use a secure HTTPS connection that is encrypted via SSL on port 443.
  Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. For more information, see section Using Your Own SSL Certificate.
   
  If port 80 is free, PRTG will reserve it as well. If port 80 is not available, PRTG will try port 8080 as fallback. If this port is also not available, PRTG searches from port 8081 upwards for a free port. PRTG will send a ticket that shows you the currently used port number and will switch back to 80 as soon as it is available again. When users try to connect on port 80 via HTTP, they will then be redirected to port 443 via HTTPS. You can change this behavior by using a registry setting. If port 443 is not available, PRTG will try port 8443 as fallback. If this port is also not available, PRTG searches from port 8444 upwards for a free port. PRTG will send a ticket that shows you the currently used port number and will switch back to 443 as soon as it is available again.
• Insecure HTTP server (standard port 80, not recommended): Use a standard web server without SSL encryption on port 80. This setting is not recommended for WAN connections.
  If you use an insecure web server on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend that you use this option in a LAN only.
• Expert configuration: This setting allows you to specify a custom web server port and the security of the connection. This option is intended for systems with an existing web server on the standard port. Define port and encryption below.
  If PRTG always uses a fallback port after a server restart, check for other programs that use the same port as PRTG. For example, the Microsoft IIS web server also uses the port 80 (443 for SSL) by default and blocks it. Please disable such programs and services on startup.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Web Server Port

You will see this setting only if you select Expert configuration above. Enter the TCP port number you want the PRTG web server to run on. Please enter an integer value.

If you use a secure connection and port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will be redirected to the custom port via HTTPS. You can change this behavior by using a registry setting.

If the defined port for a secure connection is not available, PRTG will try port 8443 as fallback. If this port is also not available, PRTG searches from port 8444 upwards for a free port. PRTG sends a ticket that shows you the currently used port number and will switch back to the original port as soon as it is available again.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Web Server Security

You will see this setting only if you select Expert configuration above. Specify if you want to use an SSL encryption. Choose between:

• Use SSL encryption (HTTPS): Use a secure HTTPS connection that is encrypted via SSL on a custom port as defined above.
  Although the connection is secure, you will see an SSL Certificate Warning in your browser when you log in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. For more information, see Using Your Own SSL Certificate.
• Don't use encryption (not recommended): This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on a custom port as defined above.

If you use a web server without encryption on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend that you use this option in a LAN only.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Connection Security

Specify the security level that will be used for connections from and to the PRTG web server. Choose between:

• High security (TLS 1.1, TLS 1.2): The web server will only accept high security connections from clients like web browsers, apps, the Enterprise Console, or API clients. These clients must be able to support modern ciphers that support authentication and encryption of 256 bits or stronger and forward secrecy (key exchange based on ECDH(E) or DH(E)).
• Default security (TLS 1.0, TLS 1.1, TLS 1.2) (recommended): The web server will additionally accept TLS 1.0–secured connections from clients. These clients must be able to support modern ciphers that support authentication and encryption of 128 bits or stronger and forward secrecy.
• Weakened security (SSL V3, TLS 1.0, TLS 1.1, TLS 1.2): If you have clients that do not support the high or default security setting, you can choose this security level to connect (for example, older browsers, browsers running on Windows XP, some default browsers on Android systems). Weakened security supports SSL V3 connections and AES and 3DES encryption.
  We strongly recommend that you update your clients in this case.

If you have set a registry key in previous PRTG versions to override the SSL version and cipher of PRTG web server connections, the High security setting will override the registry key setting and only TLS 1.1 and TLS 1.2 will be allowed. If you select the Default security setting, the registry key will override the default security setting and the connection security that you have defined in the registry will apply.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Currently Active IP Address/Port Combination(s)

Shows all currently active combinations of IP addresses and ports on which the PRTG server listens for web requests. This setting is shown for your information only and cannot be changed here.

PRTG internally uses port 8085 for report generation.

This option is not available in PRTG hosted by Paessler.

PRTG shows several graphs in the objects' detail pages in the web interface. These are kept in RAM for fast display without causing extra CPU load or disk usage. The longer the time frames and the shorter the intervals are, the more memory will be used for this. You can adapt the details for all four graphs. This setting will also change the caption of the objects' tabs in the web interface and Enterprise Console.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

Live Graph

The live graph is available for sensors only. For the live graph, no fixed time span is given, but you can define how many values will be displayed. The actual time span covered by the live graph depends on the scanning interval set for the sensor you're viewing and is calculated automatically. By default, 120 Values is set, which results in a graph covering a time span of two hours, if a scanning interval of 60 seconds is set for the sensor. Other scanning intervals will result in graphs covering different time spans. Choose between:

• 60 Values: This corresponds to a live graph covering a time span of one hour if a 1 minute scanning interval is set. Uses least RAM. We recommend this setting for installations with 10,000 sensors or more.
• 120 Values: This corresponds to a live graph covering a time span of two hours if a 1 minute scanning interval is set.
• 240 Values: This corresponds to a live graph covering a time span of four hours if a 1 minute scanning interval is set.
• 480 Values: This corresponds to a live graph covering a time span of eight hours if a 1 minute scanning interval is set.
• 960 Values: This corresponds to a live graph covering a time span of 16 hours if a 1 minute scanning interval is set. Uses most RAM.

Graph 1

By default, this is the 2 days graph in the web interface. You can change it to more or less detail by choosing a time span and a monitoring interval average associated with it. Monitoring results will be averaged regardless of the actual scanning interval set for the sensors. Choose between:

• 1 day with 1 minute averages: Results in 1440 values.
• 1 day with 5 minutes averages: Results in 288 values.
• 1 day with 15 minutes averages: Results in 96 values. Uses least RAM. We recommend this setting for installations with 10,000 sensors or more.
• 2 days with 1 minute averages: Results in 2880 values. Uses most RAM.
• 2 days with 5 minutes averages: Results in 576 values.
• 2 days with 15 minutes averages: Results in 192 values.
• 4 days with 1 hour averages: Results in 96 values. Uses least RAM. We recommend this setting for installations with 10,000 sensors or more.

Graph 2

By default, this is the 30 days graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between:

• 10 days with 1 hour averages: Results in 240 values.
• 20 days with 1 hour averages: Results in 480 values.
• 30 days with 1 hour averages: Results in 720 values.
• 30 days with 6 hour averages: Results in 120 values. Uses least RAM. We recommend this setting for installations with 10,000 sensors or more.
• 40 days with 1 hour averages: Results in 960 values.
• 40 days with 6 hour averages: Results in 160 values.
• 60 days with 1 hour averages: Results in 1440 values. Uses most RAM.
• 60 days with 6 hour averages: Results in 240 values.
   

Graph 3

By default, this is the 365 days graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between:

• 100 days with 1 day averages: Results in 100 values. Uses least RAM. We recommend this setting for installations with 10,000 sensors or more.
• 200 days with 1 day averages: Results in 200 values.
• 365 days with 1 day averages: Results in 365 values.
• 400 days with 1 day averages: Results in 400 values.
• 750 days with 1 day averages: Results in 750 values. Uses most RAM.