Troubleshooting the Alert - Connector Resource loading Error/Connector Permission loading Error¶
Root Cause¶
Below is one of possible reasons for Connector Resource loading Error or Connector Permission loading error:
- The connection to the service has no timeout, so it stays open forever and can cause the program to get stuck in an infinite loop.
Troubleshooting Steps¶
If connector encounter issues related to resource loading or permission loading , follow these steps to capture diagnostic information and share it with the support team:
- Capturing a Thread Dump and Collecting Support Files.
- Create support ticket and attach the obtained thread dump, logs, and properties files and also add Grafana metrics screenshots for the connector where issue occurred.
- Restart the connector service pod to restore functionality. Refer to Recommended Way to Restart Service Pods for safe restart procedures.
- The engineering team will review the collected information, identify the root cause, and provide further guidance.
- After restarting the pod, verify that no alerts are triggered again to confirm that the issue is resolved.
- Prev topic: Troubleshooting for Connector