Numeric measurements aggregated over time, indexed by a small set of high-cardinality-bounded dimensions, used to characterise the rate, throughput, latency, and saturation of a system. Metrics are cheap to query and cheap to retain at long horizons but lose individual-event detail; they complement rather than substitute for logs and traces. The federation expects that metric naming, units, and dimensions follow a documented convention and that high-cardinality dimensions be controlled to prevent storage explosion under UFMS-001:2.4.
The word metric in measurement contexts dates to the eighteenth century; the modern observability usage emerged in the carrier-grade monitoring tradition of the late twentieth century and was popularised in cloud through Prometheus from 2012.
Federation members must publish a metric naming convention and a cardinality budget per service. Cardinality breach without remediation within thirty days is reported under MEV-Annex:3.2.
@misc{ifo4_glossary_metrics,
title = {{Metrics}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{metrics}}},
year = {2026},
url = {https://ifo4.org/glossary/metrics},
note = {Category: Observability; key: Metrics}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.