influxdata
influxdb ignores logging "level" configuration
Steps to reproduce:
- Install influxdb 1.7.10 release 1(centos 7)
- Configure logging section
- Watch for rsyslog logs
Expected behavior: As in documentation https://docs.influxdata.com/influxdb/v1.7/administration/config#logging-settings level = "error" The log level to be emitted. Valid values are error, warn, info(default), and debug. Logs that are equal to, or above, the specified level will be emitted.
Actual behavior: with level "error" configured we are still seeing level 6 messages (info) influxd[21052]: ts=2020-03-11T08:57:27.136522Z lvl=info msg="Dropping point" log_id=0LUC5WhG000 service=collectd name=snmp_value error="NaN is an unsupported value for field value"
Environment info:
- System info: Linux 3.10.0-1062.4.1.el7.x86_64 x86_64
- InfluxDB version: InfluxDB v1.7.10 (git: 1.7 f46f63d4e2d9684a2dd716594ab609ccd32f0a5b)
Config: [logging] format = "auto" level = "error" suppress-logo = true
@alexiff thanks for opening this. I wonder if the level in the log msg field isn't the same as the level in the config.
Based on this line: https://github.com/influxdata/influxdb/blob/281c08ec50834e0bbfcb3f982b4938bdc02733f7/models/points.go#L1314
that might be what's happening.
@russorat You want to say that this is an error message but influx marks it as "info"? If yes then it's another bug? Also other messages that are clearly(from my point of view) "info" level are still passed : ts=2020-03-12T21:40:52.712904Z lvl=info msg="Cache snapshot (end)" log_id=0LUC5WhG000 engine=tsm1 trace_id=0LWAw8YG000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=1247.205ms
Don't know if this issue is still active but I observed the same issue on v1.8.10 (despite setting log level to "warn", info logs are still outputted)
Seeing this on v1.7.9 as well, but with level set to debug. Only info logs are emitted.
On startup, InfluxDB prints the log level it is running
Look on StdErr for the log line starting configured logger which will show the level. If you don't see the level you think you specified, perhaps an environment variable or command line parameter or incorrect config file is setting the level. Let us know what you see, @shrx
// If there was an error on startup when creating the logger, output it now.
if logErr != nil {
cmd.Logger.Error("Unable to configure logger", zap.Error(logErr))
} else {
logger.New(cmd.Stderr).Info("configured logger", zap.String("format", config.Logging.Format), zap.String("level", config.Logging.Level.String()))
}
@davidby-influx thanks for reaching out. After setting logger level to error in the configuration and restarting influxdb service (still on 1.11.8):
Nov 26 23:19:25 raspberrypi influxd-systemd-start.sh[183749]: Merging with configuration at: /etc/influxdb/influxdb.conf
Nov 26 23:19:26 raspberrypi influxd-systemd-start.sh[183747]: ts=2025-11-26T22:19:26.059982Z lvl=info msg="configured logger" log_id=0~SZqavl000 format=auto level=error
Nov 26 23:19:26 raspberrypi influxd-systemd-start.sh[183768]: Merging with configuration at: /etc/influxdb/influxdb.conf
Nov 26 23:19:27 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 1 attempts...
Nov 26 23:19:29 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 2 attempts...
Nov 26 23:19:30 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 3 attempts...
Nov 26 23:19:32 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 4 attempts...
Nov 26 23:19:33 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 5 attempts...
Nov 26 23:19:34 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 6 attempts...
Nov 26 23:19:36 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 7 attempts...
Nov 26 23:19:37 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 8 attempts...
Nov 26 23:19:40 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 9 attempts...
Nov 26 23:19:42 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 10 attempts...
Nov 26 23:19:43 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 11 attempts...
Nov 26 23:19:44 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 12 attempts...
Nov 26 23:19:47 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 13 attempts...
Nov 26 23:19:49 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 14 attempts...
Nov 26 23:19:50 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 15 attempts...
Nov 26 23:19:51 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 16 attempts...
Nov 26 23:19:52 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 17 attempts...
Nov 26 23:19:53 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 18 attempts...
Nov 26 23:19:54 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 19 attempts...
Nov 26 23:19:55 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 20 attempts...
Nov 26 23:19:56 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB API unavailable after 21 attempts...
Nov 26 23:19:58 raspberrypi influxd-systemd-start.sh[183747]: [httpd] ::1 - - [26/Nov/2025:23:19:58 +0100] "GET /health HTTP/1.1" 200 108 "-" "curl/7.74.0" 0adb6d3f-cb16-11f0-8001-b827ebe3b8cb 646148
Nov 26 23:19:59 raspberrypi influxd-systemd-start.sh[183714]: InfluxDB started
Nov 26 23:20:01 raspberrypi systemd[1]: Started influxdb.service - InfluxDB is an open-source, distributed, time series database.
Nov 26 23:20:02 raspberrypi influxd-systemd-start.sh[183747]: [httpd] XXX.XXX.XXX.XXX - kanta [26/Nov/2025:23:20:02 +0100] "POST /write?db=home HTTP/1.1 " 204 0 "-" "curl/7.88.1" 0d54260b-cb16-11f0-8002-b82>
Nov 26 23:20:03 raspberrypi influxd-systemd-start.sh[183747]: [httpd] XXX.XXX.XXX.XXX - kanta [26/Nov/2025:23:20:03 +0100] "POST /write?db=home HTTP/1.1 " 204 0 "-" "curl/7.88.1" 0e3d2d52-cb16-11f0-8003-b82>
Nov 26 23:20:10 raspberrypi influxd-systemd-start.sh[183747]: [httpd] 127.0.0.1 - telegraf [26/Nov/2025:23:20:10 +0100] "POST /write?db=home HTTP/1.1 " 204 0 "-" "Telegraf/1.34.4 Go/1.24.3" 121
the configured log level is correctly printed, but does this look ok? to me it's much too verbose, and there is no indication of the individual message log levels.
lvl=info msg="configured logger" log_id=0~SZqavl000 format=auto level=error
You are running with the log level set to error and the message telling you that is level info (that should be the last info level message you see, because they are suppressed at log level error after this point in start-up). If you log at debug level (the most verbose), even more information is available by setting trace-logging-enabled
The httpd messages are separate from the server logs, and do not follow the log levels; you can control them with:
Many users write them to a different log stream than the server logs, which are more useful for debugging problems.
Another log which is unrelated to log levels is query-log-enabled