Release reusable observability runtime version 2
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Begin with the package checks and release artifact inspection, then map the API v1 Flask, FastAPI, HTTPX, and Modal integrations to the explicitly owned runtimes. Review the Google Cloud deployment, authentication, dashboards, alerts, and rollback procedure. Done means the acceptance criteria pass, including fail-open behavior, restricted identities, verified resources and commands, and correlation, privacy, performance, and cost validation.
Written by the indexing model from the issue text.
Description
Summary
Release policyengine-observability 2.0 as a reusable runtime whose consumers choose their logging and OpenTelemetry destinations.
Scope
- Replace the version 1 global interface with explicitly owned runtimes.
- Provide failure-isolated Flask, FastAPI, HTTPX, process, and asynchronous context integration.
- Define provider-neutral log destination interfaces and optional Google Cloud implementations.
- Configure trace and metric OTLP exporters independently, with pluggable authentication.
- Maintain bounded per-destination queues, deadlines, sampling, redaction, and local diagnostics.
- Keep service-specific infrastructure, identity policy, attribute allowlists, and operations documentation in consumer repositories.
Acceptance criteria
- Package formatting, lint, typing, tests, coverage, and release artifact inspection pass.
- Logging and OpenTelemetry failures do not alter application responses or calculations.
- A failed or slow log destination does not block another destination or the application.
- The package contains no API v1 deployment configuration or consumer-specific authorization policy.
- Consumer integration is tracked in PolicyEngine/policyengine-api#3847 and PolicyEngine/policyengine-sim-api#685.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 7h 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policyengine-observability
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in PolicyEngine/policyengine-observability
Similar issues
-
python-version
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug javascript P2-medium python release:v3.1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
adrirubio/claude-deck#546 ·
Maintainers usually reply within 1 day
-
area: desktop area: website priority: P2 type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
appandflow/stim#3411 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 88/100
baptistehamon/lsapy#185 ·
Maintainers usually reply within 1 day