Skip to content

Reduce logging level of batch processor disposition to DEBUG #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
karel-rehor opened this issue Sep 10, 2024 · 0 comments · Fixed by #111
Closed

Reduce logging level of batch processor disposition to DEBUG #110

karel-rehor opened this issue Sep 10, 2024 · 0 comments · Fixed by #111
Assignees
@karel-rehor
Milestone
0.9.0

Comments

@karel-rehor
Copy link
Contributor

karel-rehor commented Sep 10, 2024 •
edited
Loading

Use Case

see EAR 5482

Expected behavior

log messages should not clutter the log with extraneous information

Actual behavior

Quote from EAR:

Customer is reporting cluttered logs due to the following INFO message produced by the client write_api:

2024-09-08 19:14:16,198 INFO write_api.py:569 the batching processor was disposed

Additional info

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karel-rehor karel-rehor

Labels
None yet
Projects
None yet
Milestone
0.9.0
Development

Successfully merging a pull request may close this issue.

fix: #110 - set message 'processor was disposed' to level debug. InfluxCommunity/influxdb3-python
2 participants
@bednar @karel-rehor