PolicyEngine / PolicyEngine/policyengine-uk-chat
Decide OTLP collector/export destination for UK Chat observability
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 16h 46m
- Merged PRs (30d)
- 2
Description
Context
PR #118 intentionally instruments UK Chat with policyengine-observability without configuring an external OTLP trace/metric destination. Structured observability logs currently go through the backend's normal stdout/logging path and are captured by Modal runtime logs.
Decision to make
Choose the platform-level OTLP export path for UK Chat observability data, including:
- Whether UK Chat should export OTel traces/metrics directly or through a shared collector.
- The target destination for traces and metrics.
- The environment/secrets needed for
OTEL_EXPORTER_OTLP_ENDPOINTand related auth/configuration. - Whether this should be configured per service or through a shared PolicyEngine observability deployment pattern.
Acceptance criteria
- Document the selected OTLP destination and collector strategy.
- Define the required environment variables/secrets for Modal deployments.
- Confirm how this fits with the broader PolicyEngine observability approach across services.
- Update UK Chat deployment configuration only after the destination decision is made.
Related: #118
Contributor 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.
Research direction
Start by reading PR #118 and the existing UK Chat Modal deployment configuration, then compare it with the broader PolicyEngine observability approach. Determine the collector strategy, OTLP destination, and required Modal environment variables or secrets; done means the decision is documented, its cross-service fit is confirmed, and deployment changes are specified for follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100