Proposal:
Add a JSON formatted log option to the configuration options.
Current behavior:
InfluxDB v2.x had an “auto” format mode which cannot be altered and it is supposed to detect when log output should be JSON, but the variability is not useful.
Desired behavior:
InfluxDB 1.x included an option for JSON formatted logs. Users previously used that format and then used a simple logstash configuration to send to ELK as JSON, the fields were then extracted without need for any preprocessing. The loss of a JSON formatted log means users now need to start pre-parsing the logs. When logging Flux as well there is JSON formatted data in some log statements so not sure why overall JSON format was lost, it feels like a backward step.
danxmoran
commented
3 years ago
Proposal: Add a JSON formatted log option to the configuration options.
Current behavior: InfluxDB v2.x had an “auto” format mode which cannot be altered and it is supposed to detect when log output should be JSON, but the variability is not useful.
Desired behavior: InfluxDB 1.x included an option for JSON formatted logs. Users previously used that format and then used a simple logstash configuration to send to ELK as JSON, the fields were then extracted without need for any preprocessing. The loss of a JSON formatted log means users now need to start pre-parsing the logs. When logging Flux as well there is JSON formatted data in some log statements so not sure why overall JSON format was lost, it feels like a backward step.