HQ Server Configuration

HQ Email Configuration Properties

• Base URL
• From Email Address

These configuration properties control how alert notifications appear. The Base URL is the prefix used to generate links in alert notifications. This should be the URL you would use to access HQ. The From Email Address is the address in the "From:" header on alert notification emails.

Data Manager Configuration Properties

• Delete Detailed Data Older Than
• Run Database Maintenance Every
• Delete Response Time Data Older Than
• Delete Alerts Older Than
• Reindex Metric Data Tables Nightly

Changes Require Server Restart Any changes made in this section require the HQ Server to be restarted before they take effect.

HQ stores monitoring data using a tiered model to reduce the amount of data that is stored and still provide the necessary granularity to determine when monitoring data changes. By default HQ will keep detailed metric data as defined by the metric collection intervals for a period of 2 days. After 2 days the data will be compressed and archived into hourly averages with highs and lows. To modify this setting change this setting simply change Delete Detailed Data Older Than to your desired range. Note that HQ only supports keeping detailed data for a period up to 7 days.

In addition to the range at which to condense detailed data, HQ also allows the administrator to change how often this process occurs. By default this is set to every hour. To change this, modify the Run Database Maintenance Every setting.

Response Time data can take a significant amount of space to store, depending on how many resources this data is collected for. This page allows the HQ administrator to configure the amount of time Response Time data is kept. The default is 31 days.

HQ also removes old alerts as part of its internal maintenance. The HQ administrator can use this page to configure how long to keep alerts in the system before they are purged. This setting defaults to 31 days as well.

During normal HQ operation, the metric data tables in the HQ database hold a large volume of ever changing data. Rebuilding the indexes on these tables can help to keep HQ performing well. This page allows the HQ administrator to configure whether or not to rebuild these indexes nightly. If this option is turned on the indexes will be rebuilt around midnight every night.

Automatic Baseline Configuration Properties *

• Baseline Frequency
• Baseline Dataset
• Baseline Minimum Data Points

HQ's baselining feature allows for configuration of 3 main factors that contribute to the baseline calculation. The Baseline Frequency configuration parameter allows configuration of how often to calculate a baseline for each individual metric. The default value is every 3 days.

The Baseline Dataset parameter allows configuration of the range which to use while calculating the baseline. The default for this setting is 3 days.

The final parameter is Baseline Minimum Data Points which sets the minimum number of datapoints to use when calculating a baseline. By default this value is set to 40.

LDAP Configuration Properties *

By default Hyperic HQ uses its database for storing information about users and authenticating those users. HQ can be configured to use an external LDAP directory for authenticating users in addition to its own database.

This section allows the HQ administrator to configure connection to the LDAP server. If this option is turned on, required fields are:

• URL
• Search Base
• Login Property

The URL is the LDAP URL the HQ Server will use to access the LDAP directory. If the LDAP directory requires SSL connections, check the SSL checkbox.

The Search Base is also known as the suffix. This is required for an LDAP connection. If you are unsure of this setting, check with your LDAP administrator. The Login Property is very important. This is the LDAP property that HQ will use as the username. Examples of common login properties are "cn" and "uid".

The Username and Password are used if your LDAP directory does not allow anonymous searching. This is commonly the case in any sort of secure environment, so it is likely you will need to use these fields. The username specified here must be an LDAP user with sufficient privileges to view at least the sections of the directory containing the information for the users to be logging in to HQ.

The Search Filter configuration is a way to limit the users in LDAP to a subset of the entire directory.

After LDAP authentication has been successfully configured, users will be able to log into HQ with their LDAP password (using the value specified as the Login Property as their username). The first time an LDAP user logs in to HQ, they will be directed to answer a few questions before they can continue. The questions just consist of their first and last name, email address, phone number, etc. This is for display purposes and alert notification purposes.

LDAP Users Need Roles Too As with all new users in HQ, LDAP users are not assigned to any roles by default and therefore they will not be able to see any resources in HQ until they are added to a role. HQ administrators will need to add a new LDAP user to a role in HQ after the new user logs in for the first time.

SNMP Server Configuration Properties *

If you had enabled SNMP traps for alerting. Then you will see a configuration block appear here for your SNMP server. By selecting the SNMP Protocol Version, the configuration properties will change to reflect the settings required for that SNMP version. Populate the properties with settings appropriate for your environment.