tideways-daemon Configuration Reference

The Tideways daemon usually does not require additional manual configuration by you. The following options are configurable:

  • --hostname Changes the transmitted hostname from the system hostname to a custom defined one.
  • --debug Log more information into the logfile.
  • --log points to the logfile that should be used. The daemons init scripts use /var/log/tideways/daemon.log by default.
  • --dryrunDry run mode not sending the data, for example to log which data will be sending.
  • --log-outgoing Can be used to check what data is sent to Tideways if you want to control the privacy settings.
  • --env Toggles the environment this server is automatically registered in when first connecting to the Profiler. Defaults to "production".
  • --version Show version of the daemon and quit.
  • --pidfile Points to a PID file used to cleanup sockets on startup.
  • --address Change location of the default UNIX Socket or switch to TCP/IP (Not recommended!)
  • --udp Change UDP address and port (Not recommended!)
  • --insecure Do not verify the peer's certificate (Not recommended!)
  • --server-cert Manually provide public part of the server's certificate. Only to be used in combination with collection proxies.
  • --proxy If outgoing traffic requires a proxy, use this flag to pass a host:port combination pointing to the proxy. Using proxy with authentification adduser:pass in the URL, for example --proxy=http://user:[email protected]:port.
  • --disable-server-metrics disables the collection of Load, CPU, Memory, Network and disk metrics that are stored on each trace.
  • --statsd Integration of statsD network daemon, setting ip:port sends data to StatsD service running on this ip and port.
  • --dogstatsd Integration with Datadog daemon, setting to ip:port sends data to a datadog-agent using the DogstatsD protocol.

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.


If you want to change the location of the log file please use TIDEWAYS_DAEMON_LOGFILE.


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.


You should make sure the directory /var/log/tideways is added to logrotation, 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/.

Using a Collection Proxy

A collection proxy would listen for data coming from multiple daemons and after aggregation and resampling sends them to the Tideways backend. In order to configure a daemon to work with a proxy, the --server flag should be provided, with the address of the proxy (its hostname in a private network) as value. Because the daemon sends the data via HTTPS, if the proxy is running on a self-signed certificate, it's possible to configure daemon to trust the certificate by pointing --server-cert to the public part of the certificate (typically a .crt file). One could also add the certificate to import the certificate and make it trusted across the OS, e.g. in a debian-based system this could be achieved by copying the public certificate file (not private key) to /usr/local/share/ca-certificates and then running sudo update-ca-certificates.

Still need help? Write [email protected] Write [email protected]