[itaybre]

Let SDK integrations record a metric for a moment in the past. The metrics API always stamped metrics with the current time, but MetricKit metric payloads (#9269) describe a reporting interval of up to a day before they are delivered.

Internal overloads

SentryMetricsApi+Internal.swift adds count, distribution and gauge overloads that take a timestamp: Date. They live on the internal SentryMetricsApi struct, not on the public SentryMetricsApiProtocol that SentrySDK.metrics is typed as, so the public API and its snapshots are unchanged. Metrics recorded without a timestamp keep using the current date.

let metrics = SentryMetricsApi(dependencies: SentryDependencyContainer.sharedInstance())
metrics.distribution(key: "metrickit.launch.time_to_first_draw", value: 1.2, unit: .second, timestamp: intervalStart)

Timestamp age

The SDK sends the timestamp as is. Relay rejects trace metrics older than the organization's trace metric retention and corrects timestamps for client clock drift (relay-server/src/processing/utils/normalize.rs), so ingestion owns the limit and a day-old MetricKit payload is well within it.

The trace ID is still taken from the scope when the metric is recorded. Whether past metrics should carry it is left to #9269.

Fixes #9268

#skip-changelog

[sentry]

Size Analysis

1 component analyzed

iOS Builds

Name	Configuration	Version	Download Size	Install Size
SDK-Size (iOS) io.sentry.sample.SDK-Size	Release	9.31.0 (1)	1.2 MB (+106 B)	3.1 MB (0 B)

Configure sentry-cocoa status check rules

[sentry]

📲 Install Builds

iOS

🔗 App Name	App ID	Version	Configuration
SDK-Size	io.sentry.sample.SDK-Size	9.31.0 (1)	Release

⚙️ sentry-cocoa Build Distribution Settings