This page documents an earlier version of InfluxDB. InfluxDB v2.0 is the latest stable version.
InfluxDB writes log output, by default, to
Depending on your use case, this log information can be written to another location.
Running InfluxDB directly
If you run InfluxDB directly, using
influxd, all logs will be written to
You may redirect this log output as you would any output to
stderr like so:
Launched as a service
If InfluxDB was installed using a pre-built package, and then launched
as a service,
stderr is redirected to
/var/log/influxdb/influxd.log, and all log data will be written to
that file. You can override this location by setting the variable
STDERR in the file
Note: On macOS the logs, by default, are stored in the file
For example, if
all log data will be discarded. You can similarly direct output to
stdout by setting
STDOUT in the same file. Output to
/dev/null by default when InfluxDB is launched as a service.
InfluxDB must be restarted to pick up any changes to
Starting with version 1.0, InfluxDB on systemd systems will no longer
write files to
/var/log/influxdb by default, and will now use the
system configured default for logging (usually journald). On most
systems, the logs will be directed to the systemd journal and can be
accessed with the command:
sudo journalctl -u influxdb.service
Please consult the systemd journald documentation for configuring journald.
You can use logrotate to rotate the log files generated by InfluxDB on systems where logs are written to flat files.
If using the package install on a sysvinit system, the config file for logrotate is installed in
You can view the file here.
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.