The hostname of the Analytics Agent.

This parameter is required if you require the Node.js Agent or the .NET Core Agent to send the default transaction data to the Analytics Agent.

The listening port for Analytics Agent.

For example, if the Analytics Agent is listening on port 9090, then the value of this parameter is 9090.

This parameter is required with defaultAnalyticsHost if you require the Node.js Agent to send the default transaction data to the Analytics Agent.

This value is based on whether the Analytics Agent port is SSL enabled. If the port is not SSL enabled, specify the value as false

This parameter is required with defaultAnalyticsPort and defaultAnalyticsHost if you require the Node.js Agent to send the default transaction data to the Analytics Agent.

This is a regex value to choose the containers with the name that satisfies the value. This parameter requires you to use the select option within defaultInstrumentContainer or instrumentContainer.

When the select option is used with this parameter, Cluster Agent instruments the containers that match the regex value.

This parameter overrides the default value specified for defaultContainerMatchString.

This parameter provides an option to use the custom configuration of the instrumenting agents through ConfigMaps. This parameter requires that you create the required ConfigMaps in the Cluster Agent namespace. This parameter is dynamically configurable from the Cluster Agent YAML file. The changes that you make in the YAML file are updated to all the instrumented agents without restarting the application. Similarly, the changes that you make to the configuration in the ConfigMap is updated to all the instrumented agents without restarting the application.

• configMapName : Specify the name of the ConfigMap. This allows the agent to use the same custom ConfigMap to update all the instrumented agent namespace.
• subDir : (Required for Java Agent) Specify the relative path where the ConfigMaps are mounted. For example: /ver20.8.0.3686/conf , where 20.8.0.3686 is the version of the Java Agent. This directory may differ based on the Java Agent version. See Example 6.The absolute mount path for the ConfigMap is <agent home path>/subDir. This ConfigMap replaces any ConfigMap of the same name in the target application's namespace.

The custom secret name. This is the same name that is generated when you define the license rule.

The custom secret key. This is the same key that is generated when you define the license rule.

instrumentContainer

This parameter provides an option to choose the container that must be instrumented. You can specify any of these values:

• first : This is the default value. When you specify this value, Cluster Agent instruments the first container in the pod.
• all : When you specify this value, Cluster Agent instruments all the containers in the pod.
• select : When you specify this value, Cluster Agent instruments only those containers with the name that matches a regex specified in the defaultContainerMatchString parameter or the containerMatchString parameter.

The language of the application to be instrumented.

These languages are supported:

• dotnetcore
• java
• nodejs

Regular expression to match on deployment name on which the rule applies.

If you do not specify a value for this parameter, then the Cluster Agent uses the value specified in the defaultInstrumentMatchString,

labelMatch:

• label1: value1

• label1: value2

• label2: value2

If only label1: value2 matches, then instrumentation works as expected.

Application name used by the Java Agent to report to the Controller. This overrides defaultAppName

If no value is provided, then the configured defaultAppName is used.

The value of this label is the Splunk AppDynamics application name.

This parameter is specific to Java and Node.js applications.

You can add any custom system property if your application framework requires any specific configuration for instrumentation.This value takes precedence over the default value specified in the defaultCustomConfig parameter.

For Java applications: This value is appended to the env defaultEnv variable as configured with other Java Agent properties.

For Node.js applications: This value is appended to NODE_OPTIONS.

Tier name used by the Java Agent to report to the Controller.

If no tier name is provided, then the deployment name is used as the default if the tier name strategy is manual.

The value of this label is the AppDynamics tier name.

• abc-1
• abc-2

This parameter is applicable only for Java Agent.

Set this property to false if you do not require to reuse the node names.

This parameter is specific to Java applications.

Environment variable to which the App Agent system properties will be added. When specified, this overrides defaultEnv for the deployments matching this instrumentation rule.

If none are provided, it defaults to the defaultEnv (if configured), or to the default env JAVA_TOOL_OPTIONS (if not configured at the default cluster level).

image:  "docker.io/appdynamics/java-agent:latest"
agentMountPath: "/opt/appdynamics"
imagePullPolicy: "IfNotPresent"

dotnetcore:
image: "docker.io/appdynamics/dotnet-core-agent:latest"
agentMountPath: /opt/appdynamics
alpineInitContainerImage: alpine
imagePullPolicy: "IfNotPresent"

nodejs:
image: "docker.io/appdynamics/nodejs-agent:20.8.0-stretch-slimv14"
agentMountPath: /opt/appdynamics
imagePullPolicy: "IfNotPresent"

You can select one of these properties:

• image : Location of the agent image, and its tag/version.
• agentMountPath : Location of image artifacts in the image file system. The default is /opt/appdynamics. This configuration is required only if the path differs from the default path.
• alpineInitContainerImage: Location of alpine image and its tag/version to be used for the .NET instrumentation of init container.
• imagePullPolicy: The pull policy required for the agent's Docker image. The default is IfNotPresent . You can choose one of these pull policies based on your requirement:
  • Always
  • IfNotPresent
  • Never
  This parameter is used in the init containers that are added during auto-instrumentation.The default value is IfNotPresent .

For the specific language mentioned in this rule, this overrides image-info

You must configure this if you want to override the default cluster-level configuration and use a custom agent version for this specific rule selection.

netvizInfo

bciEnabled: true

port: 3892

To configure the Network Visibility App Agent, netviz Install Infrastructure Visibility with the Kubernetes CLIto install the Network Agent.

By default, netviz netviz

Supported values are:

1. bciEnabled : Boolean flag denoting whether netviz is enabled.
2. port : The port the Network Agent is listening on (default is 3892). Override this value only when running the Network Agent on a port other than the default port.

runAsGroup

If you configured the application container as a non-root user, provide the groupId of the corresponding group.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsGroup that is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

runAsUser

If you configured the application container as a non-root user, it provides the userId of the corresponding user.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsUser that is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

securityContext

Specify the required security context constraint parameters. For the list of parameters that can be used within securityContext, seesecurityContext Parameters.

runAsGroup

If you configured the application container as a non-root user, provide the groupId of the corresponding group.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsGroup that is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

runAsUser

If you configured the application container as a non-root user, it provides the userId of the corresponding user.

This sets the appropriate file permission on the agent artifacts.

This value is applied to all the instrumented resources.

Add this parameter, if you require to override the default value of runAsUser that is configured for default instrumentation, or if you require a specific value for the resources that satisfy this rule.

To control if a process can get more privileges than its parent process. The value is true when the container runs as:

• Privileged container
• CAP_SYS_ADMIN

To add or remove POSIX capabilities from the running containers. This uses the default set of capabilities during container runtime.

To run container in privileged mode, which is equivalent to root on the host.

The type of proc mount to use for the containers.

To specify if this container has a read-only root filesystem.

To specify if the container must run as a non-root user.

If the value is true, the Kubelet validates the image at runtime to ensure that the container fails to start when run as root. If this parameter is not specified or if the value is false, there is no validation.

To apply the SELinux context to the container. If this parameter is not specified, the container runtime allocates a random SELinux context for each container.

To specify the seccomp options used by the container. If seccomp options are specified at both the pod and container level, the container options override the pod options.

To specify Windows-specific options for every container.