feat(uptime): Include response capture in incident evidence#106491
Merged
feat(uptime): Include response capture in incident evidence#106491
Conversation
github-actions
bot
added
the
Scope: Backend
wedamija
force-pushed
the
danf/uptime-response-capture-consumer
branch
from
71a7826 to
0d26091
Compare
wedamija
force-pushed
the
danf/uptime-response-capture-incident
branch
from
fc7bd4a to
2e52e00
Compare
wedamija
force-pushed
the
danf/uptime-response-capture-consumer
branch
from
0d26091 to
cbba0cd
Compare
wedamija
force-pushed
the
danf/uptime-response-capture-incident
branch
from
2e52e00 to
c8d0631
Compare
wedamija
force-pushed
the
danf/uptime-response-capture-consumer
branch
from
a51ddc4 to
73b1000
Compare
wedamija
force-pushed
the
danf/uptime-response-capture-incident
branch
from
c8d0631 to
61361f1
Compare
Base automatically changed from
danf/uptime-response-capture-consumer
to
master
January 26, 2026 23:59
When an uptime incident is created, look up the most recent response capture from the failure sequence and include its ID in the occurrence evidence_data. This allows the API/UI to retrieve and display the captured response. Also adds generate_scheduled_check_times_ms utility for extrapolating scheduled check times forward or backward from a base time. ## Project Context This is part of the Uptime Response Capture feature - storing HTTP response data (body + headers) when downtime incidents are created to help users debug failures. PRs in this series: 1. sentry-kafka-schemas: Schema changes 2. uptime-checker: Response capture config and logic 3. sentry: Storage model (UptimeResponseCapture) 4. sentry: Config production and toggle helper 5. sentry: Consumer capture creation 6. sentry: Incident integration <-- this PR 7. sentry: API and UI
wedamija
force-pushed
the
danf/uptime-response-capture-incident
branch
from
61361f1 to
e3a87be
Compare
priscilawebdev
pushed a commit
that referenced
this pull request
Feb 2, 2026
When an uptime incident is created, look up the most recent response capture from the failure sequence and include its ID in the occurrence evidence_data. This allows the API/UI to retrieve and display the captured response. Also adds generate_scheduled_check_times_ms utility for extrapolating scheduled check times forward or backward from a base time. ## Project Context This is part of the Uptime Response Capture feature - storing HTTP response data (body + headers) when downtime incidents are created to help users debug failures. PRs in this series: 1. sentry-kafka-schemas: Schema changes 2. uptime-checker: Response capture config and logic 3. sentry: Storage model (UptimeResponseCapture) 4. sentry: Config production and toggle helper 5. sentry: Consumer capture creation 6. sentry: Incident integration <-- this PR 7. sentry: API and UI <!-- Describe your PR here. -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When an uptime incident is created, look up the most recent response capture from the failure sequence and include its ID in the occurrence evidence_data. This allows the API/UI to retrieve and display the captured response.
Also adds generate_scheduled_check_times_ms utility for extrapolating scheduled check times forward or backward from a base time.
Project Context
This is part of the Uptime Response Capture feature - storing HTTP response data (body + headers) when downtime incidents are created to help users debug failures.
PRs in this series: