Skip to content

fix(mavvrik): advance metricsMarker after successful upload - #30966

Closed
pghuge-cloudwiz wants to merge 4 commits into
BerriAI:litellm_internal_stagingfrom
cloudwizio:fix/mavvrik-metrics-marker-v2
Closed

fix(mavvrik): advance metricsMarker after successful upload#30966
pghuge-cloudwiz wants to merge 4 commits into
BerriAI:litellm_internal_stagingfrom
cloudwizio:fix/mavvrik-metrics-marker-v2

Conversation

@pghuge-cloudwiz

@pghuge-cloudwiz pghuge-cloudwiz commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Superseded by #31068 which is based on the latest litellm_internal_staging tip with only our two fixes (no unrelated commits).

Without this PATCH call the catch-up logic in MavvrikFocusLogger
re-exports the same dates on every daily run.
@codecov

codecov Bot commented Jun 22, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 75.00000% with 4 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...integrations/mavvrik_focus/mavvrik_focus_logger.py 20.00% 4 Missing ⚠️

📢 Thoughts on this report? Let us know!

When "mavvrik" is in litellm.callbacks as a string, the logger is
instantiated lazily on the first LLM call. init_mavvrik_focus_background_job
runs at startup before any LLM call, so it found no MavvrikFocusLogger
instance and silently skipped scheduling the daily export job.

Fix: if no instance is found but "mavvrik" is in litellm.callbacks,
call _init_custom_logger_compatible_class to force instantiation before
the scheduler job is registered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant