driver logging improvment

[deeghuge]

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

• What openshift/kubernetes version are you running, and the architecture?
• kubectl get pods -o wide -n < csi driver namespace>
• kubectl get nodes -o wide
• CNSA/Spectrum Scale version
• Remote Spectrum Scale version
• Output for ./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

• Component:
• Severity:
• Customer Impact:
• Customer Probability:
• Phase:

Note : See labels for the labels

[deeghuge]

@hemalathagajendran Please consider these additional requirement. If you think these needs to be handled seperately that is also fine.

• Logging the time taken for each operation like volume create delete
• Marking when operation started and completed
• generate stat mainly volume created/delete per hour and per day

[deeghuge]

Most of the improvement in driver logging are complete. missing pieces are stats and verifying right logs are generated for given log levels