Parameters and General Settings

Owned by Martin Moghadam
Last updated: Oct 05, 2021 by Oliver Villumsen

You can only do this if you're a PerformanceGuard administrator.

If you select Administration > Setup > Parameters, you can customize and configure the PerformanceGuard services: Display (that is web interface-related settings), Frontend, Notification (that is Backendserver-related settings), Common (that is parameters shared between services), Status, Date and Time, and System Properties.

Read more about the effect of parameters in the Parameter description column on each of the tabs. If you're in doubt about what will happen if you change a value, contact your PerformanceGuard consultant.

After you have changed and saved the values of a service, you must restart the service in question for your changes to take effect.

If you think about changing date and time format parameters (you can do that on the Common and Display tabs), read Date and Time first.

If You Want DNS to Resolve IP Addresses

On the Display tab, there's a parameter called DNS server ip-address. You use that parameter to specify one or more DNS servers if you want DNS to help PerformanceGuard resolve server IP addresses to hostnames.

If you want to specify multiple DNS servers, you must separate the IP addresses with commas, but it's important that you don't use spaces.

Example: 10.10.10.10,20.20.20.20 will work, because there's no space between the two IP addresses. 10.10.10.10, 20.20.20.20 will not work because of the space between the two IP addresses.

Some Parameters Overlap with Agent Configuration Group Parameters

On the Status tab there are some parameters that you can also specify as part of the agent configuration group settings. If the value of such a parameter isn't the same on the Status tab and in the agent group configuration settings, PerformanceGuard will always use the highest value.

These are the parameters that overlap:

Parameter Name in Agent Configuration Group Settings

Parameter Name on Status Tab

Default Value

For how long, in minutes, should agent process lists be kept

KEEP_PERIOD_PROCESS_DATA

10080 minutes (that is one week)

For how long, in minutes, should agent resource data be kept

KEEP_PERIOD_DETAIL_DATA

10080 minutes (that is one week)

For how long, in minutes, should agent traffic data be kept

KEEP_PERIOD_TRAFFIC_DETAIL_DATA

10080 minutes (that is one week)

For how long, in minutes, should agent utilization index data be kept

Not available on Status tab, but configurable in frontend server database

10080 minutes (that is one week) for default agent configuration group
259200 minutes (that is 180 days) for default agent configuration group for servers

For how long, in minutes, should agent advanced tcp client counters be kept

Not available on Status tab, but configurable in frontend server database

10080 minutes (that is one week)

For how long, in minutes, should agent protocol transactions be kept

Not available on Status tab, but configurable in frontend server database

10080 minutes (that is one week)

For how long, in minutes, should agent advanced tcp server counters be kept

KEEP_PERIOD_ADVANCED_TCP_DETAIL_ SERVER_DATA

10080 minutes (that is one week)


See also Database Retention Periods.

Search this documentation

On this page

In this section