[Feature request]: Enable viewing raw response bodies for failing Uptime Monitors
Open
Product Area: Crons
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
Currently, when an Uptime Monitor check fails, users cannot see the full response body. This makes diagnosing API failures, HTML errors, or other server-side issues cumbersome.
### Solution Brainstorm
_No response_
### Product Area
Crons
Contributor guide
Research direction
Start by locating the Uptime Monitor implementation within the Crons product area and inspect how failed checks currently record or display responses. No files, tests, or entry points are named, so first identify the relevant backend and UI paths and their existing test coverage. Done means users can view the full response body for a failed monitor check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100