⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
Observability Foundations • Room 2

Metric Time Series (MTS) & Datapoints

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.

Single Datapoint & Resulting MTS Identity
{
  "metric": "http.server.duration",
  "value": 128.5,
  "timestamp": 1763604000000,
  "dimensions": {
    "service.name": "checkout",
    "deployment.environment": "prod",
    "http.status_code": "200"
  }
}
A single datapoint has four parts: metric name, value, timestamp, and dimensions. Adding one extra dimension key splits one MTS into many.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Complete the Splunk Infrastructure Monitoring data model definition:
A unique is defined by the combination of a name and its exact set of key-value .