John Spray 1787cf19e3 pageserver: write consumption metrics to S3 (#7200) ...

## Problem

The service that receives consumption metrics has lower availability
than S3. Writing metrics to S3 improves their availability.

Closes: https://github.com/neondatabase/cloud/issues/9824

## Summary of changes

- The same data as consumption metrics POST bodies is also compressed
and written to an S3 object with a timestamp-formatted path.
- Set `metric_collection_bucket` (same format as `remote_storage`
config) to configure the location to write to

2024-03-22 14:52:14 +00:00

..

benches

walredo benchmark: throughput-oriented rewrite (#7190)

2024-03-21 15:24:56 +01:00

client

pageserver, controller: improve secondary download APIs for large shards (#7131)

2024-03-15 19:45:58 +00:00

compaction

Minor improvements to tiered compaction (#7020)

2024-03-05 16:26:51 +01:00

ctl

pageserver: optimise disk io for vectored get (#6780)

2024-02-28 12:06:00 +00:00

pagebench

tokio-epoll-uring: use it for on-demand downloads (#6992)

2024-03-15 18:57:05 +00:00

src

pageserver: write consumption metrics to S3 (#7200)

2024-03-22 14:52:14 +00:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

build: make procfs linux only dependency (#7156)

2024-03-18 09:28:45 +00:00