Troubleshooting
#
Elasticsearch#
ResponseError: parse_exception-e ELASTIC_REQUEST_COMPRESSION=allow
- CLI Options
Some version of elasticsearch return ResponseError: parse_exception
in this case don't use compression.
#
TimeoutError: Request timed out-e ELASTIC_TIMEOUT=10000
- CLI Options
Default value of ELASTIC_TIMEOUT
option is very small. You can set higher requestTimeout and pingTimeout e.g. -e ELASTIC_TIMEOUT=10000
but even if the default value is not sufficient, consider upgrading the network or increasing the sizing of the elastic cluster.
#
Live reporting debugging-e ELASTIC_OBSERVABILITY=allow
- CLI Options
This print settings of elasticsearch connection, request and response events and payload to stdout.
Every request and response has the same requestId e.g. [0-0] on:response: requestId: 1
each additional request creates an incremental requestId.
#
Kibana#
Visualizations aren’t smoothlyThere may be several reasons for this
- Your monitor script contains some errors. Please use
kubectl -n canary logs -f <name-of-pod> -c
canary for check logs, or you can check.filebeat
index in a Kibana - You don’t have sufficient resources on your k8s cluster for run Canarytrace instance.
#
Canarytrace#
JavaScript heap out of memorySometimes a performance audit consumes more resources because individual audits can be more challenging.
Solutions
Please increase resource for Canarytrace docker image:
Do you find mistake or have any questions? Please create issue, thanks 👍