splunk-observability-mobile-rum-setup

Splunk Mobile RUM instrumentation is set up by rendering and validating observability snippets across iOS, Android, React Native, and Flutter platforms. This process enforces per-platform version pins and realm configurations while keeping app sources intact until approval.

Yes, the default behavior renders mobile RUM snippets and runbooks to prepare instrumentation without mutating app code. Guarded source patches are only generated and applied after explicit review and approval are granted.

Session replay gating for Splunk mobile RUM is enforced through enterprise-ready controls during the asset rendering and validation workflow. This ensures privacy controls and compliance requirements are met before applying instrumentation patches.

RUM-to-APM validation handoffs are provided natively within the mobile RUM setup workflow. This generates the necessary end-to-end readiness checks for production workflows, alongside handoffs for Browser RUM validation.

Yes, patch-apply gating is a core enforcement feature of the mobile RUM setup workflow. It ensures guarded source patches and render-patches are only applied when review and approval are explicitly granted, maintaining enterprise readiness.

Specifying a realm and the api_version splunk-observability-mobile-rum-setup/v1 is required to enforce correct routing and compatibility. These configurations validate mobile RUM assets and ensure proper per-platform instrumentation pins.