litellm - 💡(How to fix) Fix [Feature]: generic_guardrail_api blocked requests not logged in Guardrails Monitor [1 participants]

Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

Hi,

I'm using a custom guardrail via generic_guardrail_api that correctly blocks requests and returns action: BLOCKED, the API call itself works fine. However, blocked requests never appear in the Guardrails Monitor UI (/ui/?page=guardrails-monitor).

Setup:

LiteLLM main-latest — version 1.82.6 (pulled May 9, 2026)

generic_guardrail_api with mode: "pre_call"

PostgreSQL backend with store_audit_logs: true and store_model_in_db: true

No external logging provider (Langfuse, etc.)

Expected behavior: Blocked requests appear in the Guardrails Monitor, the same way the built-in LiteLLM Content Filter logs them natively without any external provider.

Actual behavior: Nothing is logged. The monitor stays empty for generic_guardrail_api blocks.

Is this a known limitation for external guardrails, or is there a config I'm missing? Related to #23910, not sure if that PR covers this case.

Thanks

Motivation, pitch

I'm working on Ai gateway for a small company, I went here just to report the issue and saw the application.

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

Yes

Twitter / LinkedIn details

www.linkedin.com/in/sharif-derhem