MTA-7134-LLM-Proxy-Transaction-Logging-Schema-Audit-Trail-Integration#379
Conversation
Signed-off-by: A.Arnold <anarnold@redhat.com>
|
Warning Review limit reached
Next review available in: 28 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR adds a new documentation page describing how to audit and monitor LLM proxy interactions in the MTA Developer Lightspeed setup, covering log access via oc logs, the transaction log JSON schema, and SIEM/log aggregator forwarding configuration. The master guide is updated to include this new topic. ChangesLLM Proxy Auditing Documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/topics/developer-lightspeed/proc_auditing-llm-proxy-transactions.adoc`:
- Around line 27-30: Update the prerequisites in
proc_auditing-llm-proxy-transactions.adoc so they require the minimum
namespace-scoped role needed to read proxy pod logs in the MTA namespace, rather
than cluster-admin; keep cluster-admin only for the later forwarding setup
section if needed. Reference the prerequisites list and the oc logs workflow,
and make the role requirement specific to the log-reading step instead of the
broader cluster-wide access.
- Around line 170-210: The ClusterLogForwarder example in the proxy-auditing doc
hard-codes the pod selector label, which may not match the actual proxy
workload. Update the selector in the example to use a placeholder such as
__<proxy_workload_label>__ instead of app: mta-ui-proxy, and keep the
surrounding guidance in sync by referring readers to verify the label before
applying the ClusterLogForwarder resource.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fb7c899a-f543-41b7-89c5-666f2fb4f52e
📒 Files selected for processing (2)
docs/developer-lightspeed-guide/master.adocdocs/topics/developer-lightspeed/proc_auditing-llm-proxy-transactions.adoc
Summary by CodeRabbit