DX APM Exited and Paused containers

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Using Kubernetes under DX-APM 21.3

There a lot of Exited and Paused containers, do you know the cause of it? Or is there a workaround/fix for this kind of behavior?

 

Environment

Release : 21.3

Resolution

The list contains or shows only exited status, which is the last state of a container lifecycle. 

Usually there are exit codes that can be read to understand why they are exited. Recommend the user to look out for this. 

The other thing we can do is to describe the POD, and also look into container logs for possible reasons, and EXIT code or events definitely will help narrow down.