meshctl debug report
Reference for the ‘meshctl debug report’ command.
meshctl debug report
Generates Gloo Mesh .tar.gz file for debugging issues
Synopsis
report selectively captures cluster information and logs into an archive to help diagnose problems. By default the current context will be used.
Multiple clusters can be captured using comma delimited notation meshctl debug report –kubecontext cluster1,cluster2,cluster3
Automatic upload can be enabled to send the debug information to a secure repo owned by Solo.io. It is recommended to set a folder structure that makes it easy to identify your upload
meshctl debug report –upload true –upload-dir <your_name>/<issue_name> Eg. meshctl debug report –upload true –upload-dir my-company/ssl-issues
By default, only gloo mesh and istio operational information is gathered. Sometimes application proxy information is needed. To include application namespaces use –include-namespaces
meshctl debug report --include-namespaces app1,app2
If all of your applications are deployed to a single namespace it is possible to filter down to specific pod names using a glob pattern.
meshctl debug report –include-namespaces app1 –include-pods my-deploy*,frontend-54fddd8c77-zwgnl
meshctl debug report [flags]
Options
--gloo-mesh-namespace string Namespace where Gloo Mesh is installed. (default "gloo-mesh")
-h, --help help for report
--include-namespaces strings List of application namespaces to get proxy logs.Supports glob pattern (default none)
--include-pods strings List of k8s pods to get proxy logs. Supports glob pattern (app-namespaces required, default all for the namespace)
--istio-namespace string Namespace where Istio control plane is installed. (default "istio-system")
--upload Upload snapshot to secure Solo.io owned bucket.
--upload-bucket string GCS bucket owned by solo.io. (default "solo-bug-reports")
--upload-dir string Folder in GCS to store snapshot under.
Options inherited from parent commands
--kubeconfig string Path to the kubeconfig file for the cluster.
--kubecontext string Kubernetes context for the cluster to run the command in.
-n, --namespace string Namespace to run the command in. (default "gloo-mesh")
--plain Disable styling for terminal output.
-v, --verbose Enable verbose logging.
SEE ALSO
- meshctl debug - Gloo Mesh debugging commands