Details
-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
None
-
Kiali in troubleshooting page
-
False
-
False
-
To Do
-
100
-
100%
Description
One of Kiali's goals is to aid in troubleshooting a service mesh. Thus, we should add content to our troubleshooting page that demonstrates where Kiali can help. Likewise
This content could include:
- Validating the health of the control plane (
OSSMDOC-461) and data plane components (OSSMDOC-463) [These two moved to getting started epic (OSSMDOC-449)] - Explanations of log lines of interest (of Envoy...)
- istio-ctl command equivalence
The troubleshooting page as is was written from the perspective of support engineers, thus it doesn't have Kiali content currently. In preparation for this epic, we should review the troubleshooting page - add Kiali content where it can be used, and document additional Kiali use cases that aren't captured.
Distinction of two types of troubleshooting, per jstickler :
1 – Troubleshooting the Service Mesh product (upper case), that is, the thing that we’ve installed to monitor and manage our applications. This is the infrastructure layer, the control plane. This is troubleshooting information for the installer, probably a cluster administrator, to help install and configure the Service Mesh product (Istio, Kiali, Jaeger, etc.)
2 – Troubleshooting the services in the service mesh (lower case), that is the microservices that make up the service mesh that we want to observe and manage. This is the data plane, the applications that might be added to the mesh, or pods that are failing. This is troubleshooting information for DevOps, or for developers, about why their application services are failing or that their network connections are failing, or that requests timing out, etc.
Troubleshooting Envoy with Kiali
https://medium.com/kialiproject/troubleshooting-envoy-with-kiali-7f78a57b16ad
Logs
Configuration
Metrics