Migrate API v1 simulation services to centralized observability
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- google-cloud, python
- Domain
- backend-api-design, cloud, observability
Research direction
Start by locating the API v1 simulation entry, Modal gateway, executor, and batch workers named in the scope, then inspect their current Logfire and telemetry setup. Review the existing deployment configuration and service-level tests before changing the observability integration. Done means all participating services emit the version 2 schema, preserve allowlisted correlation metadata, contain no Logfire runtime path, and remain unaffected when telemetry fails.
Written by the indexing model from the issue text.
Description
Summary
Migrate the API v1 simulation entry, Modal gateway, executor, and batch workers to policyengine-observability 2.0 and central Google Cloud telemetry.
Scope
- Replace version 1 global helpers with runtime-bound operations and spans.
- Remove Logfire initialization, secrets, dependencies, and forced OpenTelemetry disablement.
- Carry allowlisted request and trace correlation metadata from entry to gateway to worker.
- Configure explicit service identity, environment, collector endpoint, Google project, and Workload Identity Federation credentials for approved API v1 applications.
- Add service-level failure-isolation tests.
- Keep other PolicyEngine applications outside this change.
Acceptance criteria
- Each participating service emits the version 2 structured log schema.
- Worker operations restore incoming correlation metadata without including simulation inputs or reform payloads.
- No Logfire runtime path remains in these services.
- Failed telemetry setup or export does not change simulation outcomes.
- Relevant formatting, lint, unit, integration, and deployment configuration checks pass.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 15h 3m
- Merged PRs (30d)
- 14
Getting set up
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-sim-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PolicyEngine/policyengine-sim-api#314 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PolicyEngine/policyengine-sim-api#679 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-sim-api#674 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/policyengine-sim-api#646 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
PolicyEngine/policyengine-sim-api#639 ·
Maintainers usually reply within 2 days
All issues in PolicyEngine/policyengine-sim-api
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pydantic/pydantic-ai#8863 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
run-llama/llama_index#23278 ·
Maintainers usually reply within 2 days
-
documentation from-review-extraction github-actions priority: low severity:nit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
LearningCircuit/local-deep-research#6946 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oracle/langchain-oracle#323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tenstorrent/tt-metal#58057 · 1 comment ·
Maintainers usually reply within 1 day