add PGHOST variable to env files so mk_postgres can use type local co… #792
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.
General information
This adds an optional
PGHOST
variable to the .env file ofmk_postgres.py
It answers my own question at the Checkmk forum.
This is useful when connecting to databases that only LISTEN on a socket and not on a TCP port. Set
PGHOST
to a directory where the socket.s.PGSQL.$PGPORT
is located and you can use connections that are configured inpg_hba.conf
as typelocal
.In theory you could also set
PGHOST
to the name of a remote host where a database resides. This might be useful in cases where you are not allowed to install a Checkmk agent on a database machine.here is an example for monitoring a GitLab PostgreSQL instance:
postgres.sql:
gitlabhq_production.env:
Also I deleted the mentioning of
export
in the description of .env files. It created the false appearance that you could export environment variables tomk_postgres.py
.