Record Redis command latency metrics

[haasonsaas]

Summary

• attach the shared Redis command metrics hook to the ASB runtime-store client during bootstrap
• keep the instrumentation testable with an injectable registerer while production uses the default registry
• bump service-runtime to v0.1.18 and add a miniredis-backed metrics assertion

Testing

• go test ./internal/bootstrap ./cmd/asb-api ./internal/api/httpapi
• go test ./...
• git diff --check

[cursor]

PR Summary

Low Risk
Low risk: adds Prometheus instrumentation and a small bootstrap-time error path when the metrics hook can’t be registered, without changing Redis command behavior or data handling.

Overview
Adds Redis command observability during bootstrap by attaching the service-runtime Prometheus hook to the runtime-store Redis client (using the default registry in production, but allowing an injected registerer for tests).

Introduces a miniredis-backed unit test that exercises SET/GET and asserts the emitted asb_redis_commands_total and duration histogram metrics, and bumps github.com/evalops/service-runtime to v0.1.18 to pick up the shared hook implementation.

^{Reviewed by Cursor Bugbot for commit bca977c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit bca977c. Configure here.}

[cursor]

Redis client leaked on instrumentation error path

Low Severity

If instrumentDefaultRedisClient returns an error, newRuntimeStore returns without closing the newly created client. The Close function is only returned to the caller on the success path (line 478), so this error path leaks the Redis client. Adding client.Close() before returning the error would ensure cleanup.

 

^{Reviewed by Cursor Bugbot for commit bca977c. Configure here.}