Milvus Plugin

The Milvus plugin registers vector database operations as a Konduo resource. It exposes Milvus-specific signals such as search latency, query queues, insert/write path behavior, collection load, compaction/index/import backlog, and node memory.

Highlights

• Validates endpoint connectivity and TLS/auth settings with bounded health checks.
• Reads Milvus logical metrics through a linked Prometheus metric source.
• Focuses dashboards on search serving, collection load, write delay, background backlog, and capacity risk.
• Groups diagnostics around serving degradation, write path delay, background backlog, and capacity risk.

Before Registration

• Prepare Milvus endpoint, database, username/password or token, and TLS settings.
• Confirm that metric label filters select only the target Milvus deployment.
• Metric names and labels can vary by deployment; review panel coverage after applying the mapping pack.

Operations Tips

• Read search latency and query queues together with collection load, segment state, and query node memory.
• For write path delay, check insert rate, flush latency, time tick lag, and compaction backlog together.
• Arbitrary collection mutation and data operations are outside the current CE operating boundary.

---

Milvus Enterprise Overlay

The Milvus Enterprise overlay adds MCP descriptors, advanced diagnostics, metric mapping, and anomaly rules to Milvus resources. It explains vector database health through read-oriented evidence for collections, indexes, query nodes, and data nodes.

Highlights

• Provides resource metadata, monitoring overview, topology, diagnostics, metric mapping, and alert/anomaly rules through MCP.
• Diagnostics summarize collection, index, query node, and metric coverage evidence for operators.
• Anomaly rules resolve Milvus logical metrics through metric sources in declarative metric mode.
• Default behavior is read-only diagnostics; state-changing workflows need separate action routes and authorization boundaries.

Before Registration

• Community Milvus connectivity and authentication must be healthy.
• Connect a Prometheus metric source and Milvus mapping pack.
• MCP users need resource read permission and the required scopes.

Operations Tips

• Interpret search latency, index state, and query node pressure together with collection size and workload changes.
• If diagnostics lack evidence, check metric endpoint exposure and mapping pack application first.