8 views
-/https://github.com/berriai/litellm/issues/30512
GitHub · issue

#30512 [Feature]: Dynamically load Presidio supported entities from analyzer /supportedentities

  • State: open
  • Author: @alexhartuk
  • Labels: enhancement, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

When configuring a Presidio guardrail in the Admin UI, entity types should be loaded dynamically from the connected Presidio analyzer’s /supportedentities?language={lang} endpoint, merged with (or replacing) the static PiiEntityType enum.

This ensures the UI reflects:

Presidio version upgrades (e.g. new UK recognizers in 2.2+) Per-deployment recognizer registry overrides (RECOGNIZER_REGISTRY_CONF_FILE) Custom/ad-hoc recognizer entity types If the analyzer is unreachable, fall back to the static enum with a visible UI warning.

Proposed API change:

GET /guardrails/ui/add_guardrail_settings?presidio_analyzer_api_base=<url>&presidio_language=en Or a dedicated endpoint:

GET /guardrails/ui/presidio_supported_entities?analyzer_api_base=<url>&language=en UI should refetch entities when the admin enters/changes the Presidio analyzer URL in the guardrail form.

### Motivation, pitch

We run Presidio 2.2.362 as LiteLLM sidecars with a custom recognizer registry that enables UK entities (UK_PASSPORT, UK_POSTCODE, UK_VEHICLE_REGISTRATION) disabled in the …

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d19h5m48s ago — entered · #import:https:::github.com:berriai:litellm post #1866
Model omitted braces; inferred difficulty from issue scope and surface area.
The right issue is harder because it spans dashboard form behavior, new proxy/API integration, remote capability discovery, fallback handling, and user-visible error states. The left issue is primarily provider routing and embedding support/error-path coverage with narrower backend and test changes.
#0 of 0 · 31d18h5m12s ago — current · #import:https:::github.com:berriai:litellm post #2873
30512 requires coordinated backend, proxy integration, dashboard UI state, fallback behavior, and end-to-end testing, while 33221 is primarily a targeted request-translation/model-compatibility fix with narrower regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search