Litellm fix json serialize alreting 2 #15741
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Fix Redis serialization error in SlackAlerting outage alerts
Relevant issues
Fixes LIT-1291
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/
directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit
Type
🐛 Bug Fix
Changes
Problem
When Vertex AI requests timeout (408 errors), LiteLLM attempts to cache outage alert data but fails with:
This occurs because
ProviderRegionOutageModel.deployment_ids
is a Pythonset
object, which cannot be JSON serialized for Redis storage.Solution
Added two helper methods to handle set/list conversion:
_prepare_outage_value_for_cache()
: Converts sets to lists before caching_restore_outage_value_from_cache()
: Converts lists back to sets after retrievalChanges Made
SlackAlerting
class for set/list conversionregion_outage_alerts()
method to use helper methods for cachingoutage_alerts()
method to use helper methods for caching