Guardrail : Log every request

[dennyabrain]

Is your feature request related to a problem? Please describe.
Every API request that is made against kaapi-guardrails needs to be logged in the database. This is to allow post-facto investigations of any API calls. Since a guardrail consists of multiple validators that could throw exception unexpectedly, we would need to know which validator failed and why.

Describe the solution you'd like
For every request we store in the database details of that request - input, output, configuration. For each validator, we store the same details.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

_{You can configure auto-planning by selecting labels in the issue_enrichment configuration.}

🔗 Similar Issues

Related Issues

• Tattle: Guardrail and Validators kaapi-backend#433
• Platform-wide Logging Review and Standardization kaapi-backend#213
• Guardrail : Add Guardrail Framework #3
• Guardrail: Add Documentation #8
• Module: Timestamps kaapi-backend#161

👤 Suggested Assignees

• AkhileshNegi
• baarish-tesu

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!