Erik Grinaker 06b45fd0fd utils/logging: add critical! macro and metric (#10641) ...

## Problem

We don't currently have good alerts for critical errors, e.g. data
loss/corruption.

Touches #10094.

## Summary of changes

Add a `critical!` macro and corresponding
`libmetrics_tracing_event_count{level="critical"}` metric. This will:

* Emit an `ERROR` log message with prefix `"CRITICAL:"` and a backtrace.
* Increment `libmetrics_tracing_event_count{level="critical"}`, and
indirectly `level="error"`.
* Trigger a pageable alert (via the metric above).
* In debug builds, panic the process.

I'll add uses of the macro separately.

2025-02-03 19:23:12 +00:00

..

benches

Remove unused allow's (#6760)

2024-02-14 18:16:05 +00:00

scripts

Use DATA_DIR instead of current workign directory in restore_from_wal script (#9729)

2024-11-18 11:55:38 +02:00

src

utils/logging: add critical! macro and metric (#10641)

2025-02-03 19:23:12 +00:00

tests

Remove sync postgres_backend, tidy up its split usage.

2023-03-09 20:45:56 +03:00

Cargo.toml

utils: add flamegraph for heap profiles (#10223)

2025-01-10 12:14:29 +00:00