DX AIOps - How to check Jarvis services Health

Products

• DX Operational Intelligence
• DX Application Performance Management
• CA App Experience Analytics

Issue/Introduction

The following is a high-list of techniques and suggestions to employ when troubleshooting Jarvis  common performance and configuration issues.

Environment

DX 2x

Resolution

Table of Contents

• 1.Checklist
• 2.What to collect if the problem persist?

1.Checklist

 

Make sure ALL Jarvis services are in green status

 

 

Option 1:

 

-Locate the doi-nginx endpoint:

kubectl get ingress -ndxi | grep nginx

doi-nginx-ingress                     doi-nginx.lvntest010772.bpc.broadcom.net                            80        89d

 

-Connect to : http(s)://doi-nginx.<endpoint>/health

 

For example: https://doi-nginx.#.#.#.nip.io/health

 

 

Verify that all jarvis services are in green status

 

 

Option 2: 

 

- Connect to any kafka pod

 

   kubectl exec -ti <jarvis-kafka-pod> sh -n<namepsace>

 

- Query the health page:

 

   curl -XGET 'http://jarvis-apis:8080/health'

 

 

NOTE: Jarvis APIS and ElasticSearch route/ingress endpoints are not longer available, however, you can re-create them as explained in https://knowledge.broadcom.com/external/article/226870

 

 

 

2.What to collect if the problem persist?

If after applying the above checks and recommendations the problem persist, collect the below logs and contact Broadcom Support:

 

<NFS>/jarvis/apis/logs/<jarvis-apis-pod>/*.log
<NFS>/jarvis/indexer/logs/<jarvis-indexer-pod>/*.log
<NFS>/jarvis/kafka-logs/kafka-<#>/*.log
<NFS>/jarvis/esutils/logs/<jarvis-esutils-pod>/*.log
<NFS>/jarvis/zookeeper-logs/zookeeper-<#>/*.log

Additional Information

https://knowledge.broadcom.com/external/article/190815/aiops-troubleshooting-common-issues-and.html