RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[ClickHouse] Log metrics for Prometheus HTTP handler endpoints

Request to ensure that Prometheus HTTP handler endpoints reliably log metrics for rows and bytes during inserts and selects to improve monitoring.

Original Source

@@JTCunning | 0 pts | 3/13/2026

### Company or project name N/A ### Describe what's wrong Prometheus HTTP handler endpoints do not create (or do not reliably create) entries in `system.query_log` with the expected row/byte metrics: - **Remote write** (`/write`): Requests that insert time series data do not produce a `QueryFinish` row with `written_rows` or `written_bytes`. - **Remote read** (`/read`): Requests that read time series do not produce a `QueryFinish` row with `read_rows` or `read_bytes`. - **Query API** (`/api/v1/query`): Requests do not reliably appear in `system.query_log` with `read_rows > 0` and `read_bytes > 0` in a way that integration tests can assert (count-based). So either they are not logged, or the logged entries do not have read metrics set as expected. - **Query range API** (`/api/v1/query_range`): Same as Query API — integration tests that expect one additional `QueryFinish` row with `read_rows > 0` and `read_bytes > 0` after a request fail. Additionally, passing `query_id` as a URL para

Discussion

Loading comments...