Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
Was this helpful?
Ensure the proxy container for each service is running
e.g. docker ps | grep <WORKFLOW-NAME>-<SERVICE-NAME>.proxy-1
To learn about which containers should be running, see here
If the workflow is either record
, mock
, or test
ensure the gateway service is running
e.g. docker ps | grep <WORKFLOW-NAME>-gateway.service-1
Ensure that a request gets routed to the correct service container
To learn more about request service flow, see here
To view service logs run:
make -f .stoobly/docker/Makefile <WORKFLOW-NAME>/logs
To view gateway logs run:
make -f .stoobly/docker/Makefile <WORKFLOW-NAME>/logs options="--container service --service gateway"
To learn more about the command, see here
Run either of the following:
make -f .stoobly/docker/Makefile ca-cert install
stoobly-agent ca-cert install
For manual installation, see https://docs.mitmproxy.org/stable/concepts-certificates/
Double check if request exists in the scenario
By default the UI is configured to run on http://localhost:4200
See .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/bin/configure
To learn more about rewrite rules, see here
See .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/lifecycle_hooks.py
To learn more about lifecycle hooks, see here
See .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/bin/configure
To learn more about match rules, see here
Double check if request exists in the scenario
By default the UI is configured to run on http://localhost:4200
To learn more, see here