Agent Settings

The Agent Settings section provides you with the following information:

Java runtime discovery frequency: how frequently the fleet's management agents record Java usage to JMS.
Usage reporting frequency: how frequently agents check for work requests to execute.
Report JMS plugin metrics: Determines if agents report resource utilization (CPU, memory, disk, network) metrics for the JMS plugin deployed on a Managed Instance.
Report application invocation username: Controls whether agents capture the username associated with application usage in a Managed Instance.
Record Java library usage: Indicates if agents periodically scan managed instances to automatically discover vulnerabilities in Java libraries used by applications, without requiring the Scan for Java library action.
Capture IP addresses, hostnames, and FQDNs: Enables agents to capture the IP addresses, hostnames, and fully qualified domain names (FQDNs)
Agent polling interval: how frequently the fleet's management agents perform a scan of their hosts to report Java Runtime installations to JMS. (This might indicate disabled if Java Runtime Discovery isn't enabled.)
Work request validity: the time period for accepting the work request by the agents involved
List of file system paths the fleet's management agents include and exclude in their scan to discover Java Runtime installations on their hosts. (The paths are displayed separately for Linux and Windows hosts.)

To modify these settings, see Configure Agent Settings section.

Note

OCMA agents:

Report Java applications from a pod as soon as the pod starts in the Kubernetes cluster.
Scan the entire cluster every 3 hours to detect Java applications.
Update the application inventory every 24 hours to reflect the last reported time.

These behaviors are currently non-configurable.