Common Auto-Instrumentation Tasks

These properties are available to support common auto-instrumentation configuration tasks:

To set the namespaces that are in scope for auto-instrumentation:
- nsToInstrument
- nsToInstrumentRegex
(Optional) To filter and target the set of applications within a namespace that are in scope for auto-instrumentation:
- instrumentationMatchString
- labelMatch
To assign an application and tier name to an instrumented application:
- appNameStrategy
- tierNameStrategy
- tierName See Application Naming Strategies.
To instrument which containers are in a multi-container application:
- instrumentContainer
- containerMatchString The instrumentContainer default is to instrument the first container based on the ordering returned by the Kubernetes API.
If transaction analytics is required for Node.js applications, then specify the analytics host and port:
- analyticsHostanalyticsPort
  See Deploy Analytics Without the Analytics Agent. Configuration of transaction analytics is not required for .NET and Java applications. You can deploy the Analytics Agent using the sidecar model where you add an Analytics Agent container to each application pod, and then start/stop with the application container. If you use the sidecar approach, the App Server Agent uses the default host localhost and port 9090 and connects automatically. No additional configuration is required. See Install Agent Side Components in Kubernetes.

Documentation