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

perf: MeterProvider with Prometheus scrape endpoint #205

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

Implement src/perf/_meter.py for metrics collection.

Metrics

  • stack_pipeline_duration_seconds{pipeline} — histogram
  • stack_step_duration_seconds{pipeline,step} — histogram
  • stack_step_rows_out{pipeline,step} — gauge
  • stack_step_memory_delta_mb{pipeline,step} — gauge
  • stack_cache_hits_total{pipeline} — counter
  • stack_cache_misses_total{pipeline} — counter
  • stack_system_rss_mb{service} — gauge
  • stack_system_cpu_percent{service} — gauge

Tasks

  • MeterProvider setup with OTLP gRPC exporter
  • /metrics endpoint via opentelemetry-exporter-prometheus (scrape target)
  • MockMeter no-op pattern matching MockTracer
  • Tests: verify metric recording and label dimensions
Implement `src/perf/_meter.py` for metrics collection. ## Metrics - `stack_pipeline_duration_seconds{pipeline}` — histogram - `stack_step_duration_seconds{pipeline,step}` — histogram - `stack_step_rows_out{pipeline,step}` — gauge - `stack_step_memory_delta_mb{pipeline,step}` — gauge - `stack_cache_hits_total{pipeline}` — counter - `stack_cache_misses_total{pipeline}` — counter - `stack_system_rss_mb{service}` — gauge - `stack_system_cpu_percent{service}` — gauge ## Tasks - [ ] `MeterProvider` setup with OTLP gRPC exporter - [ ] `/metrics` endpoint via `opentelemetry-exporter-prometheus` (scrape target) - [ ] MockMeter no-op pattern matching MockTracer - [ ] Tests: verify metric recording and label dimensions
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:04:24 +00:00
Author
Owner
Copy Link

Complete. _meter.py with MockMeter + MeterProvider was built in #203. Added 5 tests in test_meter.py:

  • Counter (add, verify cumulative value)
  • Histogram (record, verify count + sum)
  • UpDownCounter as gauge
  • Multiple instruments on one meter
  • create_meter mock dispatch

Note: OTel 1.40 uses set-once global provider — tests use provider.get_meter() directly to avoid global mutation conflicts.

✅ 5/5 passed, lint clean.

Complete. `_meter.py` with MockMeter + MeterProvider was built in #203. Added 5 tests in `test_meter.py`: - Counter (add, verify cumulative value) - Histogram (record, verify count + sum) - UpDownCounter as gauge - Multiple instruments on one meter - create_meter mock dispatch Note: OTel 1.40 uses set-once global provider — tests use provider.get_meter() directly to avoid global mutation conflicts. ✅ 5/5 passed, lint clean.
kert closed this issue 2026-03-25 00:04:24 +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#205
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?