Updating IntroscopeEnterpriseManager.properties in DX O2

Table of Contents

STEP#1: Check the current value

a) find apm-em pod name

kubectl get pods -n | grep apm-em

for example:

kubectl get pods -ndxi | grep apm-em

output example:

apm-em-10-466718-001-b6b6d6874-248gs 1/1 Running 0 7s

b) ssh the apm-em pod

kubectl exec -ti -n bash

for example:

kubectl exec -ti apm-em-10-466718-001-b6b6d6874-248gs -ndxi bash

cd config

For example, you would like to change the value of introscope.enterprisemanager.alerts.maxPeriods=2000

more IntroscopeEnterpriseManager.properties | grep introscope.enterprisemanager.alerts.maxPeriods

output example:

#introscope.enterprisemanager.alerts.maxPeriods=2000

STEP#2: Change the value

a) Find the apm-em deployment

kubectl get deployments -n

For example:

kubectl get deployments -ndxi

output example:

NAME READY UP-TO-DATE AVAILABLE AGE
apm-em-10-466718-001 1/1 1 1 30h
apm-logstash-10-466718 1/1 1 1 30h
apm-wv-10-466718 1/1 1 1 30h
apmservices-apmbacking-singleton 1/1 1 1 30h
apmservices-at-001 1/1 1 1 30h

b) Edit the apm-em deployment

kubectl edit deployment -n

For example:

kubectl edit deployment apm-em-10-466718-001 -ndxi

Add the wanted property, for example:

introscope.enterprisemanager.alerts.maxPeriods=2000

– Save the file a new apm-em pod will be created automatically.

c) find the new apm-em pod name

kubectl get pods -n| grep apm-em

For example:

kubectl get pods -ndxi | grep apm-em

d) ssh the pod and verify the new property has been added

kubectl exec -ti -n bash

For example:

kubectl exec -ti apm-em-10-466718-001-b6b6d6874-248gs -ndxi bash

more IntroscopeEnterpriseManager.properties | grep introscope.enterprisemanager.alerts.maxPeriods

output example:

#introscope.enterprisemanager.alerts.maxPeriods=2000
introscope.enterprisemanager.alerts.maxPeriods=2000