mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-08 14:02:55 +00:00
fb0e2acb2f
## Problem When a pageserver is receiving high rates of requests, we don't have a good way to efficiently discover what the client's access pattern is. Closes: https://github.com/neondatabase/neon/issues/10275 ## Summary of changes - Add `/v1/tenant/x/timeline/y/page_trace?size_limit_bytes=...&time_limit_secs=...` API, which returns a binary buffer. - Add `pagectl page-trace` tool to decode and analyze the output. --------- Co-authored-by: Erik Grinaker <erik@neon.tech>
27 lines
720 B
TOML
27 lines
720 B
TOML
[package]
|
|
name = "pagectl"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
bincode.workspace = true
|
|
camino.workspace = true
|
|
clap = { workspace = true, features = ["string"] }
|
|
humantime.workspace = true
|
|
itertools.workspace = true
|
|
pageserver = { path = ".." }
|
|
pageserver_api.workspace = true
|
|
remote_storage = { path = "../../libs/remote_storage" }
|
|
postgres_ffi.workspace = true
|
|
thiserror.workspace = true
|
|
tokio.workspace = true
|
|
tokio-util.workspace = true
|
|
utils.workspace = true
|
|
svg_fmt.workspace = true
|
|
workspace_hack.workspace = true
|
|
serde_json.workspace = true
|