tideways-daemon Configuration Reference
The Tideways daemon usually does not require additional manual configuration by you. The following options are configurable:
|
Changes the transmitted hostname from the system hostname to a custom defined one. It defaults to the server name, if possible the fully qualified server name. On Docker Containers the Container ID is appended to the hostname for de-duplication. |
|
Log more information into the logfile. |
|
points to the logfile that should be used. The daemons init scripts use /var/log/tideways/daemon.log by default. |
|
Dry run mode not sending the data, for example to log which data will be sending. |
|
Can be used to check what data is sent to Tideways if you want to control the privacy settings. |
|
Toggles the environment this server is automatically registered in when first connecting to the Profiler. Defaults to "production". You can alternatively use the TIDEWAYS_ENVIRONMENT environment variable. |
|
Show version of the daemon and quit. |
|
Points to a PID file used to cleanup sockets on startup. |
|
Change location of the default UNIX Socket or switch to TCP/IP (Not recommended!) |
|
Change UDP address and port (Not recommended!) |
|
Do not verify the peer’s certificate (Not recommended!) |
|
Manually provide public part of the server’s certificate. Only to be used in combination with collection proxies. |
|
If outgoing traffic requires a proxy, use this flag to pass a |
|
disables the collection of Load, CPU, Memory, Network and disk metrics that are stored on each trace. |
|
Integration of statsD network daemon, setting |
|
Integration with Datadog daemon, setting to |
You can add flags to the startup of the daemon service by adding a file /etc/default/tideways-daemon
with the variable TIDEWAYS_DAEMON_EXTRA=""
defined with the flags of your choice.
TIDEWAYS_DAEMON_EXTRA="--hostname=myserver"
If you want to change the location of the log file please use TIDEWAYS_DAEMON_LOGFILE
.
TIDEWAYS_DAEMON_LOGFILE="/var/log/tideways.log"
You can change the configured Tideways environment that the daemon is running:
TIDEWAYS_ENVIRONMENT=staging<br>
How can I troubleshoot the daemon?
There is a logfile in /var/log/tideways/daemon.log
if you are using the Ubuntu package or the tarball and invoke install.sh
.
Maintenance
You should make sure the directory /var/log/tideways
is added to log rotation, especially when you enable the --debug
flag.
The tarball install script, Ubuntu/Debian and RPM packages do this by default by putting a rotation config file into /etc/logrotate.d/
.