-
Notifications
You must be signed in to change notification settings - Fork 187
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.
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
Use influxdb-client as a python native logging handler that writes to InfluxDB #364
Comments
thanks for using our client. Every PR is welcome, so feel free to implement this feature and we will be happy to accept its. Regards |
Hi @bednar, happy to hear this. I'm not quite sure I understood the code structure right: |
Sounds good. |
Do you know when this will be ready? Now the logger writes to the console, I want it to write to a file so I can use code to search for errors. |
Hey, sorry for bringing this up and not doing anything for so long. As always life and important customers came in the way. Anyhow; I reserved some time next week to push a (working) first draft. |
@strom-und-spiele 👍 awesome news, thanks |
✨ Feature request
I'd like to use the
influxdb-client
with the python native logging module.⏮️ What happend so far
Four years ago there was an attempt to do this, however this project never really took off and seems to be incompatible with the latest version of influx (v2).
💡 Idea and reasoning
The goal would be to have a class within
influxdb-client
that can be passed as a handler tologging
. To me this seems reasonable as it centralizes logging, freeing the individual modules from "knowing" about influx and allowing to make decisions on how to use the log output depending on the context the module is used.If I'm missing something, I'd really like to hear about it.
🧑🏭 Work
I'd like to make this work for a project at my day job, so I have some resources to make this happen anyway. If you think it makes sense, I'll go the extra mile and integrate it directly into this repo.
The text was updated successfully, but these errors were encountered: