⛏️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
Analytics Crucible • Room 4

Missing Data, Extrapolation & Max Delay

In real-world distributed systems, network jitter, collector restarts, and ephemeral containers frequently cause datapoints to arrive late or go missing.

SignalFlow relies on two critical controls to handle irregular telemetry: max_delay (or maxDelay, configured in Chart/Detector options or API execution settings rather than inside data()) and extrapolation policies. The max_delay setting tells the streaming engine how long (for example, 30s or 5m, or auto) to wait for slow datapoints before running calculations for a given timestamp. Setting max_delay too short drops late-arriving metrics; setting it too long adds latency to charts and alerts.

Extrapolation defines how Splunk treats missing intervals inside an active MTS when aggregating across a fleet: Null (default/strict) leaves gaps uncounted, Last Value holds the most recent reported number, and Zero treats missing intervals as 0 (useful for sparse error counters that only emit when errors occur).

Specifying Extrapolation & Max Delay in SignalFlow
# max_delay / maxDelay is configured in Chart/Detector/API execution settings, not inside data()
errs = data('payment.errors', extrapolation='zero', maxExtrapolations=3)
errs.sum(by='region').publish(label='Payment Errors')
For sparse counters that only emit datapoints when an error happens, use extrapolation='zero' so aggregations treat quiet intervals as 0 rather than missing data.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Drag items to their correct zone (or tap item then tap zone on mobile)
Leaves gaps empty rather than inventing datapoints when a host stops reporting
Carries forward the previous reported datapoint across brief reporting gaps
Ideal for sparse error counters so quiet intervals evaluate as 0 during sums
Controls how long SignalFlow waits for late-arriving datapoints before computing
Null (Default / Strict)
Last Value (Hold)
Zero (Count Missing as 0)
Max Delay (Wait Window)