Skip to content

Conversation

@joshrotenberg
Copy link
Collaborator

Summary

Adds structured tracing instrumentation to the redis-cloud API client, matching the pattern already used in redis-enterprise.

Changes

  • Add #[instrument] spans to all HTTP methods (get, post, put, delete, patch)
  • Add debug! logs for method/URL on each request
  • Add trace! logs for request bodies and response status
  • Consistent with redis-enterprise client tracing pattern

Benefits

  • Better observability for debugging API calls
  • Structured spans for tracing backends (Jaeger, etc.)
  • Request/response timing via span duration
  • Consistent logging across both API clients

Related

Partial fix for #105 - establishes the pattern for future tracing enhancements

Closes #105

- Add #[instrument] spans to all HTTP methods for structured tracing
- Add debug! logs for method/URL on each request
- Add trace! logs for request bodies and response status
- Follows same pattern as redis-enterprise client

This establishes a consistent tracing pattern across both API clients
for better observability and debugging.

Partial fix for #105
@joshrotenberg joshrotenberg merged commit 4104271 into main Nov 21, 2025
16 checks passed
@joshrotenberg joshrotenberg deleted the feat/tracing-instrumentation branch November 21, 2025 18:50
This was referenced Nov 19, 2025
This was referenced Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Enhanced tracing spans with retry and timing context

2 participants