metrickit

To collect MXMetricPayload and MXDiagnosticPayload data, implement the MXMetricManagerSubscriber protocol and register with MXMetricManager at app startup to receive daily aggregated performance metrics and immediate diagnostic events from production devices.

When subscribing to MetricKit, you must correctly handle pastPayloads and pastDiagnosticPayloads upon initial registration to process any aggregated metrics and diagnostic payloads that were missed before your subscriber was active.

You analyze MXCallStackTree data by receiving it through MXDiagnosticPayload callbacks, safely persisting the jsonRepresentation() to disk before processing, and extracting the call stack trees for crash, hang, and CPU exception diagnostics.

Yes, you can emit mxSignpost custom interval measurements in your app, and these custom signpost metrics will appear inside MetricKit payloads for deeper performance attribution alongside standard system metrics.

MetricKit requires early subscriber registration at app launch and safe persistence of jsonRepresentation() before processing, because you must handle heavier work asynchronously to avoid blocking and ensure past payloads are not lost.

Yes, MetricKit works alongside Xcode Organizer, allowing you to collect on-device metrics locally and optionally review performance trends and regressions within the Xcode Organizer environment.