Skip to main content

Slow Logs Reference

Slow logs are delivered in JSON Lines format - one JSON object per line. Each line is a self-contained JSON object representing a single operation. The following example shows a representative slow log entry for a search request:

json
{
"action": "Search",
"cluster_id": "inxx-xxxxxxxxxxxxxxx",
"collection": "medium_articles",
"connection_uid": "453798218345292801",
"consistency_level": "Bounded",
"database": "default",
"error_code": 0,
"execution_time": "231.4ms",
"interface": "Grpc",
"ip": "203.0.113.10",
"log_type": "SLOW",
"output_fields": ["title", "author"],
"partition": null,
"sdk": "pymilvus",
"sdk_version": "2.6.0",
"status": "Success",
"timestamp": 1776148276827,
"trace_id": "f89903d701329910380442aa86941be9",
"user": "key-ibchakktguxxrvvxseoasz"
}

In practice, each entry occupies a single line in the .log file. The sections below describe each field in detail.

Log field schema

FieldRequiredTypeDescriptionExample
actionNostringThe operation name, such as Query, Search, or Hybrid Search."Search"
cluster_idYesstringThe unique identifier of the cluster. This field is required by the downstream log pipeline."inxx-xxxxxxxxxxxxxxx"
collectionNostringThe target collection when the action is collection-scoped."medium_articles"
connection_uidNostringThe internal connection identifier associated with the request."453798218345292801"
consistency_levelNostringThe consistency level used by the request."Bounded"
databaseNostringThe database where the operation occurred."default"
error_codeNointThe request result code. 0 typically indicates success.0
execution_timeNostringThe measured execution time used to determine whether the request should be emitted to slow log."231.4ms"
interfaceNostringThe request interface, typically Grpc or Restful."Grpc"
ipNostringThe client IP address recorded for the request."203.0.113.10"
log_typeYesstringThe log category. For slow log entries, the value is SLOW."SLOW"
output_fieldsNoarrayThe output fields requested by the query, when applicable.["title", "author"]
partitionNostring or nullThe target partition. The value is null when no partition is specified.null
sdkNostringThe client SDK name."pymilvus"
sdk_versionNostringThe client SDK version."2.6.0"
statusNostringThe human-readable request status."Success"
timestampYesintUnix timestamp in milliseconds. This field is required by the object storage sink when generating the final file path.1776148276827
trace_idNostringA unique request trace identifier for correlation and troubleshooting."f89903d701329910380442aa86941be9"
userYesstringThe user name or API key that issued the request. This field is also used by the pipeline filter."key-ibchakktguxxrvvxseoasz"

Supported actions

The current slow logs feature enables the following actions by default:

ActionDescription
SearchVector similarity search
HybridSearchMulti-vector search with reranking
QueryScalar filtering query

File path and naming

Slow log files are uploaded to object storage under the slow directory and use UTC date and time in the final object key.

plaintext
/<Cluster ID>/slow/<Date>/<File name>.log
ComponentFormatExample
Cluster IDThe cluster unique identifier.inxx-xxxxxxxxxxxxxxx
Log type directoryFixed as slow.slow
DateUTC date in YYYY-MM-DD format.2026-04-14
File nameHH:MM:SS-<UUID>.log, using UTC time.06:31:16-jz5l7D8Q.log

Full path example:

plaintext
/inxx-xxxxxxxxxxxxxxx/slow/2026-04-14/06:31:16-jz5l7D8Q.log
Ctrl I