mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[Migration #121.2] Implement LLM usage tracking and analytics #309

New Issue
Closed
opened 2026-02-04 02:35:55 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-04 02:35:55 +00:00
Owner
Copy Link

Parent EPIC: #121 - Backend Migration from Jarvis r1
Phase: 1 - LLM Abstraction Layer
Estimate: 1-2 days

Description

Migrate LLM usage tracking system for monitoring token usage, costs, and performance.

Source Files

  • jarvis/storage/models/llm_usage.py
  • jarvis/storage/repositories/llm_usage.py

Target Implementation

  • Create Prisma schema for LLM usage tracking
  • Implement usage repository
  • Add usage analytics endpoints
  • Create usage aggregation queries

Acceptance Criteria

  • Prisma schema for LLM usage
  • Usage tracking on all LLM calls
  • Analytics queries (by workspace, provider, model)
  • Cost calculation per provider
  • Unit tests (85% coverage)
**Parent EPIC:** #121 - Backend Migration from Jarvis r1 **Phase:** 1 - LLM Abstraction Layer **Estimate:** 1-2 days ## Description Migrate LLM usage tracking system for monitoring token usage, costs, and performance. ## Source Files - `jarvis/storage/models/llm_usage.py` - `jarvis/storage/repositories/llm_usage.py` ## Target Implementation - Create Prisma schema for LLM usage tracking - Implement usage repository - Add usage analytics endpoints - Create usage aggregation queries ## Acceptance Criteria - [ ] Prisma schema for LLM usage - [ ] Usage tracking on all LLM calls - [ ] Analytics queries (by workspace, provider, model) - [ ] Cost calculation per provider - [ ] Unit tests (85% coverage)
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-02-04 02:35:55 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label
Milestone
No items
No Milestone M4-LLM (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#309
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?