mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-05 20:42:54 +00:00
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>
6 lines
163 B
Plaintext
6 lines
163 B
Plaintext
# sql_exporter config files generated from Jsonnet
|
|
etc/neon_collector.yml
|
|
etc/neon_collector_autoscaling.yml
|
|
etc/sql_exporter.yml
|
|
etc/sql_exporter_autoscaling.yml
|