Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


AppFormix Plugins


To install AppFormix certified plugins on the cluster, include the following variables in the group_vars/all file:

For example:

For a list of all AppFormix certified plugins that can be installed, look for the entries starting with plugin_info in the file roles/appformix_defaults/defaults/main.yml.

The OpenStack log parser plugins parse the API log files of each OpenStack service to collect metrics about API calls and response status codes. To install these plugins, add them to the variable appformix_openstack_log_plugins in group_vars/all, as shown above. Each plugin entry in this list requires a parameter called log_file_path to be specified. This parameter should be set to the complete path to the service's API log file on the OpenStack Controller node(s). Multiple comma-separated paths can be specified.

To identify the correct log file to be specified in log_file_path, look for entries like the following, containing a client IP address, REST call type, and response status code:

Default locations for these files are listed in the variable appformix_openstack_log_factory_plugins in roles/appformix_defaults/defaults/main.yml.

On containerized OpenStack environments, log files are generated inside the containers running the OpenStack services. However, they have to be available on the OpenStack controller host for the AppFormix plugins to be able to read them. The path specified in log_file_path should be the location of the file on the OpenStack Controller host.


In AppFormix 3.0, all OpenStack log parser plugins have to be specified in the variable appformix_openstack_log_plugins. When upgrading from an earlier version to 3.0, make sure to move all OpenStack log parser plugins defined in appformix_plugins' to appformix_openstack_log_plugins. Also, in AppFormix 3.0, all entries in this list have to be specified with a log_file_pathvalue, as described example above.