influxdata / influxdata/influxdb
Regression: JSON logging output format
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the configuration and logging implementation, then compare the current InfluxDB v2.x auto format with the prior InfluxDB 1.x JSON option. Done means users can select JSON-formatted logs through configuration and consume structured fields without preprocessing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100