General Troubleshooting
This guide provides a structured approach to diagnosing and resolving common issues. Before escalating any concerns, follow the steps outlined below to identify potential causes and solutions. Using these preliminary checks can help resolve issues efficiently and minimize downtime.
If you encounter persistent issues or unexpected behavior that is not resolved using this guide, please reach out to the ScaleOps team for further support.
Verify Pod Status
Ensure all ScaleOps pods in the scaleops-system namespace are running and ready.
kubectl get pods -n scaleops-systemCollect Logs for Analysis
If a pod is failing or restarting continuously, collect logs for further analysis:
kubectl logs <pod-name> -n scaleops-systemDescribe Pods for Issues
Use kubectl describe on the pod to see any issues or problems, such as events or warnings.
kubectl describe pod <pod-name> -n scaleops-systemAccess the Dashboard to Review ScaleOps Health
You can either port-forward the service or use the defined ingress to access the ScaleOps dashboard and test the health endpoint.
Port-Forward
kubectl port-forward -n scaleops-system service/scaleops-dashboards8080:8080Using Ingress
Access the dashboard through the ingress URL defined in your cluster. Review the ScaleOps Health Dashboard within the Troubleshoot Tab
ScaleOps Health
Access this view to analyze the overall health of ScaleOps components, including CPU and memory usage, resource requests, and any detected issues over time.