[Backend] 9.6 Add Business Metrics Tracking

[ACodehunter]

ETA

2 days

Description

This is a complex backend task that requires deep understanding of Rust, Axum, PostgreSQL, and Redis. The implementation should follow best practices for async Rust and be production-ready.

Requirements

• Implement the feature according to the title and description
• Work only in the specified files within the backend/ folder
• Add comprehensive unit and integration tests
• Update documentation in backend/README.md
• Ensure all code follows Rust best practices and project conventions

Technical Specifications

• Files to work in: backend/src/services/business_metrics.rs
• All code must be within the backend/ folder
• Use Axum for HTTP handling
• Use SQLx for database operations
• Use Redis for caching and job queues
• Implement proper error handling with custom error types
• Add tracing for observability

Acceptance Criteria

• Feature is fully implemented and tested
• Code compiles without warnings
• All tests pass (cargo test)
• Code is documented with Rustdoc comments
• Performance benchmarks meet targets
• No breaking changes to existing APIs (unless specified)

Resources

• Axum Documentation
• SQLx Documentation
• Tokio Documentation
• Redis Documentation
• Backend Code Structure

Notes for Contributors

• IMPORTANT: All work must be done within the backend/ folder
• Follow the existing project structure and code style
• Add comprehensive error handling
• Consider backward compatibility
• Test thoroughly before submitting PR
• Update backend/Cargo.toml if adding new dependencies

[hashmart138-creator]

@hashmart138-creator has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi @benelabs/crucible team!

I’d like to work on the Business Metrics Service (Issue #253). I am proficient in async Rust and the Axum/SQLx/Redis stack. I’ll ensure the implementation in business_metrics.rs includes robust error handling, tracing for observability, and full test coverage as specified.

ETA: 24 hours

Could you please assign this to me? I'm ready to start!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @hashmart138-creator to this issue.

[wowamaxe-glitch]

@wowamaxe-glitch has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I am a full-stack developer, and I’d like to take on this issue. I will ensure all requirements are properly implemented.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @wowamaxe-glitch to this issue.

[drips-wave]

Congratulations, @wowamaxe-glitch! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @wowamaxe-glitch: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