Centralize API v1 observability in Google Cloud
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- api, cloud, observability
Research direction
Start at Flask API v1 application construction and follow the simulation dispatch path to understand the request lifecycle and correlation metadata flow. Then inspect the production and staging deployment configuration for service identity, environment, collector destination, and credentials; done means the stated acceptance checks pass without changing API responses or calculation behavior.
Written by the indexing model from the issue text.
Description
Summary
Integrate the Flask API v1 service with policyengine-observability 2.0 so requests produce centralized structured logs, traces, and bounded metrics in the policyengine-observability Google Cloud project.
Scope
- Configure an explicitly owned observability runtime during application construction.
- Instrument the Flask request lifecycle without route decorators.
- Propagate W3C trace context and
X-PolicyEngine-Request-Idthrough the API v1 simulation dispatch path. - Configure production and staging service identity, deployment environment, collector destination, and workload credentials.
- Prove API responses remain unchanged when observability setup or export fails.
- Preserve existing API contracts and calculation behavior.
Acceptance criteria
- API v1 request completion records use the version 2 schema.
- Simulation dispatch carries allowlisted correlation metadata only.
- Observability failures do not change successful responses or application exceptions.
- Production and staging deploy configuration names only the approved Cloud Run services and central destination.
- Relevant formatting, lint, unit, and contract checks pass.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 23
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-api
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
PolicyEngine/policyengine-api#3823 ·
Maintainers usually reply within 1 day
-
API v2: report validations as an append-only, provenance-keyed resource on reportsPossibly taken @anth-volk claimed this 19 days ago. Open
PolicyEngine/policyengine-api#3818 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/policyengine-api#3816 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-api#3814 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
PolicyEngine/policyengine-api#3811 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/policyengine-api
Similar issues
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12887 · 1 comment ·
Maintainers usually reply within 1 day
-
area: desktop platform: macos priority: p3 status: ready type: enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
use-agent-os/agent-os#3484 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
open-telemetry/opentelemetry-python-contrib#5113 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/docs#6255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day