chore(api): reduce log verbosity for routine operations

[itzlambda]

Downgrades log levels for high-frequency routine messages to reduce noise in production logs:

• API key authentication success: debug → trace
• Scope authorization success: debug → trace
• Billing telemetry sends: debug → trace
• Validator health checks: debug → trace
• GPU offerings refresh (no changes): debug → trace
• GPU offerings refresh (with count): info → debug

Summary by CodeRabbit

• Chores
  • Fine-tuned logging verbosity levels across authentication, authorization, and server monitoring components to improve log organization and filtering capabilities.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Three source files updated to downgrade certain debug log statements to trace level. Changes affect authentication middleware, scope validation middleware, and server logging for health checks, billing telemetry, and periodic refresh operations. No functional behavior, control flow, or API modifications introduced.

Changes

Cohort / File(s)	Summary
Logging Level Updates crates/basilica-api/src/api/middleware/auth.rs, crates/basilica-api/src/api/middleware/scope.rs, crates/basilica-api/src/server.rs	Downgraded debug log statements to trace level across API key authentication success, scope validation authorization messages, health checks, billing telemetry, and periodic refresh paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• All changes are homogeneous logging-level downgrades with no functional impact
• No control flow, error handling, or API modifications
• Straightforward pattern applied consistently across files

Poem

🐰 Logs whisper softer now, from debug's shout to trace's gentle hum,
Middleware and servers alike embrace the quieter sum,
Details dance deeper still, for those who listen close,
While flow and logic rest untouched—a logging-only toast! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main objective of the pull request—reducing log verbosity by downgrading logging levels for routine operations across multiple files.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch api-log-noise

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

crates/basilica-api/src/api/middleware/auth.rs (1)

211-214: Consider downgrading JWT auth success to trace for consistency.

The API key authentication success message was downgraded to trace (line 110), but JWT authentication success remains at debug. Since both are high-frequency routine operations, consider applying the same log level reduction here for consistency.

🔎 Suggested change for consistency

-        debug!(
+        trace!(
             "JWT authentication successful for user: {}. Scopes: {:?}",
             claims.sub, claims.scope
         );

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e7ad14 and fc71ac7.

📒 Files selected for processing (3)

• crates/basilica-api/src/api/middleware/auth.rs (2 hunks)
• crates/basilica-api/src/api/middleware/scope.rs (2 hunks)
• crates/basilica-api/src/server.rs (4 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: lint-complex
• GitHub Check: build-api (stable)

🔇 Additional comments (6)

crates/basilica-api/src/api/middleware/auth.rs (1)

110-113: LGTM: Appropriate log level reduction for routine operation.

Moving API key authentication success from debug to trace is appropriate for reducing log noise in production, as this is a high-frequency routine operation.

crates/basilica-api/src/api/middleware/scope.rs (1)

66-72: LGTM: Appropriate log level reduction for high-frequency operation.

Downgrading successful scope authorization messages to trace is appropriate. This middleware runs on every authenticated request, making it a high-frequency operation that can generate significant log noise at debug level.

crates/basilica-api/src/server.rs (4)

190-196: LGTM: Appropriate log level reduction for periodic billing task.

Downgrading the billing telemetry success message to trace is appropriate. This task runs every 30 seconds (line 1046) and generates routine operational logs that don't need debug-level visibility in production.

---

882-882: LGTM: Appropriate log level reduction for periodic health checks.

Downgrading the validator health check success message to trace is appropriate. This task runs at regular intervals and generates high-frequency routine logs.

---

969-978: LGTM: Appropriate and nuanced log level adjustments for periodic refresh task.

The logging changes for GPU offerings refresh are well-designed:

• Trace for routine refresh attempts (line 969)
• Debug for successful fetches with count (line 973, downgraded from info)
• Trace for no-op refreshes during cooldown (lines 975-977)

This provides appropriate signal-to-noise ratio while maintaining visibility into meaningful state changes.

---

1022-1025: LGTM: Appropriate log level reduction for periodic health checks.

Downgrading the secure cloud health check completion message to trace is appropriate. This is a routine periodic task that doesn't need debug-level visibility in production.