cc @derekbit @shuo-wu

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Does the PR include the explanation for the fix or the feature?

• Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
  The PR for the YAML/chart change is at: feat(metrics): add schema for SPDK info collection to upgrade responder #7296

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at feat(telemetry): collect SPDK related info longhorn-manager#2346

• Which areas/issues this PR might have potential impacts on?
  Area monitoring, spdk
  Issues

• If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
  The LEP PR is at

• If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
  The UI issue/PR is at

• If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
  The documentation issue/PR is at doc(telemetry): collect SPDK node disk type website#807.

• If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
  The automation skeleton PR is at
  The automation test case PR is at
  The issue of automation test case implementation is at (please create by the template)

• If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
  The engine automation PR is at

• If labeled: require/manual-test-plan Has the manual test plan been documented?
  The updated manual test plan is at test(manual): upgrade responder should collect SPDK info longhorn-tests#1619

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at

Verified pass on longhorn master (longhorn-manager c46a54) with test steps

Deploy Longhorn and create 3 v1 volumes and 2 v2 volumes:

longhorn_disk_filesystem_Count

> kubectl exec -it ${influxdb_pod} -- influx -execute 'SELECT "longhorn_disk_filesystem_count" FROM "upgrade_request"' -database="${app_name}_upgrade_responder"
name: upgrade_request
time                longhorn_disk_filesystem_count
----                ------------------------------
1703234426043451144 1
1703234426882845418 1
1703234426998184569 1

longhorn_disk_block_count

> kubectl exec -it ${influxdb_pod} -- influx -execute 'SELECT "longhorn_disk_block_count" FROM "upgrade_request"' -database="${app_name}_upgrade_responder"
name: upgrade_request
time                longhorn_disk_block_count
----                -------------------------
1703234426043451144 1
1703234426998184569 1

longhorn_volume_backend_store_driver_v1_count

> kubectl exec -it ${influxdb_pod} -- influx -execute 'SELECT "longhorn_volume_backend_store_driver_v1_count" FROM "upgrade_request"' -database="${app_name}_upgrade_responder"
name: upgrade_request
time                longhorn_volume_backend_store_driver_v1_count
----                ---------------------------------------------
1703234426043451144 3

longhorn_volume_backend_store_driver_v2_count

> kubectl exec -it ${influxdb_pod} -- influx -execute 'SELECT "longhorn_volume_backend_store_driver_v2_count" FROM "upgrade_request"' -database="${app_name}_upgrade_responder"
name: upgrade_request
time                longhorn_volume_backend_store_driver_v2_count
----                ---------------------------------------------
1703234426043451144 2