Dynamically Change Log Levels in the Milvus Vector Database

What this post added

This post details the implementation and usage of dynamic log level adjustment in Milvus. It explains how the Uber zap logger's HTTP handler is integrated to expose a `/log/level` endpoint on port 9091. Instructions are provided on how to query the current log level and change it using `curl` commands, specifying levels such as debug, info, warn, error, dpanic, panic, and fatal.