How to test ACE timeout
This guide helps to troubleshoot why the call to the ACE dynamic API endpoint might timeout and how to mitigate it.
Routing
When deployed in the Kubernetes cluster, call usually from the consumer goes to cluster ingress controller and after that to ACE orch component. Routing between ACE components is described in system design document.
Troubleshooting
Information that is necessary to understand why timeout occurred is timeout setting and logs.
Ingress
Check Ingress Controller setup timeout settings
ACE Component configuration
It may be necessary to adjust ACE_API_TIMEOUT settings, see property description in system design document
Kibana search to obtain this information for digital-api-orch, dynamic-api-server, flow-runner components
Query for namespace dev-ace:
kubernetes.namespace_name: "dev-ace" and kubernetes.container_name: ("digital-api-orch" or "dynamic-api-server" or "flow-runner") and log: ACE_API_TIMEOUT
Log output:
