influxdata / influxdata/influxdb-java
It should be possible to not log errors in BatchProcessor
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 469
- PR merge metrics
- No merged PRs in 30d
Description
The current exception handler implementation doesn't make it possible to completely eliminate logging of errors. You can add an additional error handler, but LOG.log(Level.SEVERE, "Batch could not be sent. Data will be lost", t); will still be run no matter what. We would like to only log errors periodically so we don't completely spam our logs from all servers if InfluxDB goes down temporarily.
Could the default logging be implemented as a default exception handler that can be replaced or enhanced? I could turn off the logging, but that would mean disabling all logging from this class.
Another option would be to allow for turning down the log level of these errors, maybe to DEBUG or some other setting less than error.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating BatchProcessor and the exception handler containing the unconditional LOG.log(Level.SEVERE, "Batch could not be sent. Data will be lost", t) call. Review how additional error handlers and class logging are configured, then define completion as allowing this default error logging to be replaced, enhanced, or assigned a lower level without disabling unrelated logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100