mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-04 03:52:56 +00:00
cf7a596a15
There are quite a few benefits to this approach:
- Reduce config duplication
- The two sql_exporter configs were super similar with just a few
differences
- Pull SQL queries into standalone files
- That means we could run a SQL formatter on the file in the future
- It also means access to syntax highlighting
- In the future, run different queries for different PG versions
- This is relevant because right now, we have queries that are failing
on PG 17 due to catalog updates
Signed-off-by: Tristan Partin <tristan@neon.tech>
13 lines
242 B
Jsonnet
13 lines
242 B
Jsonnet
{
|
|
metric_name: 'wal_is_lost',
|
|
type: 'gauge',
|
|
help: 'Whether or not the replication slot wal_status is lost',
|
|
key_labels: [
|
|
'slot_name',
|
|
],
|
|
values: [
|
|
'wal_is_lost',
|
|
],
|
|
query: importstr 'sql_exporter/wal_is_lost.sql',
|
|
}
|