Skip to content

docs(prometheus): document managed batch and CheckBatchCost metrics - #711

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
litellm_batch_prometheus_docs
Open

docs(prometheus): document managed batch and CheckBatchCost metrics#711
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
litellm_batch_prometheus_docs

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

The managed batch / file lifecycle metrics and the CheckBatchCost poller metrics shipped in BerriAI/litellm#24691 (merged Mar 27, 2026), but they were never documented, so users asking for batch observability (BerriAI/litellm#35136) had no way to discover them.

Adds a "Managed Batch and File Metrics" section to docs/proxy/prometheus.md covering litellm_managed_batch_created_total, litellm_managed_file_created_total, litellm_managed_file_deleted_total, litellm_managed_file_size_bytes, litellm_managed_batch_duration_seconds, plus the poller health metrics litellm_check_batch_cost_last_run_timestamp, litellm_check_batch_cost_jobs_polled, litellm_check_batch_cost_jobs_processed_total and litellm_check_batch_cost_errors_total.

Label sets and enum values were read off the emitting code rather than the original PR body, so error_type is documented as the six values _record_error actually passes (invalid_model_id, invalid_unified_id, unmanaged_no_matching_deployment, deployment_not_found, provider_retrieval_error, cost_tracking_error), and file_type as input (upload, from managed_files.py) / output (batch output file, from check_batch_cost.py)

Validated with npm run build; no new warnings, and the ./managed_batches link resolves

Link to Devin session: https://app.devin.ai/sessions/84b2e8e5de3b47f6a1f01dc34ffca2f0

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview Jul 29, 2026 10:11pm

Request Review

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.

0 participants