Verbosity of verticapy

[wthomare]

Hello,

Due to production restriction, It will be great if the verbosity of vertica/verticapy will be tunable by a parameter and if the actual logs could be ingest by a standard python logger.

The parameter could be set in the connection and have those values :

• 0 (silent)
• 1 (warning)
• 2 (info)
• 3 (debug)

Does this parameter already exist and we missed it ?
Does such a feature is on a roadmap or can we help you ?

Wilfried Thomaré - MLOps

[afard]

Hello Wilfried,

Thanks for your valuable feedback.

If I understand it correctly, you are suggesting to add a capability to silence the displayed messages of all VerticaPy functions based on their importance, right?

There are currently a few configuration knobs like a print_info parameter to control printing of some information, but there is no comprehensive global knob to adjust the verbosity of all functions based on their level of importance. We like your suggestion and are planning to implement it in VerticaPy. Meanwhile, it would be great to learn more about the "production restriction" in your environment. It would be helpful if you can provide a few examples. This will help us to make sure your concerns will be addressed properly.

Best regards,
Arash

[oualib]

@wthomare can you please take time to give us more precision so we can implement a feature which can fit your needs?

[wthomare]

Hello,

Sorry for the delay. First of all, thanks for the tips with print_info. It's solved all our issues of message flooding in production.

But It doesn't change that It would be better if we can catch those logs into a real python logger instead of printed.
It will great for differents reasons :

• The performance monitoring with logstash (check the stability, variations, ... of some operations).
• Application monitoring when you have an error in production. Because prints are lost when a production instance is closed after a crash and not the logs.
• Formating the logs in accordance with the standart of our different companies
• With prints, you have no timestamps with the message and no synchronisation with the loggers already present in our treatment
• And all the over cons/pro of logger VS print ...

BS,
Wilfried

[afard]

Hello Wilfried,

I'm glad that your message related issues are resolved.
Thanks for your valuable suggestions. We are planning to modernize the logging mechanism of VerticaPy.

Best regards,
Arash

[oualib]

@afard do you think you can work on this?

[afard]

@afard do you think you can work on this?

@oualib, I should be able to work on this in the 2nd or the 3rd week of March.