Watson AIOps Container Monitoring Enhancement - Dynatrace Metadata Configuration

Added additional data in the comments section.
Option 1: Using ConfigMap

You can use a ConfigMap to define and store the above properties under the DT_CUSTOM_PROP key, specifying values for each property.
Once created, the ConfigMap needs to be mapped to your container so it can read the DT_CUSTOM_PROP values.

Steps:

1. Add the properties to the ConfigMap under the key DT_CUSTOM_PROP
2. In your container definition, add an environment variable named DT_CUSTOM_PROP
3. Reference the ConfigMap and Dynatrace key to pull the values.

Important: The environment variable must be named DT_CUSTOM_PROP for Dynatrace to recognize and collect the metadata.

Example ConfigMap:

apiVersion: v1
kind: configMap
metadata:
name: dynatrace-props
namespace: default
data:
DT_CUSTOM_PROP: CONTAINER_AIT=123 CONTAINER_DATACENTER=USA CONTAINER_ENVIRONMENT=Dev CONTAINER_FUNCTION=WebApp CONTAINER_K8_CLUSTER=useast1

Example Pod/Deployment YAML:

env:
- name:DT_CUSTOM_PROP
valueFrom:
configMapKeyRef:
name: dynatrace-props
key: DT_CUSTOM_PROP

Note: Ensure that DT_CUSTOM_PROP values contain no spaces (eg., use "WebApp" instead of "Web App") to avoid formatting issues.

Option 2: Hardcoding Values into Pod/Deployment

Alternatively, you can directly set the DT_CUSTOM_PROP environment variable in your Pod or Deployment file.

In this case, all metadata properties must be defined under a single environment variable named DT_CUSTOM_PROP.

Each key-value pair should be separated by a space to indicate a new metadata property.

Example:

apiVersion: v1
kind: Pod
metadata:
name: dynatrace-example
namespace: default
spec:
containers:
- name: dynatrace-example
image: dynatrace/example
env:
- name: DT_CUSTOM_PROP
value: CONTAINER_AIT=123 CONTAINER_DATACENTER=USA CONTAINER_ENVIRONMENT=Dev CONTAINER_FUNCTION=WebApp CONTAINER_K8_CLUSTER=useast1