Skip to content

Add HTTP-HEAD-RSR per miner and per allocator #505

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NikolasHaimerl opened this issue Mar 21, 2025 · 1 comment
Open

Add HTTP-HEAD-RSR per miner and per allocator #505

NikolasHaimerl opened this issue Mar 21, 2025 · 1 comment
Assignees

Comments

@NikolasHaimerl
Copy link
Contributor

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_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)

@bajtos bajtos changed the title Missing successful_http_head column Add successful_http_head for per-miner and per-allocator stats Mar 24, 2025
@bajtos bajtos changed the title Add successful_http_head for per-miner and per-allocator stats HTTP-HEAD-RSR per miner and per allocator Mar 24, 2025
@bajtos bajtos changed the title HTTP-HEAD-RSR per miner and per allocator Add HTTP-HEAD-RSR per miner and per allocator Mar 24, 2025
@bajtos
Copy link
Member

bajtos commented Mar 24, 2025

I reworded the issue title to describe the impact of the desired changes at higher level.

@NikolasHaimerl NikolasHaimerl self-assigned this Apr 1, 2025
@NikolasHaimerl NikolasHaimerl moved this to 📥 next in Space Meridian Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📥 next
Development

No branches or pull requests

2 participants