_
_
GlassFish is the Eclipse implementation of Jakarta EE (formerly the reference implementation from Oracle) and supports Jakarta REST, Jakarta CDI, Jakarta Security, Jakarta Persistence, Jakarta Transactions, Jakarta Servlet, Jakarta Faces, Jakarta Messaging, and more. This allows developers to create enterprise applications that are portable and scalable and that integrate with legacy technologies. RapDev’s GlassFish integration enables users to monitor several different modules within GlassFish, such as applications, the HTTP service, the JMS service, JVM metrics, networking, and the transaction service. This can provide helpful insights into the performance of the various components deployed in the GlassFish server to help tune performance, identify bottlenecks, and perform root cause analysis.
As a robust Java application server, GlassFish hosts servlets for handling HTTP requests and responses. Identifying and being informed of bottlenecks and other performance problems before they translate into issues reported by the users of GlassFish applications is extremely important. By collecting metrics specific to individual GlassFish applications, such as requests, errors, processing times, and response times, application administrators can use RapDev’s integration to ensure their applications are in a healthy state to serve their users.
On top of being able to track the health of the HTTP applications hosted on GlassFish, this integration also collects GlassFish virtual server metrics surrounding the embedded HTTP service. Metrics such as requests and errors by status code, bytes received and transmitted, average processing time, and connection rate can be used to identify potential client-server communication, application performance, or other issues within the entire scope of the application stack.
GlassFish, being a Java-based application server, contains metrics related to the overall performance of the JVM as the execution environment for the applications being hosted on it. By closely monitoring this integration’s JVM metrics, such as heap memory, loaded and unloaded classes, and daemon and deadlocked threads, administrators can gain crucial insights into resource utilization patterns for GlassFish domains. Pre-emptively detecting memory leaks, high CPU utilization, and excessive garbage collection allows for proactive intervention to prevent degradation in application performance, thus delivering a smooth experience to applications’ end users.
A transaction is a group of specific actions that must all be completed successfully within the application. By coupling actions into its own unit of work, a transaction can ensure data integrity and consistency since the tasks within them happen in the same order every time. If one of the tasks within a transaction is not completed successfully, the changes get rolled back, bringing the system to the same state it was before the transaction took place. On top of reliable transactions, having reliable networking components should be a top priority when serving applications to end users. RapDev’s GlassFish integration tracks information such as cache hit and lookup percentages, active vs. queued connections, and transactions committed and rolled back to give a broader picture of some of the issues that could be affecting the performance and stability of the applications the GlassFish server is hosting.
The GlassFish integration by RapDev ships with a standard out-of-the-box monitor, dashboard, and log pipeline to provide a high-level overview and correlation of just some of the observability possibilities users can unlock when utilizing this integration to monitor their GlassFish domains, virtual servers, and applications. Interested in trialing the integration? Check it out in the Datadog Marketplace!
This isn't the integration you're looking for? Missing a critical feature for your organization? Drop RapDev a note at support@rapdev.io, and we'll build it!!
