mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-05 20:42:54 +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>
18 lines
711 B
Markdown
18 lines
711 B
Markdown
# Compute Configuration
|
|
|
|
These files are the configuration files for various other pieces of software
|
|
that will be running in the compute alongside Postgres.
|
|
|
|
## `sql_exporter`
|
|
|
|
### Adding a `sql_exporter` Metric
|
|
|
|
We use `sql_exporter` to export various metrics from Postgres. In order to add
|
|
a metric, you will need to create two files: a `libsonnet` and a `sql` file. You
|
|
will then import the `libsonnet` file in one of the collector files, and the
|
|
`sql` file will be imported in the `libsonnet` file.
|
|
|
|
In the event your statistic is an LSN, you may want to cast it to a `float8`
|
|
because Prometheus only supports floats. It's probably fine because `float8` can
|
|
store integers from `-2^53` to `+2^53` exactly.
|