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

[Migration #121.5] Implement core OpenTelemetry infrastructure #312

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

Parent EPIC: #121 - Backend Migration from Jarvis r1
Phase: 3 - OpenTelemetry Infrastructure
Estimate: 2 days

Description

Migrate OpenTelemetry SDK configuration with OTLP exporter for distributed tracing.

Source Files

  • jarvis/core/telemetry.py

Target Implementation

  • Create apps/api/src/telemetry/ module
  • Implement OTLP exporter configuration
  • Add resource attributes (service name, version, etc.)
  • Configure trace sampling
  • Add context propagation

Acceptance Criteria

  • OpenTelemetry SDK configured
  • OTLP exporter to Jaeger/Zipkin
  • Resource attributes configured
  • Trace sampling configuration
  • Context propagation working
  • Environment-based configuration
  • Unit tests (85% coverage)
**Parent EPIC:** #121 - Backend Migration from Jarvis r1 **Phase:** 3 - OpenTelemetry Infrastructure **Estimate:** 2 days ## Description Migrate OpenTelemetry SDK configuration with OTLP exporter for distributed tracing. ## Source Files - `jarvis/core/telemetry.py` ## Target Implementation - Create `apps/api/src/telemetry/` module - Implement OTLP exporter configuration - Add resource attributes (service name, version, etc.) - Configure trace sampling - Add context propagation ## Acceptance Criteria - [ ] OpenTelemetry SDK configured - [ ] OTLP exporter to Jaeger/Zipkin - [ ] Resource attributes configured - [ ] Trace sampling configuration - [ ] Context propagation working - [ ] Environment-based configuration - [ ] Unit tests (85% coverage)
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-02-04 02:35:58 +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#312
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?