Instrument your application using Dynatrace OpenKit
Monitoring data sent via Dynatrace OpenKit is encapsulated into an entity that represents your application and is called custom application. Therefore, to monitor your application, you need to define and instrument the custom application following the instructions below.
Create and instrument an application
To create a custom application in Dynatrace and instrument it
- In Dynatrace, go to Custom Applications.
- Select Create custom application.
- Enter a name for your custom application, and choose an icon to visually represent your application in the Dynatrace web UI.
- Select Monitor custom application. Your custom application settings page opens.
- From the application settings, select Instrumentation wizard and then select your technology to download the latest OpenKit library.
- Use the downloaded library and the Beacon URL and Application ID provided in the instrumentation wizard to instrument your application.
- optional In the instrumentation wizard, select View incoming beacons to show incoming beacons as they arrive, with only a couple of seconds delay. This view also provides information about potential issues.
Below is a basic example that shows how to use Dynatrace OpenKit to send monitoring data to Dynatrace. For more details, see Dynatrace OpenKit API methods.
You can find your application ID and the endpoint URL in the instrumentation wizard (from your application settings, select Instrumentation wizard).
For custom applications, user identification is achieved by passing deviceID
, which should be unique for each user or device. Then deviceID
is marked as the Internal user ID in the Dynatrace web UI.
Customize instrumentation
After creating a custom application in Dynatrace and instrumenting your actual application with OpenKit, check the pages below to customize and troubleshoot the instrumentation and configure your custom application.
- Dynatrace OpenKit libraries on GitHub
- Dynatrace OpenKit API methods
- Dynatrace OpenKit logging
- Troubleshoot Dynatrace OpenKit instrumentation
- Configure cost and traffic control for custom applications
- Ignore web request errors for custom applications
- Create custom user action names for custom applications
- Configure key user actions for custom applications
- Adjust Apdex settings for custom applications
- Change user experience score thresholds for custom applications
- Create calculated metrics for custom applications
- Create USQL custom metrics for custom applications
- Define user action and user session properties for custom applications
- Customize IP address detection for custom applications
- Map internal IP addresses to locations for custom applications
- Configure first-party, third-party, and CDN resource detection for custom applications
- Use OneAgent as a beacon endpoint for custom applications
- Delete a custom application
Analyze and use RUM data
Once your custom application starts sending monitoring data to Dynatrace, you can analyze this data just like you do for any other application. See the pages below for more information.
The image below shows the overview page of our test custom application.