Technologies/Meilisearch/meilisearch.index.field_distribution
MeilisearchMeilisearchMetric

meilisearch.index.field_distribution

Documents per field distribution
Dimensions:None
Available on:PrometheusPrometheus (1)Native (1)
Interface Metrics (2)
PrometheusPrometheus
Number of documents containing each field in an index
Dimensions:None
Native
Number of documents containing each field in the index
Dimensions:None
Sources
meilisearch_index_field_distributiondocs.meilisearch.com
index.field_distributionwww.meilisearch.com

Technical Annotations (14)

Error Signatures (5)
MDB_TXN_FULL: Transaction has too many dirty pages - transaction too bigerror code
internalerror code
A document cannot contain more than 65535 fieldserror code
max_fields_limit_exceedederror code
A document cannot contain more than 65,535 fields.log pattern
CLI Commands (1)
curl -H "Authorization: Bearer ${MEILISEARCH_API_KEY}" -H "Content-Type: application/json" "${MEILISEARCH_HOST}/indexes/${INDEX_NAME}/documents/delete" -d "{\"filter\": \"timestamp < $(date --date=\"00:00 today\" -u \"+%s000\")\"}" diagnostic
Technical References (8)
LMDBcomponentfacet databasecomponentdocumentDeletioncomponentdot-notated pathconceptJSON.stringifyconceptdocumentAdditionOrUpdatecomponentfield_distributionconceptindex schemaconcept
Related Insights (3)
Index corruption when bulk deletion fails with MDB_TXN_FULL transaction limitcritical
▸
Nested object flattening causes field limit exceeded during ingestioncritical
▸
Schema evolution accumulates field definitions causing field limit exceeded errorscritical
▸