Open deeghuge opened 2 years ago
@hemalathagajendran Please consider these additional requirement. If you think these needs to be handled seperately that is also fine.
Most of the improvement in driver logging are complete. missing pieces are stats and verifying right logs are generated for given log levels
Describe the bug
When volume creation or other operations are tried in parallel, it is very difficult to track the flow of operation in the csi logs. Having context/transaction id passed in the flow will help track the flow of operations individually.
How to Reproduce?
Create multiple volume in parallel and check the driver logs
Expected behavior
I should be able to isolate logs of single operation
Data Collection and Debugging
Environmental output
kubectl get pods -o wide -n < csi driver namespace>
kubectl get nodes -o wide
./tools/spectrum-scale-driver-snap.sh -n < csi driver namespace> -v
Tool to collect the CSI snap:
./tools/spectrum-scale-driver-snap.sh -n < csi driver namespace>
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Add labels
Note : See labels for the labels