feat: LLM Cost Tracking and Budgeting feature in passmark#41
Open
devhimanshuu wants to merge 1 commit intobug0inc:mainfrom
Open
feat: LLM Cost Tracking and Budgeting feature in passmark#41devhimanshuu wants to merge 1 commit intobug0inc:mainfrom
devhimanshuu wants to merge 1 commit intobug0inc:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🌟 Summary
Introduces an enterprise-grade LLM Cost Tracking & Budgeting system. This prevents "bill shock" by strictly monitoring API costs across all parallel test workers and halting execution if a user-defined budget is exceeded.
❓ Why is this needed?
AI-driven tests can accumulate high API costs rapidly, especially during loops or parallel test execution in CI/CD. Teams need strict, observable cost controls to confidently run Passmark in production pipelines without fear of runaway expenses.
🛠️ Key Features
maxCostPerRuntoconfigure(). If the budget is breached, it safely aborts the suite with aBudgetExceededError.INCRBYFLOAT) with a 24-hour TTL to precisely aggregate costs across all parallel Playwright workers, ensuring true global limits.pricingconfig option to define custom token rates (useful for enterprise gateways or self-hosted models).ai.usage.cost) to active OpenTelemetry traces for rich Datadog/Axiom dashboarding.passmark-cost-<pid>.jsonsummary in the uploads directory and logs the total cost upon process exit.💻 Usage Example