In Splunk Infrastructure Monitoring, a Metric Time Series (MTS) is uniquely identified by a metric name combined with an exact set of key-value dimensions.
Every individual measurement sent to Splunk Observability Cloud is a datapoint consisting of four core components: the metric name (such as cpu.utilization), a numeric value, a millisecond epoch timestamp, and zero or more dimensions (such as host.name="web-01" and env="prod"). Changing even a single dimension value or adding a new dimension key creates a brand-new MTS.
Understanding MTS identity is vital for both analytics and cost control. High-cardinality dimensions—such as user_id, request_id, or container_id on short-lived pods—can multiply active MTS counts rapidly. Knowing how dimensions shape MTS identity helps you aggregate accurately in SignalFlow and avoid cardinality explosions.
{
"metric": "http.server.duration",
"value": 128.5,
"timestamp": 1763604000000,
"dimensions": {
"service.name": "checkout",
"deployment.environment": "prod",
"http.status_code": "200"
}
}