You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Missing successful_http_head column in daily_client_retrieval_stats table
Issue Description
The daily_client_retrieval_stats and daily_allocator_retrieval_stats tables are missing the successful_http_head columns that are needed for tracking HEAD RSR metrics. As noted in the discussion, we already shipped HEAD RSR and per-client-RSR independently, but didn't implement the third piece combining these components.
Current State
Currently, the table structure includes:
day (date)
client_id (text)
total (integer)
successful (integer)
successful_http (integer)
But is missing:
successful_http_head (integer)
Proposed Solution
Add the successful_http_head column to the daily_client_retrieval_statsdaily_allocator_retrieval_stats table to properly track HEAD request metrics. This will complete the integration between the HEAD RSR and per-client-RSR features.
Missing
successful_http_head
column in daily_client_retrieval_stats tableIssue Description
The
daily_client_retrieval_stats
anddaily_allocator_retrieval_stats
tables are missing thesuccessful_http_head
columns that are needed for tracking HEAD RSR metrics. As noted in the discussion, we already shipped HEAD RSR and per-client-RSR independently, but didn't implement the third piece combining these components.Current State
Currently, the table structure includes:
day
(date)client_id
(text)total
(integer)successful
(integer)successful_http
(integer)But is missing:
successful_http_head
(integer)Proposed Solution
Add the
successful_http_head
column to thedaily_client_retrieval_stats
daily_allocator_retrieval_stats
table to properly track HEAD request metrics. This will complete the integration between the HEAD RSR and per-client-RSR features.Originally posted by @bajtos in #503 (comment)
The text was updated successfully, but these errors were encountered: