AIOps - How to create the Jarvis apis and elasticsearch endpoints
search cancel

AIOps - How to create the Jarvis apis and elasticsearch endpoints

book

Article ID: 226870

calendar_today

Updated On:

Products

DX Operational Intelligence DX Application Performance Management CA App Experience Analytics

Issue/Introduction

Starting from DX Platform 21.x Jarvis API and elastic search routes/ingress are disabled by default due to security purpose.

How can check Jarvis and Elastic health and data?

Environment

DX Platform 21.x and higher

 

Cause

Jarvis APIs: 

Starting from 21.3.1 we removed the direct jarvis APIs route/ingress, however, you can check Jarvis health using the nginx router, for example, http://doi-nginx.<endpoint>/health:

Elastic APIs:
 
For Elastic, default routers are now disabled, however, you can still query Elastic from inside the pods using curl or by creating a router as described below

Resolution

Step#1 : Open the appropriate configuration yml file:

If you are using secured routes (tlsEnabled):

a) For Jarvis APIs : 

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-apis-ingress.secure.yml


b) For ElasticSearch: 

Depending on elastic cluster size (small / medium)

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.secure.small.yml

Or

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.secure.medium.yml

 

If using in-secured routes (tlsDisabled):

a) For Jarvis APIs:

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-apis-ingress.insecure.yml


b) For ElasticSearch:

Depending on elastic cluster size (small / medium)

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.insecure.small.yml

Or

<INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.insecure.medium.yml

 

Step# 2: Replace the below text values :

{{namespace}}
{{routerip}}

 

For example:

Replace {{namespace}} with dxi

Replace {{routerip}} with es.#.#.#.#.nip.io

 

Step# 3 : Apply the new configuration:

If you are using secured routes (tlsEnabled), then follow below steps :

a) For Jarvis APIs : 

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-apis-ingress.secure.yml


b) For ElasticSearch: 

Depending on cluster size (small / medium)

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.secure.small.yml

Or

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.secure.medium.yml

 

If using in-secured routes (tlsDisabled), then follow below steps:

a) For Jarvis APIs:

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-apis-ingress.insecure.yml


b) For ElasticSearch:

Depending on elastic cluster size (small / medium)

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.insecure.small.yml

Or

kubectl apply -f <INSTALL_DIR>/files/meta/plain/nextgen/dx-base/install/jarvis-elasticsearch-ingress.insecure.medium.yml

Additional Information

AIOPs - Troubleshooting, Common Issues and Best Practices