chore: Add CSI-specific Prometheus metrics

[hccheng72]

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR introduces dedicated CSI operation metrics for the AzureFile CSI driver, separate from the existing Azure cloud provider API metrics, enabling better observability of CSI operations.

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

none

[k8s-ci-robot]

Hi @hccheng72. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[andyzhangx]

/ok-to-test

[Copilot]

Pull request overview

This PR introduces dedicated CSI-specific Prometheus metrics for the AzureFile CSI driver by creating a new metrics package (pkg/metrics), separate from the existing Azure cloud provider API metrics. The change enables better observability of CSI operations with operation-level tracking of duration and success rates.

Changes:

• Added new pkg/metrics package with CSI-specific Prometheus metrics (histogram and counter)
• Integrated new CSI metrics into controller server operations (CreateVolume, DeleteVolume, CreateSnapshot, DeleteSnapshot, ControllerExpandVolume)
• Integrated new CSI metrics into node server operations (NodePublishVolume, NodeUnpublishVolume, NodeStageVolume, NodeUnstageVolume)

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
pkg/metrics/metrics.go	Defines CSI-specific Prometheus metrics with histogram and counter collectors, plus CSIMetricContext helper for tracking operation duration and success
pkg/metrics/metrics_test.go	Comprehensive unit tests for the new metrics package including success/failure tracking, labeled metrics, and edge cases
pkg/azurefile/controllerserver.go	Replaces cloud-provider metrics with new CSI metrics in controller operations; removes unused error check code
pkg/azurefile/nodeserver.go	Adds CSI metrics tracking to node operations; maintains cloud-provider metrics for remaining operations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[andyzhangx]

/hold

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 8 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, hccheng72

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andyzhangx]

/hold cancel

[andyzhangx]

/cherrypick release-1.34

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2946

Details

In response to this:

/cherrypick release-1.34

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.