Setup and configuration
Depending on the architecture of your deployment and the goals you want to achieve, you can choose among the following extension methods:
The Dynatrace OneAgent SDK enables you to instrument your applications manually to extend end-to-end visibility for frameworks and technologies for which there is no code module available. With the SDK, you get full access to all analysis and monitoring functionality, including auto-baselining and AI-based root cause analysis. For more information, see OneAgent SDK.
- If you can install OneAgent on a host, use OneAgent extensions.
- If you need to monitor a remote technology where OneAgent installation isn't an option, use ActiveGate extensions.
- If you simply want to monitor a Java application that exposes MBeans, use JMX extensions.
With OneAgent extensions, you can extend OneAgent monitoring to any OneAgent-detected processes that expose an interface (for example, processes that are served over HTTP—databases, applications, and load balancers). extensions run within a OneAgent and fully integrate new-technology monitoring into Dynatrace Smartscape and problem detection. You need some Python expertise to develop OneAgent extensions. For more information, see OneAgent extensions.
With ActiveGate extensions, you can extend Dynatrace monitoring to any remote technology that exposes an interface, where OneAgent installation isn't an option. For example, PaaS technologies, network devices, or cloud technologies. ActiveGate extensions (aka Remote Plugins) are executed on ActiveGate and can acquire metrics and topology from remote sources, fully integrating new-technology monitoring into Dynatrace Smartscape and problem detection. You need some Python expertise to develop ActiveGate extensions. For more information, see Introduction to ActiveGate extensions.
With JMX/PMI extensions you extend Dynatrace monitoring to any Java based application exposing MBeans. No coding required, use our intelligent wizard to guide through the extension configuration and deployment. For more information, see How do I monitor JMX metrics in my Java applications?.
The Extension SDK is a versatile solution that enables you to monitor any custom technology that exposes an interface. Develop and deploy your extensions. Dynatrace can seamlessly integrate your custom-technology monitoring data into relevant analysis views, taking full advantage of all your favorite Dynatrace features and AI-driven root cause analysis.
If your business has digital touchpoints outside of your applications, you can use Dynatrace OpenKit to instrument them, whether or not they’re traditional rich client applications, smart IoT applications, or even Alexa skills. Dynatrace OpenKit is best suited for client/server applications that communicate via HTTP (for example, rich-client-applications, embedded devices, and terminals). For more information, see Dynatrace OpenKit.
Custom metric ingestion and analysis
A custom metric is defined as a new type of metric that offers a user-provided metric identifier and unit of measure. The semantics of custom metrics are defined by you. Following the definition of a custom metric, the metric can be reported for multiple monitored components. For full details on the setup and consumption of custom metrics in Dynatrace, see Custom metrics ingestion and analysis.