[Alpha] Splunk RUM Flutter agent
Alpha documentation links
Tip:
Use these links to navigate through the documentation for this alpha release. These links aren't visible in the left nav.
This Splunk RUM Flutter agent offers the same out-of-the-box metrics provided for native iOS and Android apps, and allows you to see all of your mobile app data in a unified view.
Supported features
| Crash reporting | Crashes are detected in the native layer by the same logic that is present in native agents. Crashes that happen in the Dart (Flutter) or TypeScript (React Native) layer are not captured, as they require framework-specific handling outside of the scope of this alpha release. |
| Manual error reporting | API for manual error reporting is available, but the functionality to deobfuscate errors/crashes from the Dart and TypeScript layer is not present. |
| Network interception | Only network communication that happens through the native libraries ( |
| OpenTelemetry support | Support for OpenTelemetry is limited to the native layer, allowing hybrid agents to emit OTLP. However, the OTel API is not supported on the Dart/TypeScript hybrid layer. |
| ANR/App hang detection | Full functionality. |
| Application startup measurement | The native implementation of startup measurement may not accurately reflect hybrid applications, as it must account for the time required for hybrid functionality to load and render the UI. |
| Slow frame detection | Native measurements are used. |
| Network monitoring | Full functionality. |
| Interaction detection | Interactions are detected, but without context for the UI elements (missing element identifiers), they cannot be used for DEA or other analytics. However, they can be used for visualization in session replay. |
| Navigation detection | Automatic instrumentation is supported for a set of commonly used navigation libraries. Manual instrumentation has full functionality and API. |
| Custom events & workflows | Since the hybrid agents don't include an OTel API, the API is proprietary (uses a proprietary model). Everything is bridged to the native layer, and OTLP is emitted. |
| Local sampling | Full functionality. |
| Span filtering | Agents support filtering but don't directly use the OTel data model (SpanData). |
| Global attributes | Similar to custom events and workflows, there is a proprietary API and bridging to the native layer sets attributes for all OTel signals. |
| User identification | Full functionality. |