Overview

Motadata APM supports Java trace ingestion using OTEL and its custom agent. Java applications must run on supported versions (i.e., Java v8 and above) of the JDK, and trace ingestion is agent-based with runtime instrumentation.

Navigation

Go to Menu > Settings > APM > Application Registration. Clicking the Application Registration button, you can register a new application. From the application registration screen, select the instrumentation type Host/VM or Docker.

Host/VM

Java Trace Configuration

Field	Description
Select Agent	Select the Host/VM where this application is running. You can configure Java application service for both Windows and Linux type agent.
Language	Select Java from the language icons.
Service Name	Provide a unique and meaningful name (e.g., ERP).
Application Path	Specify the full path to the executable JAR file used to start the application. Ensure the path ends with .jar. (e.g home/motadata/app.jar)

Providing these details displays Setup Command to instrument your Java application. Add the following argument to your java -jar command and restart the service to collect Traces.

You can configure Trace ingestion according to the framework used to build the application. The below mentioned are the supported frameworks.

Supported Frameworks

The following frameworks are supported for instrumentation and monitoring. Ensure your application version aligns with the minimum supported version listed below.

Framework	Supported Version(s)
ActiveJ	6.0+
Akka Actors	2.3+
Akka HTTP	10.0+
Apache Axis2	1.6+
Apache Camel	2.20+ (excluding 3.0+ for now)
Apache CXF JAX-RS	3.2+ (excluding 4.0+ for now)
Apache CXF JAX-WS	3.0+ (excluding 4.0+ for now)
Apache Dubbo	2.7+
Apache ShenYu	2.4+
Apache MyFaces	1.2+ (excluding 4.0+ for now)
Apache Pekko Actors	1.0+
Apache Pekko HTTP	1.0+
Apache Struts	2.3+
Apache Tapestry	5.4+
Apache Wicket	8.0+
Armeria	1.3+
Armeria gRPC	1.14+
Avaje Jex	3.0+
AWS Lambda	1.0+
Dropwizard Views	0.7+
Eclipse Grizzly	2.3+
Eclipse Jersey	2.0+
Eclipse Metro	2.2+
Eclipse Mojarra	1.2+ (excluding 4.0+ for now)
Finagle	23.11+
Finatra	2.9+
Grails	3.0+
GraphQL Java	12.0+
gRPC	1.6+
GWT	2.0+
Java HTTP Server	Java 8+
Javalin	5.0+
JAX-RS	0.5+
JAX-WS	2.0+ (excluding 3.0+ for now)
JSP	2.3.x only
Ktor	1.0+
Play MVC	2.4+
PowerJob	4.0.0+
Quarkus Resteasy Reactive	2.16.7+
Ratpack	1.4+
RESTEasy	3.0+ (excluding 6.0+ for now)
Restlet	1.0+
RMI	Java 8+
Servlet	2.2+
Spark Web Framework	2.3+
Spring Batch	3.0+ (excluding 5.0+ for now)
Spring Boot	All supported production versions
Spring Cloud AWS	3.0+
Spring Cloud Gateway	2.0+
Spring Core	2.0+
Spring Integration	4.1+ (excluding 6.0+ for now)
Spring RMI	4.0+
Spring Scheduling	3.1+
Spring Web MVC	3.1+
Spring Web Services	2.0+ (excluding 4.0+ for now)
Spring WebFlux	5.3+
Undertow	1.4+
Vaadin	14.2+
Vert.x Web	3.0+
XXL-JOB	1.9.2+
ZIO	2.0+

Configuring the application, you can provide the below details:

Field	Description
Service Attributes(Tags)	Add key–value tags to your application for better filtering and organizing data in Explorer. Attribute keys must be in lowercase (for example, apm.env = prod). To add multiple Key-Value pairs you can click the add icon.
Add Custom Parameters	Allows you to define custom sampling or tagging parameters for advanced use cases. These optional parameters are passed to the agent (for example, version=4).

Clicking the Apply Configuration button, the ingestion gets started.

