Note that you shouldn't interact with a finished custom action. Terminated by OneAgent (for example, when OneAgent shuts down).Completed via DTXAction#leaveAction(), or.To check the state of a custom action, use the DTXAction#isFinished() method.Ī custom action is finished when the action is: Sometimes it's helpful to know whether a custom action is still open and can be used to report data. All associated data is stored and sent to Dynatrace Kotlin copy download // create a custom action val action = Dynatrace.enterAction( 'Tap on Purchase') If custom actions are not closed explicitly, OneAgent closes them and sends them to the Dynatrace Cluster.Ĭall enterAction to start a custom action and leaveAction to close a custom action. You can create custom actions and enhance them with additional information. However, when OneAgent shuts down or has to start a new session, it closes all open custom actions. OneAgent does not automatically add additional events, such as web requests, to custom actions or close custom actions.

Attach a web request to the user actionĬustom actions are different from the user actions created with the Dynatrace Android Gradle plugin.You can then enrich these custom actions using the following monitoring operations: With user action monitoring, you can define and report custom actions. In this case, you can override the values pre-configured from the auto-instrumentation. You can then define a manual Dynatrace.startup call. Use the autoStart.enabled property to deactivate the auto-start feature from the auto-instrumentation. In this case, the injected Dynatrace.startup call is called before your manual Dynatrace.startup call, so your manual configuration is ignored. If you use a combination of manual and auto-instrumentation, the auto-instrumentation injects a Dynatrace.startup call into the Application.onCreate method.

Okhttp kotlin