Christian Schwarz 6ee84d985a impr(perf tracing): ability to correlate with page_service logs (#11398) ...

# Problem

Current perf tracing fields do not allow answering the question what a
specific Postgres backend was waiting for.

# Background

For Pageserver logs, we set the backend PID as the libpq
`application_name` on the compute side, and funnel that into the a
tracing field for the spans that emit to the global tracing subscriber.

# Solution

Funnel `application_name`, and the other fields that we use in the
logging spans, into the root span for perf tracing.

# Refs

- fixes https://github.com/neondatabase/neon/issues/11393
- stacked atop https://github.com/neondatabase/neon/pull/11433
- epic: https://github.com/neondatabase/neon/issues/9873

2025-04-04 15:13:54 +00:00

..

benches

buffered writer: add cancellation sensitivity (#11052)

2025-03-18 18:48:43 +00:00

client

feat(storcon): passthrough mark invisible and add tests (#11401)

2025-04-02 17:11:49 +00:00

compaction

utils: explicit OTEL export config and OTEL enablement via common entry point (#11139)

2025-03-12 11:07:49 +00:00

ctl

fix(pagectl/benches): scope context with debug tools (#11285)

2025-03-17 21:27:27 +00:00

pagebench

storcon: reuse reqwest http client (#11327)

2025-03-21 11:48:22 +00:00

src

impr(perf tracing): ability to correlate with page_service logs (#11398)

2025-04-04 15:13:54 +00:00

test_data

pageserver: add layer visibility calculation (#8511)

2024-08-01 09:25:35 +00:00

Cargo.toml

safekeeper: https for management API (#11171)

2025-03-14 11:41:22 +00:00