PolicyEngine / PolicyEngine/policyengine-api
Better logs to help diagnose the frequent 502 errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 22
Description
These 502 issues happen frequently:
Automatically resolved api.policyengine.org incident
Monitor: api.policyengine.org
Cause: Status 502
Length: 3 minutes
Checked URL: GET https://api.policyengine.org/
Response:
502 Server Error
See more
⚠️ Incident
🌐 Monitor
Incident started July 16th at 8:26:43 AM
But currently, there is not sufficient logging within the API to diagnose. This issue is about getting the logging in place.
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
No files, tests, or entry points are named in the issue. Start by tracing the API request path and existing logging around the reported 502 responses, then reproduce or inspect a failure; done when the logs contain enough request and error context to diagnose these incidents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100