Set Up Configuration Tracking for a Resource

Topics marked with * relate to features available only in vFabric Hyperic.

Hyperic Configuration Tracking Functionality

For supported resource types, you can configure Hyperic to track changes made to configuration files (or other local files of interest) and log events for the associated resource. Configuration tracking is supported for most platform and server types; typically not for services.

Configuration tracking functionality for server types varies by resource type, plugins that have been updated to use the new event-based tracking added in Hyperic 4.6.5 track more information about file changes than those that still use the still-supported polling-based tracking.

The plugins that are updated to use event-based tracking are listed in Set Up 4.6.5 Configuration Tracking for a Server. Follow the instructions in that section for those server types. For other server types, and for platform and service types that support configuration tracking see Set Up Polling-Based Configuration Tracking.

Learn about Configuration Tracking

See Log and Configuration Event Tracking for information about:

  • What resource types support configuration tracking,

  • Prerequisites for configuration tracking,

  • The differences between Hyperic's event-based and polling-based configuration tracking,

  • Where to view configuration events in the Hyperic user interface, and

  • Support for using configuration change events in alerts.

Set Up 4.6.5 Configuration Tracking for a Server

Hyperic 4.6.5 has enhanced configuration tracking support for server types. The instructions in the section apply to server types whose plugin is updated to use event-based configuration tracking listed below.

  • Tomcat

  • Apache

  • WebSphere

  • WebLogic Server

  • JBoss

  • PostgreSQL

  • mySQL

  • Oracle

To enable and configure configuration tracking for a resource of one of the previous server types:

  1. Navigate to the server instance.

  2. Select Configure Server from the Tools menu.

    • The Configuration Properties page appears.

  3. In the Monitoring section of the page:

    1. Make sure that the Enable Config Tracking box, which enables and disables configuration tracking for the server, is checked.

      If you are satisfied with the default filter definition in the "Configuration Files" in, skip the following step, and click OK.

    2. In the "Configuration Files" box, specify the files you wish to monitor in this fashion:

      • where:

        • path — An absolute path, or a path relative to the managed resource's discovered install directory.

        • recurse — Indicates, with a value of "true" or "false", whether or not track the files inside directories below the target directory specified by path.

        • regex — A regular expression for filtering the directories or files to track for changes, in the directory (or directory tree for recursive tracking) specified by path.

    3. Click OK.

Example Configuration Files setting

For MySQL, the default value of the Configuration Files field, which specifies which files to track is:


When configuration tracking is enabled, this filter causes Hyperic to track my.cnf in the following directories:

  • MySqlHome/etc

  • MySqlHome/etc/mysql

  • MySqlHome

  • the home directory of the user under which MySQL runs

  • /usr/local/mysql/data

  • /usr/local/var

  • the Windows directory

  • c:/

and track my.ini in the following directories:

  • the Windows directory

  • c:/

  • MySqlHome

Set Up Polling-Based Configuration Tracking

For platforms and services that support configuration tracking, and server types that have the agent uses a cryptographic hash function to continuously compare a original version of the file with the current version to see if it has changed.

To enable and configure configuration tracking for a platform or service:

  1. Navigate to the resource instance.

  2. Select Configure ... from the Tools menu.

    • The Configuration Properties page appears.

  3. On the Edit Configuration Properties page:

    1. Click the Enable Config Tracking box to turn configuration tracking on and off for the resource.

    2. Enter the path, relative to the resource's installation directory, to each file you wish to track. Separate files with a comma.

    3. Click OK.

Configure Alerts Based on Configuration Events

  1. Enable and configure configuration tracking as described above.

  2. For the instructions in Define an Alert for a Resource, or Define an Alert for a Resource Type and choose the "Config Changed" condition type.