DX APM - Troubleshooting Guidelines for doi-soacorrelationengine

book

Article ID: 143270

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

How can I troubleshoot and investigate issues related to doi-soacorrelationengine?

Environment

APM 11.x, 19.x

Resolution

1- Check that doi-soacorrelationengine pod is running

kubectl get pods -n<apm-namespace> | grep doi

For example:

kubectl get pods -ndxi | grep doi

2.- Check that doi-soacorrelationengine index exist and that data is being correlated

http(s)://{es_endpoint}/_cat/indices

In the below example, data is being correlated, 1732

 

3.Review the doi-soacorrelationengine log:

Fist, find the pod name:

kubectl get pods -ndxi | grep doi



Connect or ssh doi-soacorrelationengine pod as below:

kubectl exec -it doi-soacorrelationengine-69bf6b4b4d-r5w6q -ndxi bash

cd log

tail -f correlationengine.log

 

4.Check soacorrelation logs from previous days from <NFS directory>

In this example:  /data/nfs/ca/dxi/

cd /doiservices/soacorrelationengine/logs

unzip CorrelationHazelCast-<timestamp>.log.gz

Attachments