![]() A manual startup on the other hand occurs later, thereby causing you to miss everything, including this application startup event, until the startup occurs.Ī manual startup requires the following two steps: Note: An automated startup usually provides you with a lifecycle application start-up event. If you can't do a automated startup through the, you can always perform a manual startup and decide values such as beaconUrl and applicationId at runtime. ![]() Not resetting the cache might result in an mixture of old and new configuration. Metro caches all files and a configuration change might lead to a different situation. Specify custom paths via custom arguments.Īttention: Whenever you change your configuration in please use react-native start -reset-cache option. Use react-native run-android or react-native run-ios to rebuild and run your app. ![]() You can use the same custom arguments as mentioned above. This will configure both Android and iOS projects with the settings from. Build and run your appĮxecute npx instrumentDynatrace or react-native instrument-dynatrace in the root of your React Native project. The required changes for the versions above can be found here. expo v44.0.0 or newer or babel-preset-expo v9.0.0 or newer:.The changes have to be done in the following cases: Update Babel Configurationĭepending on your version of Metro or Expo (if used), your babel configuration will need to be updated. This is important as you will only see Application startup and Touches out of the box.įor more details about the configuration, see Advanced topics. Note: Define the components that you want to see lifecycle instrumented ( example). If you are not sure you can always use npx configDynatrace to create a default configuration file. Download and copy this file into the root folder of your application. In the settings you will see a file which can be downloaded for React Native. Your old configuration is still available in nfig and you have to copy your values to the new .ĭefine a mobile app in Dynatrace and open the Mobile app instrumentation settings. Note: If you are upgrading from a previous version of this plugin, you'll notice that the file format has changed. In your project's root directory, create or extend so that it contains the following configuration properties transformer.babelTransformerPath and reporter: For React Native v0.72.1 or newer If you already have a babel transformer (babelTransformerPath) in place, you need to use the upstreamTransformer property in to use a transformer besides our dynatrace transformer. The following configuration must be added. If you don't know the version, enter react-native -version in your terminal. seperate native projects) react-native link doesn't work as expected, manually add the iOS agent to your project.ĭepending on your React Native version, you will need to use a different way to register the transformer. Standalone Project: If you are using React Native standalone and embed it in your native project have a look here.This means every time the configuration changes you need to call npx instrumentDynatrace. Furthermore you need to trigger the configuration manually as the plugin is only automatically working with the React Native CLI. Expo: Make sure you actually have platform folders like android/ and/or ios/ so the plugin can do the configuration correctly.React Native v0.60 or newer : npm install React Native v0.59.x : react-native install iOS only : If you use pods, you need to go into your ios directory and execute pod install to install the new Dynatrace dependency to your xCode project.When your changed be sure to execute npx instrumentDynatrace beforehand. Note: If you are upgrading to React Native v0.70 (or newer) or using the 9.x+ version, be aware that our automated script running before every start/run-android/run-ios command is no longer working. Configuration of standalone React Native project.Using a second transformer besides the dynatrace transformer.How does Dynatrace determine the user action name?.This agent versions are configured in this plugin: Gradle version 6.1.1+ ( How to update?).Typescript bindings to add manual instrumentation.User actions for class and functional components (lifecycle events such as render(), didMount() and didUpdate()).User actions for onPress and onLongPress (Touchables, Buttons, Pickers, RefreshControl, Pressable).User actions for application start and native controls.Auto-instrumentation using OneAgent for Android and iOS. ![]() For an intro you can also check out our announcement blog post. If you want to start using this plugin and are not a Dynatrace customer yet, head to and sign up for a free trial. The Dynatrace React Native plugin helps auto-instrument your React Native app with Dynatrace OneAgent for Android and iOS and also provides an API to add manual instrumentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |