6 views
-/https://github.com/berriai/litellm/issues/30008
GitHub · issue

#30008 Custom redaction tags (keyword_redaction_tag, pattern_redaction_format) not working in v1.87.1

  • State: open
  • Author: @xrwang8

## Bug Description

Custom redaction tags (`keyword_redaction_tag` and `pattern_redaction_format`) configuration parameters are not working as documented in v1.87.1.

According to the [official documentation](https://docs.litellm.ai/docs/proxy/guardrails/litellm_content_filter#customizing-tags), these parameters should allow customizing the placeholder format for redacted content.

## Expected Behavior

When configured with: ```yaml keyword_redaction_tag: "***REDACTED***" pattern_redaction_format: "***{pattern_name}***" ```

Redacted content should use the custom placeholders.

## Actual Behavior

Configuration can be saved to database, but **runtime does not read these values**. Placeholders are fixed to default values: - Keywords → `[KEYWORD_REDACTED]` - Patterns → `[{pattern_name}_REDACTED]`

## Test Evidence

### Test 1: Custom keyword_redaction_tag ```bash curl -X POST "http://10.200.9.249:30090/guardrails" \ -H "Authorization: Bearer sk-1234" -H "Content-Type: application/json" \ -d '{ "guardrail": { "guardrail_name": "custom-tag-test", "litellm_params": { "guardrail": "litellm_content_filter", "mode": "pre_call", "default_on": true…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h22m29s ago — entered · #import:https:::github.com:berriai:litellm post #1709
The right issue is harder because it spans several proxy endpoints, request-model propagation, provider selection, and identifier transformation, requiring coordinated routing and regression testing across integrations. The left issue is comparatively localized to configuration flow and runtime placeholder handling.
#30008 is harder because it requires tracing configuration from persistence through runtime guardrail construction, correcting parameter propagation, and adding coverage for multiple formatting paths; #29340 is more localized to deployment-time UI routing and static fallback behavior.
Cross-platform native packaging requires coordinated build matrices, ABI compatibility, installation behavior, CI coverage, and fallback handling, while the other issue is comparatively localized to configuration propagation and runtime behavior.
The right issue is harder because it spans configuration persistence, runtime loading, and guardrail behavior across multiple execution paths, with compatibility and regression-testing risk. The left issue appears localized to endpoint construction and targeted coverage.
#0 of 0 · 31d18h22m52s ago — current · #import:https:::github.com:berriai:litellm post #2676
#14505 is harder because it requires cross-cutting security-context integration, trusted identity resolution, enforcement against conflicting inputs, provider-specific propagation, and broad regression coverage. #30008 is comparatively localized to configuration plumbing and runtime formatting behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search