Debugging KIC in Konnect

Kong Ingress Controller must communicate with the Konnect APIs to provide an integration with Gateway Manager. If you encounter issues with KIC in Konnect, you should first inspect logs from Kong Ingress Controller to identify the root cause.

The Prometheus metrics ingress_controller_configuration_push_count and ingress_controller_configuration_push_duration_milliseconds_bucket show upload failures to Konnect, where the dataplane label is the URL of Konnect.

Kong Ingress Controller logs the details for every failed request and response (method, URL, status code) it receives from Konnect by default.

If you set the LOG_LEVEL to trace, Kong Ingress Controller will log the details for every request and response it receives from Konnect.

Here is an example of a failed request/response log entry:

Request failed  {"x_b3_traceid": "66c731200000000034ce3297e8e64544", "x_b3_spanid": "4e6955874299011d", "x_datadog_trace_id": "3805034363203503428", "x_datadog_parent_id": "5650141246939267357", "v": 0, "method": "GET", "url": "https://us.kic.api.konghq.com/kic/api/control-planes/81bc4af5-ed3c-40b4-bb88-b5a05fbe34a1/oauth2?size=1000", "status_code": 404}

If your issue requires further investigation on the Konnect side, attach logs with tracing information to your support ticket.