TechPrufer
Get started
Milvus
Milvus logoMilvus · Feature trail

Dynamic Log Level Control

1 post · Sep 2022 – Jan 2024

What this trail covers

Milvus introduces dynamic log level control via an HTTP interface on port 9091, allowing engineers to adjust logging verbosity (debug, info, warn, error, dpanic, panic, fatal) without service restarts. This mechanism leverages the Uber zap logger's http_handler.go module, enabling real-time performance debugging and issue identification.

All Milvus trails
  1. Milvus 2.3.4: Faster Searches, Expanded Data Support, Improved Monitoring, and MoreMilvus 2.3.4 introduces access logs for improved monitoring of gRPC interactions, recording method names, user requests, response times, and error codes. It also adds support for importing Parquet files, streamlining data processing and making Parquet the default output for the BulkWriter tool. Searches in growing segments are up to tenfold faster due to a new binlog index. The limit for collections/partitions has been increased to 10,000. Other enhancements include reduced memory usage, refined error messaging, accelerated loading, and improved query shard balance.
  2. Dynamically Change Log Levels in the Milvus Vector DatabaseThis post details the implementation of dynamic log level control in Milvus by leveraging the Uber zap logger's http_handler.go module. It explains how Milvus exposes an HTTP interface on port 9091 to allow real-time modification of log levels without requiring service restarts, facilitating performance debugging and issue identification.