mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-15 17:32:56 +00:00
ea3e1b51ec
We don't know how our s3 remote_storage is performing, or if it's blocking the shutdown. Well, for sampling reasons, we will not really know even after this PR. Add metrics: - align remote_storage metrics towards #4813 goals - histogram `remote_storage_s3_request_seconds{request_type=(get_object|put_object|delete_object|list_objects), result=(ok|err|cancelled)}` - histogram `remote_storage_s3_wait_seconds{request_type=(same kinds)}` - counter `remote_storage_s3_cancelled_waits_total{request_type=(same kinds)}` Follow-up work: - After release, remove the old metrics, migrate dashboards Histogram buckets are rough guesses, need to be tuned. In pageserver we have a download timeout of 120s, so I think the 100s bucket is quite nice.
32 lines
820 B
TOML
32 lines
820 B
TOML
[package]
|
|
name = "remote_storage"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
async-trait.workspace = true
|
|
once_cell.workspace = true
|
|
aws-smithy-http.workspace = true
|
|
aws-types.workspace = true
|
|
aws-config.workspace = true
|
|
aws-sdk-s3.workspace = true
|
|
aws-credential-types.workspace = true
|
|
hyper = { workspace = true, features = ["stream"] }
|
|
serde.workspace = true
|
|
serde_json.workspace = true
|
|
tokio = { workspace = true, features = ["sync", "fs", "io-util"] }
|
|
tokio-util.workspace = true
|
|
toml_edit.workspace = true
|
|
tracing.workspace = true
|
|
scopeguard.workspace = true
|
|
metrics.workspace = true
|
|
utils.workspace = true
|
|
pin-project-lite.workspace = true
|
|
workspace_hack.workspace = true
|
|
|
|
[dev-dependencies]
|
|
tempfile.workspace = true
|
|
test-context.workspace = true
|