How to reject Java Classes from being sent to the vFunction Server for Analysis

Overview of the Issue
Steps to Resolve the Issue

Overview of the Issue

If an organization finds that specific classes are not useful for the vFunction Analysis or if sending the Sampling Threads associated with this class are creating a significant amount of networking throttle, then these classes can be removed from the Analysis workflow. In this scenario, the Callstacks associated with this Class will not be uploaded from the vFunction Agent to the vFunction Server.

Steps to Resolve the Issue

Take the following steps to resolve this issue:

SSH to the Application Server running the vFunction Agent
Open the vFunction instance’s installation.yaml, such as

vi /etc/sysconfig/vfunction/installation/instances/default-java/installation.yaml

To the agent.override_properties, add an override property to reject the problematic Class, such as

controller:
  name: NAME
  host: SERVER_ADDRESS
  ...

server_application:
#  name:
   ...

agent:
  override_properties:
    - com.vfunction.runtime.beanfilter.classRejectNames=org.apache.organization.infrastructure.core.config.organizationProperties

Save the file changes
Run the vFunction Upgrade script, such as

sudo bash /opt/vfunction/controller-installation/upgrade.sh -i default-java

Restart the Application