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

perf: TracerProvider setup with MockTracer/MockSpan no-ops #204

New Issue
Closed
opened 2026-03-24 23:50:06 +00:00 by kert · 2 comments
kert commented 2026-03-24 23:50:06 +00:00
Owner
Copy Link

Implement src/perf/_tracer.py following marimo _tracer.py pattern.

Tasks

  • MockSpan with no-op set_attribute(), set_status(), __enter__/__exit__
  • MockTracer with no-op start_as_current_span()
  • create_tracer(name) — returns real OTel tracer when STACK_TELEMETRY=true, MockTracer otherwise
  • Lazy OTel imports — opentelemetry only imported when telemetry is enabled
  • Two named tracers: pipeline_tracer = create_tracer("stack.pipeline"), api_tracer = create_tracer("stack.api")
  • _enabled() reads STACK_TELEMETRY env var and stack.toml [telemetry].enabled
  • Tests: verify MockTracer when disabled, real tracer when enabled
Implement `src/perf/_tracer.py` following marimo `_tracer.py` pattern. ## Tasks - [ ] `MockSpan` with no-op `set_attribute()`, `set_status()`, `__enter__`/`__exit__` - [ ] `MockTracer` with no-op `start_as_current_span()` - [ ] `create_tracer(name)` — returns real OTel tracer when `STACK_TELEMETRY=true`, MockTracer otherwise - [ ] Lazy OTel imports — `opentelemetry` only imported when telemetry is enabled - [ ] Two named tracers: `pipeline_tracer = create_tracer("stack.pipeline")`, `api_tracer = create_tracer("stack.api")` - [ ] `_enabled()` reads `STACK_TELEMETRY` env var and `stack.toml [telemetry].enabled` - [ ] Tests: verify MockTracer when disabled, real tracer when enabled
kert added this to the P26: Pipeline Telemetry — OTel instrumentation, perf module, Grafana dashboards milestone 2026-03-24 23:50:06 +00:00
kert commented 2026-03-25 00:01:18 +00:00
Author
Owner
Copy Link

Starting work. Core MockTracer/MockSpan and TracerProvider setup already exist from #203. Remaining:

  • Tests with real OTel provider (STACK_TELEMETRY=true)
  • Verify span creation, attribute recording, context propagation
  • Verify OTLP fallback to FileExporter when collector unreachable
Starting work. Core MockTracer/MockSpan and TracerProvider setup already exist from #203. Remaining: - Tests with real OTel provider (STACK_TELEMETRY=true) - Verify span creation, attribute recording, context propagation - Verify OTLP fallback to FileExporter when collector unreachable
kert commented 2026-03-25 00:04:23 +00:00
Author
Owner
Copy Link

Complete. _tracer.py with MockTracer/MockSpan + TracerProvider was built in #203. Added 9 deep tests in test_tracer.py:

  • Real span creation with attributes
  • Nested parent→child→grandchild span hierarchy
  • Exception recording on spans
  • Status code propagation
  • Timing (end > start)
  • create_tracer mock vs real dispatch
  • Endpoint resolution (env override, config fallback)

✅ 9/9 passed, lint clean.

Complete. `_tracer.py` with MockTracer/MockSpan + TracerProvider was built in #203. Added 9 deep tests in `test_tracer.py`: - Real span creation with attributes - Nested parent→child→grandchild span hierarchy - Exception recording on spans - Status code propagation - Timing (end > start) - create_tracer mock vs real dispatch - Endpoint resolution (env override, config fallback) ✅ 9/9 passed, lint clean.
kert closed this issue 2026-03-25 00:04:23 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label
Milestone
No items
No Milestone P26: Pipeline Telemetry — OTel instrumentation, perf module, Grafana dashboards
Projects
Clear projects
No project Skin Subs
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#204
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?