mirror of
https://github.com/milvus-io/milvus.git
synced 2026-07-21 10:15:43 +00:00
5eebaa9ad4
issue: #47404 - message trace context: add trace context serialization and restore/inject helpers for WAL messages and msgstream conversion - WAL append trace: normalize WAL spans for autocommit, txn, broadcast, append, appendimpl, and broadcast callback paths - trace propagation: restore message trace context in producer, broadcast retry, replicate primary/secondary, recovery, flusher, and query/data flowgraph consumers --------- Signed-off-by: chyezh <chyezh@outlook.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Observability - AI Agent Guides
This directory contains observability guides for AI agents working on Milvus. Use these guides before changing logging, metrics, tracing, or related configuration.
Guides
| Guide | Use When |
|---|---|
| mlog - AI Agent Logging Guide | Adding or changing application logs. Covers mlog usage, context requirements, fields, levels, and logging rules. |
| WAL Tracing | Understanding or changing WAL trace span semantics across append, consume, transaction, broadcast, and replication paths. |
Rules of Thumb
- Use
mlogfor all Milvus logs. Do not usezap, the oldpkg/logpackage, the standardlogpackage, orfmt.Printlnfor runtime logging. - Keep observability hot paths cheap. Avoid payload logging and high-cardinality metric labels.
- When debugging, start from the narrowest available evidence such as trace ID, request time window, node, collection, channel, or error message.
- Preserve compatibility for metric names, label sets, config keys, and log field names unless the task explicitly requires a breaking change.
- Add or update focused tests when changing observability behavior.