All configuration settings are passed as system properties. They can be edited with systemctl edit --full snw_01
Property | Default value | Description |
---|---|---|
|
|
log4j2 configuration location |
|
|
Relp application name |
|
localhost.localdomain |
Relp hostname |
|
|
API version |
|
|
API system parameter limit |
|
|
Tables to fetch |
|
Username for authenticating to the API |
|
|
Password for authenticating to the API |
|
|
|
Protocol to use when connecting to the API |
|
|
API host |
|
|
API port |
|
|
Statestore directory, relative to current working directory |
|
|
Fetch interval |
|
|
Is proxy enabled |
|
|
Proxy hostname |
|
|
Proxy port |
|
|
Does proxy require authentication |
|
Username for proxy authentication |
|
|
Password for proxy authentication |
|
|
|
Relp connection timeout, in milliseconds |
|
|
Relp transaction reading timeout, in milliseconds |
|
|
Relp transaction writing timeout, in milliseconds |
|
|
Relp connection retry interval, in milliseconds |
|
|
Relp target port |
|
|
Relp target address |
You can involve yourself with our project by opening an issue or submitting a pull request.
Contribution requirements:
-
All changes must be accompanied by a new or changed test. If you think testing is not required in your pull request, include a sufficient explanation as why you think so.
-
Security checks must pass
-
Pull requests must align with the principles and values of extreme programming.
-
Pull requests must follow the principles of Object Thinking and Elegant Objects (EO).
Read more in our Contributing Guideline.
Contributors must sign Teragrep Contributor License Agreement before a pull request is accepted to organization’s repositories.
You need to submit the CLA only once. After submitting the CLA you can contribute to all Teragrep’s repositories.