Debugging Connect

The effective configuration of Axual-Connect can be seen by inspecting the connect-pods in kubernetes.
You can do that via k9s or kubectl.
Make sure that your kubectl uses the correct context.

The configuration of the helm-charts are in the values.yaml file that you used to deploy the helm chart.

The most recent logs can be seen by using k9s or command line:

Historical logging is not kept when deploying the platform via helm.
You are encouraged to configure a central logging system and configure it to scrape Axual-Connect logs, too.

The port on which the API is hosted can be seen via k9s or kubectl.

The port is configurable in values.yaml.

You can hit the service endpoint from inside any container in the same k8s namespace.
The recommended way, if possible, is to port-forward the endpoint from a Connect Pod and check the API in your browser.

Now that you know how to check the configuration, logs and the API, you can debug connect.
Note that runtime configuration, such as customer connect-application definitions, are stored in the MGMT-API database.

The "AOM" (axual operations manager) is a middle-man between MGMT-API and Connect.
Sometimes it’s worth checking the AOM logs, as well.

As we’ll identify common problems, we’ll list them here.