Check that vFunction is connected

In the application server log, ensure the vFunction Agent is connected by searching for in the monolith application logs:

vFunction native agent version {version_number} successfully loaded 
Jolokia: Agent started with URL http://ip_address:port/jolokia/ 

The monolith is running more than once

Make sure the monolith process appears only one-time

ps -ef | grep java

If needed, add the classes to include under instrconf_additions

Sometimes the system excludes classes from the analysis, for example, classes that belong to framework packages such as com.oracle. In these cases, the user can specify what to include and exclude from the analysis by editing the file: /etc/sysconfig/vfunction/installation/instances/<instance_name>/installation.yaml

For example, suppose I want to include classes from com.oracle.sample123 and exclude classes from org.mit.

The section will be:

instrconf_additions:
  inclusions:
    -	com.oracle.sample123.
  exclusions:
    -	org.mit.

To apply the changes run: /opt/vfunction/controller-installation/upgrade.sh

Similar inclusions should be configured in the native_conf.json file, which is used in the arguments of your application.