Log Analysis
For troubleshooting common error scenarios, the AppViewX Cloud Connector’s logs can be analyzed to identify the cause and the solution required, therefore.
Within the installation directory, the AppViewX Cloud Connector logs can be accessed at ./deps/logs/cloud-connector.log.
AppViewX comes with a set of commands required for troubleshooting based on log analysis.
To troubleshoot based on log analysis, you can use the
kubectl commands as usual. You can also use the k3s available
in the ./deps/tools folder. Using k3s, you can fire kubectl
commands in the form k3s kubectl.
Syntax:
<kubectl-command-parameters>
- To list all the pods and their status, use the following
syntax:
./deps/tools/k3s kubectl get pods -A - To delete a pod and then restart it, use the following
syntax:
./deps/tools/k3s kubectl delete pods <pod-id> -n <name-space> - To describe the pods, use the following syntax:
./deps/tools/k3s kubectl describe pods <pod-id> -n <name-space> - To check the logs via
kubectlcommand for k3s related pods, use the following syntax:./deps/tools/k3s kubectl logs <pod-id> -n kube-system
Note: The k3s cluster created by the AppViewX Cloud Connector is
called cc.
Troubleshooting: If your error remains unresolved even after
executing the above troubleshooting steps, email the AppViewX Technical Support team
at [email protected] or call them at +1 (212) 390 1644.
