Move some debug logging to trace level

[Jasperav]

My logs are overflowed with meilisearch logging. I think a lot of logging should be done at trace level rather than the debug level. Take a look for example:

2022-11-13T19:21:17.360870Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Found bundle for host: 0x6000030882a0 [serially]
2022-11-13T19:21:17.360890Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Can not multiplex, even if we wanted to
2022-11-13T19:21:17.360913Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Re-using existing connection #0 with host 127.0.0.1
2022-11-13T19:21:17.360931Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Connected to 127.0.0.1 (127.0.0.1) port 7700 (#0)
2022-11-13T19:21:17.360981Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: We are completely uploaded and fine
2022-11-13T19:21:17.362746Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Mark bundle as not supporting multiuse
2022-11-13T19:21:17.362898Z DEBUG send_async{method=POST uri=http://127.0.0.1:7700/indexes/users/search}:handler{id=0}: isahc::handler: Connection #0 to host 127.0.0.1 left intact

This is what is logged when I try to update a field. I would expect at most 1/2 lines, not 7.

[gmourier]

Hi @Jasperav 👋

What do you expect from the debug level? Do you use it for any particular reason?

Thanks!

[Jasperav]

Hey @gmourier. I would expect debug level is showing me logging which helps me tracing back bugs. I think all the logs that I mentioned in this ticket, are not supporting me in any way and should be moved to the trace level. The current logging is really for internal use only (e.g. Found bundle for host: 0x6000030882a0 [serially], what can clients do with this information?)

I was hoping I would just see things like the HTTP return status code from Meili. If for any reason the HTTP return status code would be wrong, I could just turn on trace and see more logging. Now the logs are polluting my console.

[Jasperav]

@gmourier Just a headsup that I am still hoping some logs will be moved, this is my Github Actions logging after I queried meilisearch for 3/4 times. It is not really nice to search for my bug between al those logs which just eats disk space and isn't helpful.

[gmourier]

Hi @Jasperav 👋

Thanks for the follow-up.

What do you mean by "tracking back bugs"? If you want to reduce the logs, you could just use INFO. I guess that's not enough for your use case, I'd like to know more.

Thanks!

[Jasperav]

@gmourier I had a bug in my code which was catched by the CI. When I downloaded the logs, I was seeing these Meili logs everywhere. I have debug statements everywhere in my code which helps me finding bad things. I still think it is weird that Meili is logging this at Debug level and not at Trace level, since these logs contains a lot of log lines which don't help users tracking bugs which are not Meili related. It is just the same all over again.

[irevoire]

Hello, we just rewrote our whole logging infrastructure; from what I see, this issue is fixed.
It would be nice to get your feedback on the v1.7.0-rc.0 - https://github.com/meilisearch/meilisearch/releases/tag/v1.7.0-rc.0