On this page, you will learn how to perform initial setup for iOS frontends.
Before you begin, ensure your environment meets the following requirements:
Experience Vitals > Overview.To enable the New RUM Experience for web frontends at the environment level:
Experience Vitals.Follow the instrumentation wizard in the experience vitals app to include the agent into your setup.
Add your application's identification keys to your app's Info.plist file. You can find these values in the instrumentation wizard.
<key>DTXApplicationID</key><string>YOUR_APPLICATION_ID</string><key>DTXBeaconURL</key><string>YOUR_BEACON_URL</string>
Replace YOUR_APPLICATION_ID and YOUR_BEACON_URL with the actual values from the instrumentation wizard in Dynatrace.
Import the Dynatrace module in your app to verify the integration.
import Dynatrace
Trigger a project build once before using any OneAgent SDK methods or import declarations.
Build and run your application to verify the installation.
After completing the basic setup, you can customize OneAgent behavior using configuration keys in your Info.plist file. For detailed configuration options including manual startup, debug logging, and all available keys, see Configuration.
| Configuration key | Default | Description |
|---|---|---|
DTXApplicationID | — | Your application's unique identifier (required) |
DTXBeaconURL | — | The beacon endpoint URL (required) |
DTXStartupWithGrailEnabled | false | Sends data to Grail from the first app start |
For a complete list of configuration options, see Configuration keys.
After installing and configuring OneAgent, verify that data is being collected:
Open your app and perform several actions (navigate between screens, tap buttons, and make network requests).
Go to your mobile frontend in Dynatrace:
Experience Vitals > Overview.Verify that sessions and user actions appear in the data.
This data can also be analyzed directly in Grail using DQL.
It may take a few minutes for data to appear in Dynatrace after the first app launch.
For information about supported versions, known limitations, and compatibility with other monitoring tools, see Support and limitations.