Repository navigation
feat(metrics): make the listener address configurable - #59
Merged
Merged
Conversation
psteinroe
added a commit
that referenced
this pull request
Oct 15, 2026
`just install-tools` and `just upgrade-tools` now install taplo with `cargo install taplo-cli --locked` instead of `cargo binstall`. `taplo-cli` doesn't publish binstall metadata, so `cargo binstall` relied on the third-party quickinstall binary host, which now returns `402 Payment Required`. When that happens, binstall falls back to `cargo install` without `--locked`, which pulls in `uuid 1.28`. That needs rustc 1.89, but this repo pins 1.88. Taplo's own docs recommend `--locked` for this reason. I checked that `cargo install taplo-cli --locked` builds taplo 0.10.0 on rustc 1.88. `cargo-binstall` was only installed to fetch taplo, so it's no longer part of these recipes. CI already moved to taplo's release binaries in #59.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Prometheus exporter always listened on
[::]:9000. You can now setPGSTREAM_METRICS_ADDRto use a different address. The default stays the same. If the value isn't a valid socket address, startup fails with a configuration error that names the variable.This lets several instances share one host network, for example containers run with
--network host. A fixed port 9000 collides between instances, and with other local services that also default to 9000, such as S3-compatible gateways. Existing deployments that don't set the variable behave as before.The new setting is documented in
docs/reference/configuration.md. Unit tests cover the default, an override, and an invalid value.