Expected records missing in the api_consumer_access table from Service Graph Connectors (SGCs) on Yokohama, due to incomplete IRE payloads - Support and Troubleshooting

Expected records missing in the api_consumer_access table from Service Graph Connectors (SGCs) on Yokohama, due to incomplete IRE payloads .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Issue :

In Yokohoma version instances, api_consumer_access table are not being populated. Instead, incomplete payloads are being generated for them.

Root cause:

A CMDB-related entry with the relation api_consumer_access to cmdb_ci_api is missing. As a result, api_consumer_access table are not being populated, leading to an incomplete payload generation.

Workaround (Recommended):

For API Service Graph Connector for Apigee X - prior to version 2.1

Import the following 2 update sets:

Remove related entry update set Add related entry update set For API Service Graph Connector for AWS API Gateway - prior to version 2.2

Import the following 2 update sets:

ETL changes update set Add related entry update set Note: The order of import update sets does not affect the outcome and can be applied in any sequence.