Open Data Connector (ODC) Troubleshooting

Products

• DX Operational Intelligence
• DX OI SaaS
• DX Operational Observability

Issue/Introduction

The following is a high-list of tips, techniques and suggestions to employ when troubleshooting ODC issues.

Environment

• DX O2 SaaS
• DX O2 OnPremise 2*

Resolution

Table of Contents

• ERROR 404 NOT_FOUND "Unable to Fetch the schema"
• CHECK ODC SUPPORTABILITY METRICS
• HOW TO CAPTURE ALARM PAYLOAD

 

 

ERROR 404 NOT_FOUND "Unable to Fetch the schema"

You need to update the URL that the alarm is sent to in AppNeta.    

 

In DXO2 go to Settings/Setup Integrations and copy the Ingestion API link

In AppNeta go to the API and update the observer with the new URL.

 

 

CHECK ODC SUPPORTABILITY METRICS

(If dx o2 OnPremise setup) 

 

a. Login to Cluster Manager as MASTERADMIN

b. Go to Metric Browser 

 

You can monitor or check for health and data ingestion by looking at the below supportability metrics:

 

  - oiservices | odc-connector-<####> | Beans | ODC - ## | Alarms: Alarms Published

  - oiservices | odc-connector-<####> | Beans | ODC - ## | Alarms: Alarms Received
  - oiservices | odc-connector-<####> | Beans | ODC - ## | Metrics: Published Per Interval
  - oiservices | odc-connector-<####> | Beans | ODC - ## | Metrics: Received Per Interval
  - oiservices | odc-connector-<####> | Beans | ODC - ## | Topology: Entities Published
  - oiservices | odc-connector-<####> | Beans | ODC - ## | Topology: Entities Received

 

 

HOW TO CAPTURE ALARM PAYLOAD

For capturing the payload, update the following property :

 "LOGGING_LEVEL_INGESTEDDATALOGGER: "DEBUG" 

 

following log file should have the payload coming from webhook:

 

odc-connector-ingestion-api.log

Additional Information

Techdocs - ODC connector