Once the Application is Running, you need to verify the below points:

-  Confirm that the service has been registered successfully.
- On the service registration screen, the Service Trace Collection Status should display "Running."
- The traces will start appearing in the APM Explorer screen.

Docker

Java Trace Configuration

Field	Description
Select Agent	Select the Docker where this application is running. You can configure Java application service for Linux type agent.
Language	Select Java from the language icons.
Service Name	Provide a unique and meaningful name (e.g., ERP).
Application Path	Specify the full path to the executable JAR file used to start the application. Ensure the path ends with .jar. (e.g home/motadata/app.jar)

Providing these details displays Setup Command to instrument your Java application. Add the following argument to your java -jar command and restart the service to collect Traces.

You can configure Trace ingestion according to the framework used to build the application. The below mentioned are the supported frameworks.

Supported Frameworks

The following frameworks are supported for instrumentation and monitoring. Ensure your application version aligns with the minimum supported version listed below.

Framework	Supported Version(s)
ActiveJ	6.0+
Akka Actors	2.3+
Akka HTTP	10.0+
Apache Axis2	1.6+
Apache Camel	2.20+ (excluding 3.0+ for now)
Apache CXF JAX-RS	3.2+ (excluding 4.0+ for now)
Apache CXF JAX-WS	3.0+ (excluding 4.0+ for now)
Apache Dubbo	2.7+
Apache ShenYu	2.4+
Apache MyFaces	1.2+ (excluding 4.0+ for now)
Apache Pekko Actors	1.0+
Apache Pekko HTTP	1.0+
Apache Struts	2.3+
Apache Tapestry	5.4+
Apache Wicket	8.0+
Armeria	1.3+
Armeria gRPC	1.14+
Avaje Jex	3.0+
AWS Lambda	1.0+
Dropwizard Views	0.7+
Eclipse Grizzly	2.3+
Eclipse Jersey	2.0+
Eclipse Metro	2.2+
Eclipse Mojarra	1.2+ (excluding 4.0+ for now)
Finagle	23.11+
Finatra	2.9+
Grails	3.0+
GraphQL Java	12.0+
gRPC	1.6+
GWT	2.0+
Java HTTP Server	Java 8+
Javalin	5.0+
JAX-RS	0.5+
JAX-WS	2.0+ (excluding 3.0+ for now)
JSP	2.3.x only
Ktor	1.0+
Play MVC	2.4+
PowerJob	4.0.0+
Quarkus Resteasy Reactive	2.16.7+
Ratpack	1.4+
RESTEasy	3.0+ (excluding 6.0+ for now)
Restlet	1.0+
RMI	Java 8+
Servlet	2.2+
Spark Web Framework	2.3+
Spring Batch	3.0+ (excluding 5.0+ for now)
Spring Boot	All supported production versions
Spring Cloud AWS	3.0+
Spring Cloud Gateway	2.0+
Spring Core	2.0+
Spring Integration	4.1+ (excluding 6.0+ for now)
Spring RMI	4.0+
Spring Scheduling	3.1+
Spring Web MVC	3.1+
Spring Web Services	2.0+ (excluding 4.0+ for now)
Spring WebFlux	5.3+
Undertow	1.4+
Vaadin	14.2+
Vert.x Web	3.0+
XXL-JOB	1.9.2+
ZIO	2.0+

Configuring the application, you can provide the below details:

Field	Description
Service Attributes(Tags)	Add key–value tags to your application for better filtering and organizing data in Explorer. Attribute keys must be in lowercase (for example, apm.env = prod). To add multiple Key-Value pairs you can click the add icon.
Add Custom Parameters	Allows you to define custom sampling or tagging parameters for advanced use cases. These optional parameters are passed to the agent (for example, version=4).

Clicking the Apply Configuration button, the ingestion gets started.

Once the Application is Running, you need to verify the below points:

• Confirm that the service has been registered successfully.
• On the service registration screen, the Service Trace Collection Status should display "Running."
• The traces will start appearing in the APM Explorer screen.