SLO
Last updated
Was this helpful?
Last updated
Was this helpful?
The Grey Matter Service Level Objective (SLO) service is compatible with Postgres versions 10.x and 11.x only. For more information on the SLO service and using its API, see the .
The server certificate must have a CN that matches the hostname of the Postgres server. See for details.
To ensure that clients connect via SSL a pg_hba.conf
file must be configured accordingly.
Certificates and the pg_hba.conf
file must be volume mounted into the container and referenced via a Postgres startup command. The same configuration should be followed for production deployments.
Name
Type
Default
Description
GITHUB_ACCESS_KEY
String
""
OAuth token used to interact with GitHub via automated scripts
LOG_LEVEL
String
debug (dev), error (prod)
DROP_SCHEMA
Boolean
false
Controls whether or not the schema is dropped when DB connection is established. Use with extreme caution in production.
DATABASE_URI
String
none
Database connection URL. In production, replace the password string with a secret.
SSL_ENABLED
Boolean
false
Informs service to connect to Postgres via SSL
SSL_SERVER_CA
String
none
Path to CA or intermediate certificate (SSL_ENABLED=true
is required)
SSL_SERVER_CERT
String
none
Path to server certificate (SSL_ENABLED=true
is required)
SSL_SERVER_KEY
String
none
Path to server certificate private key (SSL_ENABLED=true
is required)
SERVICE_PORT
Number
1337
Port where gm-slo will listen (overridden to use 443 if SERVER_SSL_ENABLED=true
)
SERVICE_SSL_ENABLED
Boolean
false
Informs service to receive client connections over SSL only
SERVICE_SSL_CA
String
none
Path to client trust file (SERVICE_SSL_ENABLED=true
is required)
SERVICE_SSL_CERT
String
none
Path to client certificate (SERVICE_SSL_ENABLED=true
is required)
SERVICE_SSL_KEY
String
none
Path to client private key (SERVICE_SSL_ENABLED=true
is required)
Level of messages to log. debug (see for more)
Need help configuring SLOs? Contact us at .